Operations | Monitoring | ITSM | DevOps | Cloud

Outages on the Internet always catch you by surprise, whether you are the end user or the Head of SRE or DevOps trying to keep a clear mind while you execute your incident playbook. As people in charge of ensuring reliable services for our customers, our normal experience of outages involves surfing a deluge of fire alarms and video calls as we work to solve the problem as quickly as we can. We often forget, therefore, what an outage means to the end user.

We are super excited to release the second Release Candidate of Icinga DB! This release comes after many hours, days and months of experimenting, re-thinking and rebuilding our own code and marks a huge step towards a new data backend for Icinga.

Complex incidents are both exhausting and commonplace. In this case, incidents that I am referring to as “complex” are incidents that involve multiple, disparate, notifications in your alert management platform. Perhaps these incidents are logically separated because the underlying systems or services were seen as less coupled than they turned out to be in reality.

Dear Trapped, Thanks for asking the question! Approaching observability as an all-or-nothing problem often leads to the project feeling daunting. But that’s not specific to observability—any project can be overwhelming if you think it needs to be done all at once, perfectly. Such as, erm, writing an entire book on observability! *looks around worriedly*

The world of cloud computing has been revolutionized by a solution called serverless computing. It has been an absolute joy for developers to use. Before this innovation, developers had to worry about the resources powering their code. Since the launch of serverless computing, the developer’s focus on operating-system and hardware architecture is now a thing of the past. It handles all the server management while focusing on what you do well — writing good quality code.

Datadog is one of the most highly rated tools for network monitoring, application performance monitoring & log analysis. The platform is highly rated by engineers for its wide range of useful features, high integrability and support of both custom configurations and reporting dashboards.

“If it ain’t broke, don’t fix it” is a popular quote for a simple reason: Changes can lead to unexpected results. Many network engineers have learned this lesson the hard way. Stories of admins who update firmware or configurations only to have network problems begin are common. Even big names in networking have been hit by change-induced network failures.

Every company is a software company and every company wants to get better at it. That’s the reason we built Software Development Optimization or SDO. SDO helps you track siloed data across the DevOps toolchain. It normalizes and correlates data, provides you with DORA’s 4 key metrics and gives you deep insights into the velocity and quality of delivery across services and teams.

IT is messy stuff. Enterprise applications and devices rely on a web of interdependent clouds, networks, and containers. IT operations (ITOps), development operations (DevOps), and cloud operations (CloudOps) engineers work hard to manage this mess. If they succeed, they create a stable, agile IT environment that makes their enterprise more productive. If they fail, their enterprise becomes less productive.

It’s that season of sharing, and in the spirit of sharing, we have a new feature to share with you — notebook sharing. Now you can take your favorite InfluxDB notebooks and share them with whoever you would like. They don’t need to have an InfluxDB Cloud account. They just click on the link you share with them, and they can see the notebook that you shared, for the time range that you selected.