Operations | Monitoring | ITSM | DevOps | Cloud

Since Grafana started 10 years ago, there have been more than 43,000 commits to the open source project. Grafana founder Torkel Ödegaard has made more than 7,600 of those commits, and he recently reflected on some personal favorites he’s worked on, ranging from early query builders to the latest navigation updates. Torkel isn’t the only one who has strong feelings.

DevOps engineers are under intense pressure to provide reliable, high-quality services to teams and stakeholders. In large part, this is because end users today demand seamless access to software and a great user experience – a trend that will only increase as digital transformation accelerates and we move further into the future. DevOps professionals rely on various metrics to meet performance and reliability goals, one of the most important being service level objectives (SLOs).

If you are trying to figure out how to measure the performance of your application, you are in the correct place. We spend a lot of time at Stackify thinking about application performance, especially about how to monitor and improve it. In this article, we cover some of our most important application performance metrics you should be tracking.

You may be thinking, “What on earth is an observability pipeline? And how does the Super Mario World fit in?” Hold on to your hat, my friend, because you’re about to find out!

Logs are like gold ore. They have valuable nuggets of information, but those nuggets often come in a matrix of less helpful material. Extracting the gold from the ore is crucial because it is vital to unlocking insights and optimizing your system(s). Raw logs can be overwhelming, containing informational messages, debug statements, errors, etc. However, buried within this sea of data lies the key metrics you can use to understand your applications' performance, availability, and health.

InfluxDB vs Thanos: Overview, Pros and Cons, and Differences.

Since 2020, the Intel team has been contributing to Telegraf, including both telemetry from Intel-specific platform features (such as Intel® Resource Director Technology, Intel® Dynamic Load Balancer, or power statistics from Intel-based platforms) and telemetry gathered from generic tools and frameworks; for example, Data Plane Development Kit (DPDK), Libvirt, P4 Runtime, or Reliability Availability Serviceability (RAS).

Hey there! We're excited to share a new troubleshooting feature we have added to Netdata, the Netdata Assistant. We've built this tool to help you troubleshoot more effectively and with less stress. Let's dive in.

Today’s guest blog is by Mike Stem­le, a software engineer and Principal Architect for the Ar­c XP di­vi­sion of the Wash­ing­ton Post. In his role, Mike focuses on AppSec and large-scale architecture. Any­body who works with me knows that I love the Data­dog Service Catalog.

Imagine you have a network, whether it's a LAN or a vast enterprise-level network spread across different locations. Now, picture yourself wanting to monitor and analyze the data flow within that network. That's where network telemetry comes into play. Network telemetry is a group of techniques that allow you to understand better what's happening within networks. It's like watching the network's pulse to keep track of its health and performance. Read on to learn more about the network telemetry landscape.