Operations | Monitoring | ITSM | DevOps | Cloud

Netdata is launching its Discord server

It’s been a long time since our last community update, rest assured that we have been hard at work here at Netdata. Community building is hard, especially when you have such a venerable community like the one here at Netdata, where hundreds of contributors have contributed to creating one of the best monitoring solutions that exist. Last year we started to concentrate working on consolidating the community by integrating the various platforms where people come together to talk about Netdata.

Kubernetes monitoring and troubleshooting made simple

Infrastructure monitoring was difficult enough when entire businesses ran off a few bare metal servers in a dusty, forgotten closet. Other IT infrastructure monitoring tools fell short, unable to provide complete and granular-enough metrics in real time, even when we were only dealing with a handful of systems responsible for running every part of the application stack.

Container deployment showdown: Docker or Kubernetes?

Monitoring the current state and performance of applications is critical for IT Ops and DevOps teams alike. Understanding the health of an application is one of the most effective ways of anticipating potential bottlenecks or slowdowns, yet it’s one of the largest challenges faced by many organizations that build and deploy software. This is largely due to applications’ distributed and diversified nature.

Start Kubernetes monitoring in 5 minutes with Netdata

While Kubernetes (k8s) might simplify the way you deploy, scale, and load-balance your applications, not all clusters come with "batteries included" when it comes to monitoring. Doubly so for a monitoring stack that helps you actively troubleshoot issues with your cluster. You need robust Kubernetes monitoring, but you don’t want to spend a week setting it up, much less a single valuable day.

5 DevOps best practices to reinforce with monitoring tools

As part of a modern software development team, you’re asked to do a lot. You’re supposed to build faster, release more frequently, crush bugs, and integrate testing suites along the way. You’re supposed to implement and practice a strong DevOps culture, read entire novels about SRE best practices, go agile, or add a bunch of Scrum ceremonies to everyone’s calendar.

Introduction to StatsD

StatsD is an industry-standard technology stack for monitoring applications and instrumenting any piece of software to deliver custom metrics. The StatsD architecture is based on delivering the metrics via UDP packets from any application to a central statsD server. Although the original StatsD server was written in Node.js, there are many implementations today, with Netdata being one of them.

Actionable alerts with fewer false positives: intelligent alarms with Netdata

Think about any sport or competitive activity, whether that’s football or a spelling bee. They always feature at least one person who acts as a moderator, referee, or judge. With their domain expertise, this person watches everyone’s behavior and constantly compares that against a set of rules. If someone crosses that threshold, they blow a whistle or throw up a flag. They are, in effect, saying that things have gone from OK to not OK.

Creating your first health alarm in Netdata

The per-second metrics and interactive visualizations in the Netdata Agent don’t mean much if you don’t know what you should be looking at, or whether anything is going wrong on your node in the first place. That’s why Netdata has a built-in health watchdog to notify you when metrics show an anomaly or full-blown incident that demands your immediate attention. Every Netdata Agent comes with hundreds of preconfigured charts that you don’t need to edit in order to take advantage of, but you may want to create your own based on your infrastructure, node, workload, or applications.