Skip to content

Optimizing logs

The Optimize Logs page is the heart of Obics for log cost. It shows your log noise as a ranked table of log groups (each row is a cluster of near-identical log lines collapsed into one pattern), ordered by how much they cost per month.

The Optimize Logs page with the tab bar, cost columns and trend sparklines

A row of tabs sits above the table. Each shows a count and, on some, a savings badge.

TabWhat it contains
ActiveThe current scan’s live findings: log groups still generating noise, with recommendations you can act on. The badge shows potential savings from this scan.
Fix ReadyLog groups where a fix has been prepared and a pull request is waiting to merge. Badge = estimated savings once merged.
Fix FailedFixes that were attempted but failed (only appears when there are any).
IgnoredLog groups you dismissed so they stop cluttering the Active view.
ResolvedFixes that landed and were marked resolved. Badge = realized savings.

(Ctrl+] / Ctrl+[ cycle the tabs.)

The Fix Ready tab, listing log groups whose fixes are waiting to merge with their saved bytes and savings

The Active tab shows, per log group:

ColumnMeaning
IDThe log group’s display ID.
ΔRank change versus the previous scan.
Log groupThe log message (sample or normalized template) with the matched source line beneath it in grey.
ServiceWhich service emits it.
Bytes/1dIngest in the 24h before the last scan.
Bytes/moProjected monthly ingest.
Events/moProjected monthly event count (millions).
Cost/moForecast monthly cost (ingest + indexing + events).
Max Savings %The best available saving from its suggestions.
First seen / Last seenWhen Obics first and last saw this group.
RetentionHow long this service’s logs are kept.
TrendA sparkline of recent volume.

The gear (Settings) button toggles columns and switches the Log group cell between the raw sample and the normalized template. Service-wide items are tinted green and can collapse under a service service-wide (N)” header.

Each log group carries one or more suggestions. The common types:

TypeWhat it proposes
Reduce VerbosityLower the log’s level (e.g. to debug) or gate it behind a flag.
Remove DuplicateDelete a log that duplicates another.
Reduce RedundancyTrim redundant fields or repeated content.
Aggregate LogsReplace many per-event logs with a periodic summary or counter.
Sample (HotPathLogs)Keep the log but emit only a fraction (e.g. 1%) on a hot path.
Custom InstructionA remediation you wrote yourself.

Every suggestion also shows a savings % and a Visibility Loss Risk badge (Low, Medium, or High Risk), so you can weigh the saving against how much diagnostic visibility you’d give up. An amber Side Effects badge means applying it also needs a change on the vendor side (like an exclusion filter).

Click any row to open its detail popup.

A log group detail popup showing Optimization Opportunities and ranked suggestions

At the top is a badge grid: Service, First/Last Seen, Volume/1d, Cost/mo, and more. Below are two inner tabs:

  • Optimization: an Optimization Opportunities paragraph explaining why this log is wasteful, then one card per suggestion (type, savings %, risk, the recommendation text, and action buttons). A + Add custom instruction box lets you write your own remediation.
  • Details: a 30-day Trend chart, the Template, Metadata, and Log in Code (a file:line link to the matched source location with a highlighted code snippet). A Drilldown section links to the log in your vendor and shows real Samples.

Arrows at the top (← / →) step through log groups without closing the popup, and the #ID / Share buttons copy a deep link.

From a row’s menu or the popup you can:

ActionEffect
OpenOpen the detail popup.
Quick FixApply the top suggestion immediately and create the fix.
Create PROpen a pull request for a chosen suggestion (see Applying fixes).
Move to ignore list / UnignoreHide or restore the group.
Copy promptCopy an AI prompt covering the suggestions.
Open PR / Open Work ItemJump to a created PR or linked ticket.

Selecting rows with their checkboxes reveals a bulk actions bar with Ignore and Quick Fix.

The top bar has a search box (free-text across log groups) and a Last seen filter (Within 1–90 days). The Ignored and Resolved tabs are all-time, so the recency filter is hidden there.

Next: Applying fixes and creating pull requests.