May 2024
Last updated
Last updated
Release Date: May 30, 2024
Affected Sections: Logs, Traces, K8s Events
Today we introduce the ability to customize your data retention policies for logs, traces, and Kubernetes events, based on specific properties.
This means that two datasets of the same kind can now also have two different retention periods. As an example, you can choose to retain error logs from cluster X for 30 days, while retaining non-error logs for the cluster for only 7 days.
This new capability offers complete flexibility and enhanced control over the management of your monitoring data.
Key Benefits
Cost optimization - gain total control over your data retention policies, so you can change the retention periods of specific data anytime to reduce the cost of your data storage.
Compliance requirements - align your data retention periods to your industry's requirements and/or organization's internal policy.
To learn more, check out our full details and configuration instructions.
Release Date: May 27, 2024
Affected Sections: All
We are thrilled to announce a significant enhancement to our observability platform: the ability to select multiple clusters and investigate all their data in a single, consolidated view. This new capability allows you to simultaneously monitor as much of your environment as you choose, providing a more comprehensive picture and saving considerable time.
Key Benefits:
Unified, holistic monitoring experience for better troubleshooting: Quickly identify and resolve issues that appear in multiple clusters, reducing resolution times (MTTR) and ensuring smoother operations.
Enhanced data analysis and insight correlations: Correlate data across clusters to bring up patterns, dependencies, and performance bottlenecks that might not be as easily noticeable when monitoring each cluster individually.
Use cases:
Side-by-side comparison of DEV, STG, and PROD environments: Understand if an issue is present in one or more of your development phases by viewing your development, staging, and production environments all in one view.
Regional issue identification: Save time by quickly identifying issues that show up in multiple regions by monitoring regional clusters simultaneously.
In addition to selecting individual cluster names, you can now also create custom environment labels. This helps you group together multiple clusters that share the same purpose or have any common denominator.
As an example, you could add the custom label "DEV" to all clusters that make up your dev environments.
Once custom environment labels are added, you will see them as part of the drop-down menu. Selecting a label will show data for all the clusters that share that label.
Learn how to add custom environment labels
Release Date: May 22, 2024
Affected Sections: Logs
Major enhancements to our Logs search engine which will improve your experience and shorten your investigation time!
Our enhanced logs search engine now offers faster search capabilities. We have optimized the search process, enabling quicker and more efficient retrieval of log data. This means you can now pinpoint the information you need in a fraction of the time, enhancing your productivity and streamlining your workflow.
We've introduced wildcard support in our search engine, making it easier than ever to find partial matches. This feature enables more flexibility in your searches, helping you locate specific log entries even when you only have partial information. Whether you're troubleshooting an issue or analyzing patterns, wildcard queries provide a powerful tool to enhance your search capabilities. Read more about how to apply wildcards to your logs searches here.
Stay tuned for more exciting updates, and as always, we invite you to share your thoughts with us in our Slack community!
Log in to start using these new and improved logs search engine capabilities.
These new capabilities are optimized for v1.7.84 or later. Learn how to groundcover to the most recent version.
