This is archived documentation for 1.1.0. Go to the latest version.
Version 1.2 release notes
The Grafana Enterprise Logs (GEL) team is excited to announce the release of GEL 1.2.
GEL 1.2 is built off of Loki 2.4, so it inherits all the features, enhancements, and bug fixes of the upstream project. Refer to the Loki v2.4 release notes.
Features and enhancements
GEL 1.2, like the upstream Loki 2.4, introduces a new deployment mode called a simple scalable deployment. In this mode, Loki is deployed as a collection of read nodes and write nodes. Read and write paths can be scaled and debugged separately, and without the complexity of a microservices deployment. Multiple replicas of the read and write nodes provide high availability for your logging service. An advantage will be no downtime when you upgrade.
GEL 1.2 eliminates the use of the word “instance,” which had been used as a synonym for “tenant”. Switching to “tenant” allows GEL to more closely align with terminology used in Loki and avoids confusion caused by the fact that “instance” can have multiple meanings besides “tenant.”
- All references to “instance” in the GEL documentation and GEL Grafana plug-in have been replaced with the word “tenant.”
- We’ve added new API endpoints which specify
tenantin the request and response bodies. We have deprecated and will eventually remove the original endpoints that use the word
We now have a GEL Helm chart for those interested in deploying on Kubernetes.
As part of the simple scalable deployment implementation, we updated the default values for configuration parameters. Those defaults are more in line with Grafana Labs’ recommendations for running the software. It also saves users from needing to update their deployed values, thereby shrinking their configuration size.
- For a full list of GEL v1.2 changes, see GEL releases.
- We do not anticipate any breaking changes due to the updated default values.
- If the
path_prefixflag is set in the
common_configsection, GEL will look for the license file in the
path_prefixdirectory. Users who already define the path to their license with the
pathflag in the
license_configconfiguration section will see no change in behavior. This flag, when set, takes precedence.
Metrics related to chunk storage and the runtime configuration have changed their prefixes from
loki_. If you have any dashboards or downstream logic built on these metrics, you need to update them.
1.2.0 bug fixes
Fixed a bug that broke leader election for the admin API. By default, leader election is on.
We corrected the URL of the ring endpoint for the GEL gateway. This fixes the ring page on the GEL Grafana plug-in.
Related Enterprise Logs resources
Grafana Enterprise Logs: Logging with security and scale
Join us for this webinar, which will cover: Challenges with logging as organizations scale and the volume of logs explodes, how Grafana Enterprise Logs enables organizations to make logs available to any team members who need them, features available in GEL and how to get access, a live product demo so you can see GEL for the first time
VIDEO: Watch this first-look demo of the new Grafana Enterprise Logs
Based on Loki, Grafana Enterprise Logs is part of the Grafana Enterprise Stack for composing and scaling observability on your own infrastructure.
Introducing Grafana Enterprise Logs, a core part of the Grafana Enterprise Stack integrated observability solution
Powered by the Loki open source project, the Enterprise Logs offering joins metrics and dashboards in our enterprise-ready stack for self-managed observability.