Cost Breakdown
Know Where to Cut
Pinpoint event types driving 80% of cost fromFluentd/Bit · OTel · Filebeat · Logstash · Splunk UF
Edge Reporter Workflow
Capture event costs before they ship. Works with your forwarders
Receive
Forwarder sidecar
Transform
Typed objects
Analyze
Cost breakdowns
Report
Publish metrics
Hover over each step to learn more
Frequently Asked Questions
Edge Reporter classifies every event by its event typeEach log event is automatically classified by its stable message structure — variable data stripped, pattern preserved:
Raw log event:[2025-08-01 22:19:30,905] INFO [controller-1-to-controller-registration-channel-manager]: Recorded new controller, from now on will use node 0.0.0.0:9093 (id: 1 rack: null) (kafka.server.NodeToControllerRequestThread)
Extracted event type:channel_manager_Recorded_new_controller_from_now_on_will_use_node_id_rack
Timestamps, IPs, and runtime values are stripped. The remaining structure becomes a cost-tracking key — no regex, no manual rules.
How message extraction works → — showing which types cost the most and where your log budget goes, broken down by type, severity, and application.
Runs as a shadow deployment alongside your log forwarder — monitors the live event stream without modifying, filtering, or redirecting any data. Analyzes events at the source, before they ship.
Most teams start here. Identify cost targets with Reporter, then act with Edge Optimizer (lossless reduction) or Edge Regulator (budget caps).
Edge Reporter runs as a sidecar process — completely asynchronous to your log forwarder. It never sits in the data path and adds zero latency to log shipping.
Reporter provides visibility — it shows where every dollar goes by classifying events using pre-compiled log templates from your source code.
The Console's AI analysis uses your cost metrics to generate specific optimization recommendations — which event types to regulate, where optimization has the highest ROI, and what to prioritize first.
To reduce costs, pair Reporter with:
- Edge Optimizer — 50%+ lossless volume reduction
- Edge Regulator — budget caps to prevent overspend
Most teams deploy Reporter first, identify targets, then add optimization within a week.
Edge Reporter deploys in your infrastructure — no data leaves your network. Add a tenx blockEdge Reporter — Helm values:tenx:
enabled: true
apiKey: "YOUR-LICENSE-KEY"
kind: "report"
runtimeName: my-edge-reporterFluent Bit · Fluentd · Filebeat · OTel Collector · Logstash · Splunk UF · Datadog AgentFull deploy guide → to your existing forwarder Helm values and run helm upgrade. For VMs, the CLI and Docker options take under 5 minutes.
Know What Costs Most
CLI · Docker · KubernetesWorks with any forwarder


