Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit Bucket Histograms, allowing users to efficiently capture and transmit distributions of measurements and compute statistical calculations like percentiles without increasing costs. Explicit Bucket Histograms empowers users with unparalleled analytical capabilities as they can now seamlessly ingest, store, and query histograms.
Native histogram support in Observability Cloud means users will no longer have to run special infrastructure to pre-aggregate their percentile data, which could incur additional costs and obscure source data. Natively ingesting histograms also eliminates the need to send and store each unique observation, which could prove costly, especially for cloud-forward enterprises.
Histograms, as defined by OpenTelemetry, give users a cost-effective way to send data to Splunk Observability while maintaining the flexibility to analyze performance data in real time. Histograms combine data for the min, max, sum, and count of a population along with a set of buckets that allow end users to compute percentiles. Because of the increase in data represented by a histogram, a histogram MTS will be equivalent to 8 standard MTS. Billing reports will track customers’ total usage and new metrics will track histogram-specific usage.
Like gauge and counter metrics, histogram metrics can be used in charts and detectors. Explicit Bucket Histograms are useful for performance data, such as request latency or response time. The most common way to use histogram data is to calculate percentiles for your charts and detectors. When creating a chart or detector with histogram data, users can:
Histograms are defined in OpenTelemetry. They can be sent into Observability Cloud:
Learn more and start using histograms today!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.