Earlier this month, Elastic announced that there would be upcoming changes to its open source licensing. These changes do not affect on-prem deployments of Elasticsearch. Since Mattermost Enterprise Edition uses Elasticsearch in its on-prem deployments, we felt it important to explore the reasoning behind Elastic’s decision, how the new license terms are different, and why there will be no impact on Mattermost users as a result of these changes.

Today I’m happy to announce that observIQ’s Stanza Log Agent will become a key part of the OpenTelemetry project. This has been in the works for many months and the team at observIQ is thrilled to see it becoming a reality. We’re particularly pleased to see it happening just as we launch our log management platform which will be the first platform to take full advantage of the log agent technology now incorporated into OpenTelemetry.

Earlier this week, I wrote a blog stating our intention to fork Kibana and Elasticsearch. This was a huge decision on our end, one that we did not take lightly. A few days have passed since this announcement and I wanted to share how humbled and excited we are with the responses from companies and individuals who are eager to participate and contribute.

A couple of days ago, Elastic announced that it will change the licensing of Elasticsearch and Kibana as of the 7.11 release to a proprietary dual license (under the SSPL license) and away from the open-source Apache-2.0 license. This move has caused extensive turmoil and frustration in the open-source community, especially with organizations that rely on Elasticsearch. Let me start with the end in mind.

We are moving our Apache 2.0-licensed source code in Elasticsearch and Kibana to be dual licensed under Server Side Public License (SSPL) and the Elastic License, giving users the choice of which license to apply. This license change ensures our community and customers have free and open access to use, modify, redistribute, and collaborate on the code.

Open source has come a long way. One of my favorite reports on the subject is Red Hat’s State of Enterprise Open Source. For 2020, 95% of respondents said that open source is strategically important to their business needs. Here, I will be recapping my recent Illuminate presentation about embracing open source data collection and I thought it’s important to first talk about how open source has changed.

18 months ago, Redgate embarked on a new and ambitious journey with the acquisition of Flyway. It’s been quite a ride since then and we thought we’d end 2020 with an update on what’s been happening with the world’s most popular open source migrations framework for database deployments. We’ve learned a lot, and I wanted to share that with you in this post.

Prometheus is an essential element in DevOps. It has one of the largest contributor communities in the open source world and is the favorite database for time-series metrics data. It is also part of Logz.io’s complete observability package, which integrates open source grafana, Jaeger, and ELK Stack into one platform. It’s a favorite for system and container monitoring. This tutorial will show you how Prometheus works with Docker and your local machine.