Operations | Monitoring | ITSM | DevOps | Cloud

“How am I supposed to debug this?" Just imagine: Late Friday, you are about to shut down your laptop and … an issue comes up. Warnings, alerts, red colors. Everything that we, developers, hate the most. The architect decided to develop that system based on microservices. Hundreds of them! You, as a developer, think why? Why does the architect hate me so much? And then, the main question of the moment: How am I supposed to debug this?

Enrique Fueyo Ramírez is the Co-founder and CTO of Lang.ai. Here’s a post on how him and his team at Lang.ai instrumented performance monitoring for GraphQL resolvers.

A service desk is the focal point of an IT organization to render services, and the quality of its services determines the perception of being a valuable part of the organization. The ongoing transition of businesses to adopt cloud infrastructure has forced IT organizations to modernize their service desks, which include vendors adopting cloud capability and smart automation powered by AI.

One of the easiest ways to increase query performance in SQL Server is to make sure it can quickly access the requested data as efficiently as possible. In SQL Server, using one or more indexes can be exactly the fix you need. In fact, indexes are so important, SQL Server can warn you when it figures out there’s an index missing that would benefit a query.

We may be biased, but we think we’ve had some great blogs that are informational, impartial, and (hopefully) not boring to read about all things related to what’s happening on the internet. Looking back at our blog—dating back to 2006—one series saw the limelight from 2012-2017: the state of the internet series.

Collaboration tools like Slack and Teams are here to stay. They’re very much inseparable from the distributed workforce that we all continue to find ourselves in. A robust set of integrations are then an essential part of today's monitoring and observability platforms. Feeding Catchpoint data into your support team via a Slack channel could be the difference between catching a disruption early or having to respond to a full-blown outage.

Systems run into problems all the time. To keep things running smoothly, we need to have an error monitoring and logging system to help us discover and resolve whatever issue that may arise as soon as possible. The bigger the system the more challenging it becomes to monitor it and pinpoint the issue. And with serverless systems with 100s of services running concurrently, monitoring and troubleshooting are even more challenging tasks.