Operations | Monitoring | ITSM | DevOps | Cloud

Burnout in the workplace can tarnish careers and negatively impact work-life balance. And as our work environment becomes increasingly more remote, people are starting to re-examine the modern problems of burnout at work.

Close your eyes and breathe slowly, can you already feel the coolness on the tips of your boots? On the tense phalanges of your hands? The first step is right in front of you. It is a spiral staircase armed with worn ashlars under old voussoirs. The dim light of a chandelier accompanies you. What are you waiting for? Go up! The forbidden book awaits you in the last of the stays, where you will finally find out something about the history of monitoring.

Cloud API logs are a significant blind spot for many organizations and often factor into large-scale, publicly announced data breaches. They pose several challenges to security teams: For all of these reasons, cloud API logs are resistant to conventional threat detection and hunting techniques.

What precisely are the requirements of a DevOps practitioner, as opposed to an SRE, legacy developer, or operations manager? And do those specific requirements require a different approach to monitoring?

When the Domain Name System (DNS) was created in 1983 I imagine its creator Paul Mockapetris and his team had no idea that nearly 40 years later our interconnected world would be so reliant on the very simple, but critical, DNS network service. I have a love-hate relationship with DNS. I love all of the memes I see about how “It’s always DNS”, but I hate that it’s also true—I always forget to check that DNS is working correctly when troubleshooting network issues!

As an on-call engineer, you might deal with the day-in, day-out occurrence of alerts. These alerts may come from your alerting provider (PagerDuty, OpsGenie, etc.), Slack notifications telling you the site is down, or the ever concerning text message "Hey, is the site down?". These alerts elicit reactions that range from "shit" to "again?" and in many cases, both.

We are seeing a renewed focus on accelerating digital transformation projects across business ecosystems and workflows within our customer base. These projects are enabling key business outcomes and this organizational transformation has given security and IT leaders the catalyst and opportunity to modernize security operations while eliminating on-premises debt.

If you feel intimidated by Kubernetes’ complexity but still need to modernize your business applications with containers, rest assured you’re not the only one. The container orchestration platform solves many problems but also creates new ones, so read on to find out about a new approach that can help you get just the benefits.

Many enterprises use open source enterprise support from a vendor, such as Red Hat or Canonical, to boost uptime and peace of mind. Others choose to use open source without any additional vendor support, relying on one of the major benefits of open source – the robust community support that is freely available.

If you’re familiar with Telegraf, you know that you can easily configure this lightweight collection agent with a single TOML configuration file to gather metrics from over 180 inputs and write data to a wide variety of different outputs and/or platforms. You might also know that Telegraf can act as a processor, aggregator, parser, and serializer.