Operations | Monitoring | ITSM | DevOps | Cloud

Software development has always played a vital role in the development of a business. But software development is not only the coding of a part of the software; it also extends to debugging, testing, releasing frequently, and monitoring. Application performance monitoring is one of the most essential things that every software needs to do because a running software application can always go wrong in ways unimaginable.

The complexity of applications is continually increasing the need for good logs. This need is not just for debugging purposes but also for gathering insight about the performance and possible issues with an application. The Python standard library is an extensive range of facilities and modules that provide most of the basic logging features. Python programmers are given access to system functionalities they would not otherwise be able to employ.

An application running in production is a difficult beast to tame. Most experienced developers–ones who spent enough late nights or Saturday mornings trying to break apart a nasty production bug–will try and create the clearest possible picture for their later selves while writing their code, so that they could understand what’s actually going on in the system during an incident.

If the last year has taught those of us at ScienceLogic anything, it is that we underestimated how much our customers and partners relied on us. It’s understandable, really, since no one could have anticipated the pandemic-driven chaos, and how it would push IT to its limits—and beyond.

An important skill in database performance tuning is capturing, reading, and understanding query execution plans. The query execution plan is a roadmap of the resources allocated and operations performed when the database engine gathers the results of your query.

Efficient root cause analysis is vital to incident management. How quickly an issue can be understood determines the mean time to resolve (MTTR), which directly impacts the digital experience. When there is a sudden outage or a performance degradation, root cause analysis can become laborious given the complexity of all the components involved and the potentially huge amount of observability data generated from different sources.

In the last century we had very primitive computers and now, at the dawn of a new millennium are we the users who have become primitive!? Want to learn more? Let’s get to know User Experience Monitoring My first computer, in 1987, was a laptop with a monochrome LCD screen and 16 kilobytes of program memory. They were 15,584 precious bytes and they were read and executed very quickly.

OpenTelemetry (or “OTel”) helps you get your instrumentation started quickly, and it helps you get the most out of that telemetry data by providing flexible exporting options. As a result, it’s emerging as the new standard for instrumentation. To that end, today we’re sharing more insight into the work we’ve done (and are doing) to enable a path for all Honeycomb users toward OTel adoption. We hope you’ll be as excited as we are to embrace these open standards!