Metrics cost
Reduce time series that nobody queries.
Well-named metrics, with just the right dimensions and cardinality under control.
One extra dimension on a metric can multiply its time series and its cost without adding anything. And metrics with different names for the same thing make it impossible to compare services.
Five phases, always in the same order. Select each one to see what happens in it. In full projects they map onto the stages of our method.
We review what's monitored today, with which tools, which incidents went unnoticed and what it costs.
We design the collection layer with OpenTelemetry: agents, gateways, egress paths, common attributes and sampling.
We apply naming conventions, aggregation rules and custom metrics.
We compare cardinality before and after and confirm that dashboards and detectors still work.
We tune cardinality, sampling and detectors based on real usage to contain cost and noise.
Reduce time series that nobody queries.
Measure orders, sign-ups or payments alongside the technical ones.
Get every team measuring the same thing the same way.
The number of distinct time series a metric generates based on its dimensions. It's one of the main cost drivers.
We only drop the detail nobody uses; we check that against real usage first.
Yes, Splunk APM generates metrics from traces that can be used in dashboards and detectors.
Tell us about your situation. If this service is not what you need, we will tell you; if it is, we will propose a concrete first step.
Request this service