June 18, 2025

Release 2.5.2 shipped on June 18, 2025.

Features#

New Billing#

• We are now using Stripe for payment gateway and subscription management for all new users. (existing paid users will have chargebee as their payment gateway as of now).
• This will bring better experience for users to add cards and manage subscriptions, add multiple payment methods and select primary methods and more options for payments.

Quickwit for RUM#

• Implemented quickwit for RUM to load data faster and for performance improvements.

New search UX#

• Updated search UX where you can search easily and edit the operator or label or searched text with a simple click.
• Improved the performance of search and suggestions—results now load faster as you type.

Agent Pipeline#

• Added two new processors: Attributes processors and compact processors for Metrics pipeline and Trace pipeline.

Improvements#

OpsAI#

• Now we give 2M free tokens as a limit for all free accounts to use OpsAI. Once the token limit is exhausted, our system won’t make new requests to AI providers to fetch results.
• Added new categories for error types (internal errors, misc error, dependency issues, gRPC errors).
• Merge in steps: now we root cause analysis and solution in a single step.

Infrastructure Kubernetes#

• Added timeline view inside workloads → deployments → deployment info.
• It helps to visualize data about pod status, workload availability, warning events and changes.
• Fixed the issue of data not loading inside the Events tab (Workloads → Deployments → Events) for timeline graph.

Workloads → Deployments → Map#

• Updated Map view with new UI for better and easy visibility

APM#

• Updated APM components with latest graphs and UI.

UX improvements#

• Metrics pipeline: Added an option to select multiple/all metrics to enable or disable it at once.

Error tracking alerts#

• Added an option to filter errors by attributes (ex: service name, browser name etc) to get customized alerts on any errors for front-end or backend.
• Fixed the billing alerts which were not working as expected. You can set alerts on usages and get notification if usage exceeds the threshold.