Release notes for June 2026
Grepr released these feature updates, improvements, and bug fixes in June 2026.
June 30, 2026
New feature: Uniform trace head sampling and standalone span head sampling
You can now set a single trace head sampling rate that retains whole traces together, and span head sampling now works even when tail sampling is not configured. Your existing trace pipeline configurations continue to load unchanged. See Use head sampling to sample traces.
Bug fix: The attribute remapper showed incorrect defaults for JSON parsing
When configuring the remapper in the pipeline UI, the option to preserve the original JSON message field defaulted to off even though the processing engine kept it on, and the list of reserved service attributes was incomplete. The remapper form now shows the correct defaults, so your saved configuration matches what actually runs. See Remap JSON attribute fields to top-level log event fields.
June 29, 2026
New feature: Expanded query language support in Log Explorer
Log Explorer now translates your searches through an upgraded query engine that provides more consistent and complete support for query syntaxes, including Datadog-like syntax and New Relic log query-like syntax. This engine adds support for numeric tag comparisons, such as port:>8000, and lexicographic string tag comparisons, such as service:>cloud, where values are compared alphabetically.
New feature: Pipeline sources redesigned as cards with a guided agent setup
Pipeline sources now appear as integration-style cards instead of a table, and a new Agent Setup Guide walks you through connecting agents using a public or private ingest endpoint, including inline AWS PrivateLink setup. You can copy ingest URLs directly from the source and integration cards, with OTLP tokens handled securely so they never appear on screen.
New feature: Critical path analysis for traces
You can now enable critical path analysis on a trace reducer to see how much each span contributes to a trace’s end-to-end latency. The results appear as new span fields that you can query in the data lake, pass through to downstream vendors as span attributes, and see highlighted in the Trace Explorer waterfall view. Critical path analysis is opt-in per pipeline and supports sampling and a maximum span count to help you control cost. See Analyze the critical path.
New feature: Trace Explorer critical path and trace view improvements
Trace Explorer now has a dedicated Traces tab alongside Signatures and builds trace and signature aggregates incrementally as spans load, so the view stays usable while data streams in. Traces whose loaded spans are missing the root span are now flagged instead of borrowing metadata from a child span, and the detail panes, waterfall, flamegraph, and critical path displays are easier to read.
New feature: Convert spans and logs to Datadog custom metrics with SQL
You can now define a SQL operation that turns spans or logs into custom metrics and sends them to Datadog. Each numeric column your query produces becomes a metric, tagged with the dimensions you select, so that you can build per-service or per-operation gauges directly in your trace pipeline. See Transform spans and traces with SQL.
New feature: Remove keys from maps and variants in SQL transforms
The new SQL functions MAP_REMOVE_KEYS and VARIANT_REMOVE_KEYS let you drop specific keys from a log event’s tags map and remove properties from VARIANT attributes on logs and spans. Use them to strip unwanted or sensitive attributes before your data is sent downstream. See VARIANT functions: query, extract, and transform values and Collection functions.
New feature: Original metric series preserved for anomalous objects
When an object triggers a metric anomaly rule, Grepr now re-emits its original raw series alongside the aggregated cohort output, so you keep full-resolution data for the objects that matter. You can configure the metric name suffix used for the passthrough series.
New feature: Improved time range picker for pipeline metrics and Log Explorer
A single, more capable time range picker now powers both pipeline metrics and Log Explorer. You can type relative ranges such as 4h or 45m, enter absolute windows, and adjust individual date parts with the arrow keys. Your selected range is preserved as you move between the pipelines list and the pipeline detail pages.
New feature: Updates to charts and pipeline metric cards improve usability
Charts across the app now share a unified look, and pipeline metric cards have more consistent titles, spacing, and typography, making them easier to read at a glance.
June 22, 2026
New feature: Copy resource IDs across the app
You can now copy the IDs for your user account, pipelines, and integrations directly from the UI with a copy button, and administrators get a new User ID column in user management. This makes it easier to get the identifiers you need for API calls and support requests.
New feature: Backfill logs to OpenTelemetry destinations
You can now select an OpenTelemetry integration as the destination for a logs backfill job. Previously, backfill jobs were not supported with an OpenTelemetry integration and would return an error message.
June 17, 2026
New feature: Create log pipelines with a guided wizard
You can now use a guided wizard that walks you through each step of configuring and creating a log reduction pipeline. The wizard is the default flow when you create a log reduction pipeline, but you can switch to the advanced configuration editor at any point as you go through the pipeline creation steps.
June 13, 2026
New feature: Preview the job graph diff before submitting a pipeline
When you edit or create a pipeline, you can now review a diff of the exact job graph that will be submitted before you confirm the changes. The confirmation dialog includes a side-by-side or unified view, an option to show unchanged lines, and a baseline version picker to compare the pending change against any earlier pipeline version.
New feature: Copy a ready-to-use OTLP ingest URL with your token
You can now copy a complete OTLP ingest URL with your integration token already filled in, from both the pipeline source view and the integration card menu. The token is fetched on demand when you copy so that you can paste the URL directly into an OpenTelemetry agent configuration. Retrieving the token in clear text requires the Edit integration permission and is recorded in the audit log as a security event.
New feature: Time range picker on the integrations page
The integrations page now has a time range picker in the top bar that lets you change the time range for integration metrics displayed on the integration cards, replacing the fixed per-card ranges. The picker uses the same presets and custom-range input as the pipeline overview pane on the pipeline details page, with a default range of 15 minutes.
New feature: Filter spans by trace ID in the trace explorer
You can now filter spans by trace ID in the trace explorer. Add a traceId: term to your query, including grouped values such as traceId:(a OR b), or pass a traceId URL parameter to open the explorer with the filter already applied.
Bug fix: Invited users could sign in with the wrong role
An issue where accepting an invitation could intermittently sign users in with baseline Member permissions instead of the role they were invited with has been fixed.
Bug fix: Logs from a SQL operation connected to the data lake were routed incorrectly
An issue in which logs from a SQL operation with output connected to the Data Lake step were routed incorrectly in the pipeline job graph has been fixed. The output now correctly reaches the data lake sinks and continues through the step that follows the data lake.
Bug fix: CLI list sorting was ignored for machine-readable output formats
An issue where the --sort option on the CLI list commands was applied only to the default table output and ignored for the raw, csv, pretty, and compact formats has been fixed. Sorting is now applied consistently across all output formats.
June 10, 2026
New feature: View pipeline metrics during transient and stopped states
The pipeline overview now shows metrics while a pipeline is in a transient state, such as updating, restarting, or starting, and for stopped pipelines, instead of showing a loading spinner or an empty state. The pipeline’s status also appears in the top bar on the pipeline overview page.
June 4, 2026
New feature: Syntax highlighting for filter queries
Query summaries on the pipeline filter page now render with the same query-language syntax highlighting used elsewhere in the UI, making queries easier to read. This update also fixes an issue where a # character in a query, such as #011, was treated as the start of a comment, greying out the rest of the query.
New feature: Plan, validate, and apply edits to pipelines with the Grepr CLI
You can now use the CLI commands job:plan, job:draft, and job:apply to plan, validate, and then apply changes to your pipelines. Using these commands, you can plan and test pipeline changes before you apply any changes to a production pipeline. When you’ve finished validating your changes, you can apply the changes to the production pipeline. See Preview and validate pipeline changes before applying them to production.
Bug fix: Pipeline cards reordered when a pipeline changed state
An issue in which pipeline cards on the pipelines page were reshuffled whenever a pipeline changed state, such as during updates or restarts, has been fixed. Cards are now sorted alphabetically with stopped pipelines last, and only move when a pipeline is created, deleted, started, or stopped.
Bug fix: Misleading pipeline action notifications
An issue where pipeline start, stop, and save notifications could report that an action had completed before it actually finished has been fixed. Starting and stopping a pipeline now show an in-progress message, and saving shows that changes are being applied only when a redeploy is triggered.