June 02, 2026

Cryostat 4.2.0 is Released!

---

Table of Contents

• Table of Contents
• Release Highlights
  • New Features
  • Feature Enhancements
• Where can I get the latest version of Cryostat?
• Feedback

---

Hello everyone,

We are pleased to announce that Cryostat 4.2.0 is now here!

Release Highlights

New Features

1. Support for JFR analytics: custom SQL queries can now be performed on archived JFR data without explicitly needing to download JFR files from Cryostat storage.
2. Smart trigger UI: provides a new Triggers view for managing smart triggers in the Cryostat web console. This view provides a way to declaratively configure the Cryostat Agent to start JFR recordings based on defined conditions. In earlier releases, the only available way to define smart triggers were by appending them to the agent's JAR file path or by using a JVM system property or environment variable.
3. Audit Logging: actions performed when interacting with Cryostat's API are now tracked. This is especially useful for Administrators wanting traceability and accountability of actions performed within Cryostat. This enhances the Archives views (Flight Recordings, thread dumps, heap dumps) enabling a detailed view of information about the target application an archived data file was sourced from, even if that target has since gone offline.
4. Async-profiler Integration: Attach the async-profiler.jar to your application and create profiling sessions to capture async-profiler event types.
5. Thread dump visualizations: Thread dumps can now be analyzed within the Cryostat console through list views and pie charts.
6. Cryostat Agent discovery enhancements: When using the Cryostat Agent in a Kubernetes or OpenShift context, the Agent instances will now appear nested within Pod, Deployment, ReplicaSet, and Namespace elements merged with any EndpointSlice-discovered targets.

Feature Enhancements

1. Harvester period and Harvester max file settings: cryostat.io/harvester-period and cryostat.io/harvester-max-files labels are now available and can be specified in the application's deployment.
2. Cryostat web console navigation menu enhancements:
   • The Diagnostics > Analyze > Thread Dumps view is renamed Diagnostics > Analyze > Thread Dump Archives in this release.
   • The Security > Certificates view now replaces the Certificates pane that was in the top-level Security view in earlier releases.
   • The Security > Credentials view now replaces the Credentials pane that was in the top-level Security view in earlier releases
3. "All Archives" and "Targets" tab for Heap and Thread dumps views : The Diagnostics > Analyze > Heap Dumps and Diagnostics > Analyze > Thread Dump Archives views in the Cryosat web console both now include an All Archives tab in addition to a Targets tab. Each of these All Archives tabs provides the same type of functionality and look-and-feel as the All Archives tab in the Flight Recorder > Analyze > Archives view.
4. "All Archives" table updates: Several usability updates were added to this table include filtering by time range or lineage and displaying fields such as Target Name and URL details.
5. POST Discovery endpoint: Plug-ins that are registered with Cryostat can now use a POST /api/v4.2/discovery API for sending requests to the Discovery POST endpoint. This new POST API supports the addition of a “fill strategy” in API requests, which can be set to either NONE or KUBERNETES. If the fill strategy is NONE, the POST /api/v4.2/discovery API provides the same behavior as the existing POST /api/v4/discovery API. If the fill strategy is KUBERNETES, this works in conjunction with a context map to determine contextual lineage data for a node in terms of its associated pod, replica set, deployment, namespace, and realm.
6. GraphQL API enhancements:
   • The targetNodes top-level query now includes a useAuditLog optional parameter, which is set to false by default. When this parameter is set to true, querying information about target applications that might have been previously discovered but subsequently lost is possible.
   • The DiscoveryNodeFilterInput now accepts jvmId, jvmIds and targetIds as search parameters for filtering discovery nodes.

For further details on these items, check the GitHub Discussions release announcement.

Where can I get the latest version of Cryostat?

You can install Cryostat using our Kubernetes operator on OperatorHub.io or via a Helm Chart . As always, you can also run Cryostat in other environments with a little more manual setup.

If this is your first time installing Cryostat on Kubernetes, you can Get Started right here on this website.

If you had previously installed Cryostat Operator 4.1.x with OLM, then you may have already been upgraded to 4.2.0, or else you should be able to approve and install the upgrade.

Feedback

Please reach out to the Cryostat mailing list or GitHub Discussion with any questions or comments.