Operations | Monitoring | ITSM | DevOps | Cloud

Analytics

Power your Puppet reports with PowerBI in 10 minutes

Every Puppet practitioner can appreciate the wealth of information stored inside PuppetDB. Although Puppet Enterprise console offers some insights into the data, we sometimes need rich dashboards, possibilities to correlate data about facts, nodes and reports and drill-down features. In short, we wish there were a way to unleash the full power of PuppetDB data to create situational awareness about our estate. This article will show that PowerBI is a very powerful companion to PuppetDB.

Improving Application Quality through Log Analysis

Throughout the history of software development, one statement has remained true: no application is perfect. Due to that fact, development organizations must work with all resources at their disposal to limit the impact that application problems have on the end-user. Server log files represent an important resource that should be referred to during the process for troubleshooting any application issue.

Importance of System Resource Monitoring on Graylog, Elasticsearch, and MongoDB Servers

The first thing we tell Graylog users is, “Monitor your disk space.” The core set of metrics discussed below should always be in acceptable parameters and never grow over extended periods without going back to normal levels. This is why it is critical to monitor metrics that come directly from the hosts running your Graylog infrastructure.

Community Highlight: How Supralog Built an Online Incremental Machine Learning Pipeline with InfluxDB OSS for Capacity Planning

This article was written by Gregory Scafarto, Data Scientist intern at Supralog, in collaboration with InfluxData’s DevRel Anais Dotis-Georgiou. At InfluxData, we pride ourselves on our awesome InfluxDB Community. We’re grateful for all of your contributions and feedback. Whether it’s Telegraf plugins, community templates, awesome InfluxDB projects, or Third Party Flux Packages, your contributions continue to both impress and humble us.

Kibana platform migration: Lessons in large scale cross-team collaboration

When Kibana 4.0 was created back in 2015, it only had three apps: Dashboard, Visualize, and Discover. Fast forward five years, Kibana now consists of 100+ plugins, millions of lines of code, thousands of dependencies, and dozens of frameworks. The architecture of Kibana that worked well with three apps had become a bottleneck that was hindering Kibana’s stability, scalability, performance, and development velocity.