Release notes for May 2026
Grepr released these feature updates, improvements, and bug fixes in May 2026.
May 9, 2026
Filter, exclude, or copy any field directly from log details
When you open the details of a log in Log Search, every tag tile and every field in the JSON tree now has an actions menu. From the menu, you can add a filter for the value, exclude the value, replace the current search, or copy the field or key-value pair to your clipboard. The generated filter is rendered in the query language you currently have selected, so you see the exact fragment that gets added to your search. Filters apply immediately to the results without requiring a backend round trip.
Faster pattern matching for log reduction
Log-reducer pipelines now use a higher-performance pattern matcher by default when masking and tokenizing log messages. You may see higher throughput and lower CPU usage on log-heavy workloads after this release, without any configuration change.
May 3, 2026
New feature: Fetch Grepr platform metrics with a Prometheus-compatible endpoint
Grepr now provides an endpoint that exposes platform performance metrics in the Prometheus and OpenMetrics text exposition formats. You can scrape this endpoint with any monitoring tool that supports either format to monitor your Grepr pipelines alongside your other infrastructure. To learn more about configuring metric scraping, see Monitor performance metrics.
New feature: The new Reader role provides finer-grained access control to Grepr resources
Grepr now includes a built-in Reader role for users who need view-only access to organization resources. Reader role users can query logs and view resources, but cannot create, edit, or delete resources, and cannot run backfill jobs that send data to vendor integrations. See Manage users in the Grepr platform.
New feature: Allow users to run backfill jobs without granting full access to integrations
You can use the new write:integrations permission to grant users permission to send data through an integration configured as a pipeline sink. Use this permission to allow users to run backfill jobs through an integration without granting further permissions on the integration. See Permissions in the Grepr platform.
New feature: Upload log files in the pipeline log viewer
The pipeline log viewer now supports uploading log files as an alternative to streaming live data. To test your pipeline configurations with sample data, you can upload files in JSON or plain text formats, and log files up to 10 MB in size. This is useful for validating pipeline behavior against known datasets without sending live data. See View pipeline data flows and test changes with live edit.
New feature: View vendor sink HTTP delivery status on the pipeline overview
The sinks page in pipeline overview pages now displays a stacked bar chart showing HTTP response status codes from requests to vendor platforms, grouped into 2xx, 4xx, 5xx, and other responses. This makes it easier to identify delivery issues with your downstream observability platforms.
New feature: Combined CPU utilization and CPU hours on the pipeline overview
The pipeline overview page now displays CPU utilization and CPU hours together in a single CPU card. The card includes a filled-area chart of vCPU usage with the total CPU hours displayed in the header, along with a help tooltip describing both metrics.
New feature: Log explorer improvements
The classic log explorer view has been removed, leaving only the updated view with instant filtering. The maximum result count is now capped at 25,000 to prevent browser performance issues with larger result sets. Additionally, table headers in the log explorer now render correctly in dark mode.
Bug fix: Log status remapper did not accept numeric severity values
An issue where the log status remapper did not accept numeric severity values from OpenTelemetry sources and JSON loggers has been fixed. The status remapper now accepts numeric severity values that follow the OpenTelemetry severity numbering scheme, from 1 through 24.
Bug fix: OpenTelemetry attribute keys containing dots were incorrectly split
An issue in which OpenTelemetry attribute keys containing literal dots, such as foo.bar, were incorrectly split into nested key-value lists during the OTLP round-trip has been fixed. Attribute keys are now preserved as-is.
Bug fix: Premature logout when accepting an invitation
An issue where accepting an invitation could log you out before your account was fully provisioned, leaving you without permissions, has been fixed.
Bug fix: Spurious 403 errors during concurrent role updates
An issue where authorization checks could return spurious 403 errors during concurrent role updates has been fixed.