Operations | Monitoring | ITSM | DevOps | Cloud

Coca-Cola is one of the most recognizable brands on the planet. That’s because wherever it’s produced, the quality, product, and design are the same. When three Coca-Cola companies merged in 2016 to create Coca-Cola European Partners, operational differences became apparent. The company needed a way to standardize platforms and processes across 13 Western European countries and 50 bottling plants. We had three systems in place, three ways of working, and multiple languages.

Grafana Labs was founded in 2014 to build a sustainable business around the open source Grafana project, so that revenue from our commercial offerings could be re-invested in the technology and the community. Since then, we’ve expanded further in the open source world — creating Grafana Loki and Grafana Tempo and contributing heavily to projects such as Graphite, Prometheus, and Cortex — while building the Grafana Cloud and Grafana Enterprise Stack products for customers.

When Grafana Labs CEO and co-founder Raj Dutt announced to the team that the company would be relicensing our core open source projects from Apache 2.0 to AGPLv3, he opened the floor for discussion and encouraged anyone who had further questions to reach out. We believe in honesty and transparency, so we collected hard questions from Grafanistas, and Raj answered them for this public Q&A. The time felt right. As I’ve said publicly before, I’ve been thinking about this topic for years.

A common challenge in data engineering is to combine traditional data warehousing and BI reporting with experiment-driven machine learning projects. Many data scientists tend to work more with Python and ML frameworks rather than SQL. Therefore, their data needs are often different from those of data analysts. In this article, we’ll explore why having a data lake often provides tremendous help for data science use cases.

Telecom companies monitor their network using a variety of monitoring tools. There are separate fault management and performance management platforms for different areas of the network (core, RAN, etc.), and infrastructure is monitored separately. Although these solutions monitor network functions and logic – something that would seem to make sense — in practice this strategy fails to produce accurate and effective monitoring or reduce time to detection of service experience issues.

Back in December, Amazon Web Services (AWS) and Grafana Labs partnered to launch the Amazon Managed Service for Grafana in a preview to a limited set of customers. Amazon Managed Service for Grafana is a scalable managed offering that provides AWS customers a native way to run Grafana directly within AWS alongside all their other AWS services.

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week we explore the rising scope of location intelligence in improving the overall customer experience.

Starting today, Honeycomb’s Management API is generally available to all Honeycomb users. The Honeycomb Management API is a set of endpoints that lets you programmatically set up, configure, and delete queries, datasets, derived columns, and more. With this release, you can now manage Honeycomb with configuration as code either directly via API or with third-party tools, like Terraform, using the community-contributed Honeycomb provider.

APIs are the backbone of software products. Whether the APIs are customer facing or for internal use, making sure that your APIs are up and running is crucial. In this post, we will see how to get started with API monitoring with Checkly.

Why we felt there was a need for a full stack open source observability platform and how we went about building it.