Operations | Monitoring | ITSM | DevOps | Cloud

As systems become more complex and distributed, the total amount of machine data put off by those systems continues to skyrocket. While teams may need access to an ever-increasing scope of machine data to gain insights into their increasingly complicated systems, that same need to access an increasingly large amount of data also creates cost concerns. Those concerns can grow into cost emergencies quickly.

Given the strategic importance of the cloud and size of cloud expenditures, it’s critical for enterprises to have solid controls in place to manage it all. According to our latest research, however, while most organizations agree with that sentiment, very few have put it into practice. There are distinct but related disciplines that come into play: FinOps and cloud governance. In this two-part series, we explore current state of each.

For this post, we’ll use a small Flask app that allows users to input a city name and they receive the current weather information for that city. We’ll make an API call to openweathermap.org to get the weather information for the city.

Back in late May, we hosted a webinar on the heels of our Series D funding announcement where we also took the wraps off our big product announcement: Cribl Search.

The U.S. Army Combat Capabilities Development Command (DEVCOM) Army Research Laboratory (ARL) faces unique challenges in working with data to develop new technologies. It needs the ability to seamlessly analyze data both in the field and in the lab. Connectivity in the field can also be very unpredictable. Without a database that can handle intermittent connectivity, the systems become inefficient and waste time and money.

Honeycomb ruffled the first of many feathers nearly seven years ago when we coined the term “observability” in talking about production code. Today, we get to celebrate a major victory in our push for the term to break free from its unsuitable parent category, Application Performance Monitoring (APM).