See what your team's Claude Code, Codex, and OpenCode agents are doing and what they cost. Data lands in your own S3 bucket through a standard OpenTelemetry integration.
Grepr works out an application’s distinct trace paths on its own, separating a cache hit from a backing-store call so tail sampling can be aggressive without hiding a slow tier.
Grepr collapses 586 repeats of the same log pattern into a single Datadog event, cutting the stream by 99% while the raw logs stay queryable in S3.
Redact PII from your logs using the Grepr CLI, the Claude Code plugin, and Terraform, so the fix is tested against live traffic before it ships and stays managed as code.
The safe way to change a Grepr pipeline: prepare and test the change in the UI, then apply it through Terraform so your configuration stays consistent as code.
Starting from a pipeline built in the Grepr UI, the full round-trip of exporting it, importing it into Terraform state, and managing changes as code.
Get back the analyses that log summarization removes by querying the full raw data in your Grepr data lake with the Grepr CLI and the Claude Code plugin.
Run analytical queries over the data in your Grepr data lake, directly from the UI. This walkthrough shows how to ask analytical questions of your logs in the Analyze view, without writing SQL or backfilling into your observability tool.