What's New in Graylog 6.0? | WED, MAY 22, 11am ET | Webinar >> ​

Graylog is excited to announce Graylog v4.2. This release includes new integrations for Google Cloud, Workspace, and Mail logs, OpenID Connect, and other key enhancements that create more efficiencies in your approach to centralized log management.

Read on for more details about the new release.


Tarballs (manual installation):

Please report bugs and any other issues in our GitHub issue tracker. Thank you!


Graylog has extended our authentication methods to include OpenID Connect, aka OIDC. If you use any of these third parties — Auth0, Azure AD, Google, Keycloak, Ping Identity, and OneLogin — you can connect to Graylog using OIDC.  NOTE: Duo, Microsoft ADFS, and Team Sync are not currently supported using OIDC. OIDC does support Okta, however, we recommend that you use our dedicated Okta authentication support for your Okta authentication needs. Also, our Okta authentication does support Team Sync.


Graylog Enterprise has brought Google Cloud Services into the fold. These new inputs allow you to gather your Google Cloud, Workspace, and Mail logs into the Graylog ecosystem, making them a part of your centralized log management activities.



Graylog v4.2 comes with a new UI for installing Illuminate core, processing, and pipelines. This automated installation process takes care of everything under the covers — i.e., it updates Elasticsearch templates, installs new processing pipelines and rules, installs new CSV lookups, and syncs the Illuminate installation across all nodes in your cluster. Illuminate installation is now a matter of uploading the Illuminate bundle via the UI and then selecting the processing pipelines you want to be active. A few clicks and you’re ready to unpack your Spotlight content and get to logging. Note that the installer does not currently manage certain Spotlight content such as dashboards and alerts.


Okta on-prem — Adding a Custom Authorization Server (Enterprise)

Graylog now offers the flexibility to use your own custom Okta endpoint for authentication rather than the default Okta endpoint.

Storing Indexing/Processing Failures (Enterprise)

When a message fails, you need to know why. Graylog now makes this process fast and efficient through a new separate dedicated stream that shows the messages that failed when indexing. This makes it easier to see the problem, identify the issue, and resolve it quickly. An added benefit to this enhancement is that you can create alerts for indexing/processing failure messages, and you can download, save, and archive the failed messages for future review.


Let us know what you’d like to have included in our GitHub issue tracker.

Get the Monthly Tech Blog Roundup

Subscribe to the latest in log management, security, and all things Graylog blog delivered to your inbox once a month.