content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# MFA Generator This generator can create [RFC 4226](https://datatracker.ietf.org/doc/html/rfc4226) compliant TOTP tokens given a seed secret. The seed secret is usually provided through a QR code. However, the provider will always also provide a text based format of that QR code. That's the secret that this generator ... | https://github.com/external-secrets/external-secrets/blob/main/docs/api/generator/mfa.md | main | external-secrets | [
-0.14993999898433685,
0.01301856804639101,
-0.08247150480747223,
0.038337189704179764,
-0.033749260008335114,
0.05117843300104141,
0.020005319267511368,
-0.04859886318445206,
0.022141817957162857,
0.0026311110705137253,
0.04187434911727905,
-0.06675820052623749,
0.09895248711109161,
-0.042... | 0.115436 |
The Grafana generator creates short-lived [Grafana Service Account Tokens](https://grafana.com/docs/grafana/latest/administration/service-accounts/). It creates or reuses a Grafana service account (not a Kubernetes ServiceAccount) and generates a new API token for it. When the ExternalSecret is deleted, the generated t... | https://github.com/external-secrets/external-secrets/blob/main/docs/api/generator/grafana.md | main | external-secrets | [
-0.14078769087791443,
-0.03253142908215523,
-0.05039814114570618,
-0.0003247869899496436,
-0.08956973999738693,
-0.017639124765992165,
0.006030908320099115,
-0.0425226055085659,
0.10463844984769821,
0.03257450461387634,
-0.00652720732614398,
-0.057167962193489075,
0.03604098781943321,
-0.0... | 0.129304 |
The Azure Container Registry (ACR) generator creates a short-lived refresh or access token for accessing ACR. The token is generated for a particular ACR registry defined in `spec.registry`. ## Output Keys and Values | Key | Description | | -------- | ----------- | | username | username for the `docker login` command |... | https://github.com/external-secrets/external-secrets/blob/main/docs/api/generator/acr.md | main | external-secrets | [
-0.04790666326880455,
0.008393601514399052,
-0.09085844457149506,
0.05811803787946701,
-0.0214313343167305,
0.03174682706594467,
0.07114211469888687,
-0.025817036628723145,
0.046543560922145844,
0.09632724523544312,
-0.019392628222703934,
-0.04530881717801094,
0.05743854492902756,
0.019908... | 0.013568 |
CAUTION: Starting with Prometheus 3.0, console templates and libraries are no longer bundled with Prometheus. If you wish to use console templates, you must provide your own templates and libraries by specifying the `--web.console.templates` and `--web.console.libraries` command-line flags. This documentation page is m... | https://github.com/prometheus/docs/blob/main/docs/visualization/consoles.md | main | prometheus | [
-0.03307027369737625,
0.04624273255467415,
-0.044822391122579575,
-0.03924252837896347,
0.042707376182079315,
-0.06273659318685532,
-0.0027328182477504015,
0.05652819573879242,
0.001411855104379356,
0.02255612425506115,
-0.022524641826748848,
-0.05308596044778824,
0.0007842426421120763,
0.... | 0.199074 |
`humanizeNoSmallPrefix`: For absolute values greater than 1, display the result using [metric prefixes](http://en.wikipedia.org/wiki/Metric\_prefix). For absolute values less than 1, display 3 significant digits. This is useful to avoid units such as milliqueries per second that can be produced by `humanize`. \* `human... | https://github.com/prometheus/docs/blob/main/docs/visualization/consoles.md | main | prometheus | [
-0.06131671741604805,
0.041254397481679916,
-0.1258816421031952,
0.025331776589155197,
-0.07187303155660629,
-0.050709810107946396,
-0.0021283335518091917,
0.07037972658872604,
-0.042685795575380325,
-0.006710078567266464,
0.01632171869277954,
-0.0893382653594017,
0.025035619735717773,
0.0... | 0.156032 |
[Perses](https://perses.dev) is an open-source dashboard and visualization platform designed for observability, with native support for Prometheus as a data source. It enables users to create, manage, and share dashboards for monitoring metrics and visualizing data. Perses aims to provide a simple, flexible, and extens... | https://github.com/prometheus/docs/blob/main/docs/visualization/perses.md | main | prometheus | [
-0.0640082061290741,
0.03441225737333298,
-0.07234068214893341,
-0.04764917865395546,
0.010436995886266232,
-0.14095282554626465,
0.010794741101562977,
0.02946174517273903,
0.0420912504196167,
0.03335230425000191,
-0.008013848215341568,
-0.029597122222185135,
0.03973378986120224,
0.0350419... | 0.251079 |
[Grafana](http://grafana.com/) is an open-source analytics and visualization platform used to monitor and analyze metrics from various data sources. It allows users to create, explore, and share interactive dashboards, supporting integrations with databases like Prometheus, InfluxDB, Elasticsearch, and more. Grafana is... | https://github.com/prometheus/docs/blob/main/docs/visualization/grafana.md | main | prometheus | [
-0.09883452951908112,
-0.010842195712029934,
-0.10509312897920609,
0.004594637081027031,
-0.004984086845070124,
-0.13373036682605743,
-0.02735189162194729,
-0.018905337899923325,
0.003251816378906369,
0.019463930279016495,
-0.026012932881712914,
-0.0629010871052742,
-0.0006242567324079573,
... | 0.256851 |
Occasionally you will need to monitor components which cannot be scraped. The [Prometheus Pushgateway](https://github.com/prometheus/pushgateway) allows you to push time series from [short-lived service-level batch jobs](/docs/practices/pushing/) to an intermediary job which Prometheus can scrape. Combined with Prometh... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/pushing.md | main | prometheus | [
-0.11889946460723877,
-0.0030882784631103277,
-0.031397998332977295,
-0.0013675870141014457,
-0.01463833637535572,
-0.13115380704402924,
-0.06234347075223923,
0.004533918108791113,
-0.02511022239923477,
-0.0421060211956501,
-0.0047866529785096645,
-0.021169276908040047,
-0.026716364547610283... | 0.169918 |
There are a number of libraries and servers which help in exporting existing metrics from third-party systems as Prometheus metrics. This is useful for cases where it is not feasible to instrument a given system with Prometheus metrics directly (for example, HAProxy or Linux system stats). ## Third-party exporters Some... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exporters.md | main | prometheus | [
-0.0946497917175293,
-0.0622226782143116,
-0.04607322812080383,
-0.01232169009745121,
-0.00488827470690012,
-0.07022131979465485,
-0.03998316079378128,
0.02092134580016136,
0.005002625286579132,
-0.01530588697642088,
-0.016589641571044922,
-0.05069207027554512,
-0.005175196100026369,
0.013... | 0.16729 |
\* [Cryptowat exporter](https://github.com/nbarrientos/cryptowat\_exporter) \* [DigitalOcean exporter](https://github.com/metalmatze/digitalocean\_exporter) \* [Docker Cloud exporter](https://github.com/infinityworks/docker-cloud-exporter) \* [Docker Hub exporter](https://github.com/infinityworks/docker-hub-exporter) \... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exporters.md | main | prometheus | [
-0.11484359204769135,
0.007254781201481819,
-0.042824387550354004,
-0.006167555693536997,
0.09666255861520767,
-0.04082437977194786,
-0.04564789682626724,
-0.06102833151817322,
-0.03149070963263512,
0.007572501432150602,
0.06128912419080734,
-0.046226780861616135,
-0.004109013359993696,
-0... | 0.129122 |
(\*\*direct\*\*) \* [Dovecot](https://doc.dovecot.org/main/core/config/statistics.html#openmetrics) \* [Envoy](https://www.envoyproxy.io/docs/envoy/latest/operations/admin.html#get--stats?format=prometheus) \* [Etcd](https://github.com/coreos/etcd) (\*\*direct\*\*) \* [Flink](https://github.com/apache/flink) \* [FreeBS... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exporters.md | main | prometheus | [
-0.11791181564331055,
-0.024334393441677094,
-0.022815927863121033,
0.009818337857723236,
0.0564134307205677,
-0.13735003769397736,
-0.06277801841497421,
-0.00627177907153964,
0.0011441089445725083,
0.010640425607562065,
0.04398328810930252,
-0.0054239919409155846,
-0.031598519533872604,
-... | 0.202569 |
## Abstract This document specifies the protocol negotiation mechanism used by Prometheus when scraping metrics from targets. It defines the Accept header format, supported Content Types, and the negotiation process for determining the best available format for metric exposition. ## Introduction Prometheus supports mul... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/content_negotiation.md | main | prometheus | [
-0.07639344781637192,
0.0494297556579113,
-0.010895447805523872,
-0.03417028486728668,
0.029283126816153526,
-0.10530604422092438,
-0.01674404926598072,
-0.016819702461361885,
-0.02019977755844593,
0.00619955500587821,
-0.018420018255710602,
-0.06853047758340836,
0.024318737909197807,
0.03... | 0.163875 |
Default Accept Header ``` Accept: application/openmetrics-text;version=1.0.0;escaping=allow-utf-8;q=0.5,application/openmetrics-text;version=0.0.1;q=0.4,text/plain;version=1.0.0;escaping=allow-utf-8;q=0.3,text/plain;version=0.0.4;q=0.2,/;q=0.1 ``` ### Protobuf-First Accept Header ``` Accept: application/vnd.google.prot... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/content_negotiation.md | main | prometheus | [
-0.0455915592610836,
0.049621373414993286,
0.00033872565836645663,
-0.12351527810096741,
0.00044547076686285436,
-0.095530204474926,
-0.023336142301559448,
0.004129937384277582,
-0.0463908351957798,
0.019535185769200325,
0.003660155925899744,
-0.1500440090894699,
-0.021010132506489754,
0.0... | 0.046724 |
This document covers what functionality and API Prometheus client libraries should offer, with the aim of consistency across libraries, making the easy use cases easy and avoiding offering functionality that may lead users down the wrong path. There are [10 languages already supported](/docs/instrumenting/clientlibs) a... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_clientlibs.md | main | prometheus | [
-0.1525016725063324,
0.024067720398306847,
0.008766633458435535,
-0.08468662947416306,
0.004295710939913988,
-0.018825538456439972,
0.0036275419406592846,
0.08017493784427643,
-0.04654953256249428,
-0.043116096407175064,
0.010805033147335052,
-0.0007179991225712001,
0.03418460860848427,
0.... | 0.187106 |
The client library SHOULD enable this. The common use case is instrumenting a piece of code overall, not a piece of code in the context of one instance of an object. Users shouldn’t have to worry about plumbing their metrics throughout their code, the client library should do that for them (and if it doesn’t, users wil... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_clientlibs.md | main | prometheus | [
-0.14496150612831116,
-0.03879139572381973,
-0.13908971846103668,
0.03250396251678467,
-0.191152885556221,
0.010494074784219265,
-0.019682398065924644,
0.0576026551425457,
0.0071941097266972065,
-0.04856077954173088,
-0.04449714347720146,
-0.09620115160942078,
0.05063692852854729,
0.028297... | 0.088652 |
allow not having quantiles, as just `\_count`/`\_sum` is quite useful and this MUST be the default. A summary MUST have the following methods: \* `observe(double v)`: Observe the given amount A summary SHOULD have the following methods: Some way to time code for users in seconds. In Python this is the `time()` decorato... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_clientlibs.md | main | prometheus | [
-0.05291759595274925,
0.04621734470129013,
-0.04012107104063034,
-0.004078214056789875,
-0.12431759387254715,
-0.004107852466404438,
0.05036379396915436,
0.03670496866106987,
0.04535416513681412,
-0.026831787079572678,
-0.007731026038527489,
-0.11015757918357849,
0.01237052958458662,
0.072... | 0.164293 |
support a `remove()` method with the same signature as `labels()` that will remove a Child from the metric no longer exporting it, and a `clear()` method that removes all Children from the metric. These invalidate caching of Children. There SHOULD be a way to initialize a given Child with the default value, usually jus... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_clientlibs.md | main | prometheus | [
-0.09014271944761276,
0.02204960398375988,
-0.07064345479011536,
0.0474557988345623,
-0.08698698878288269,
-0.011138970963656902,
0.04611987993121147,
-0.011611077934503555,
0.06417272239923477,
-0.04267100244760513,
0.04803390055894852,
-0.09774303436279297,
-0.004056672565639019,
0.00473... | 0.121051 |
Unit tests Client libraries SHOULD have unit tests covering the core instrumentation library and exposition. Client libraries are ENCOURAGED to offer ways that make it easy for users to unit-test their use of the instrumentation code. For example, the `CollectorRegistry.get\_sample\_value` in Python. ## Packaging and d... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_clientlibs.md | main | prometheus | [
-0.14011554419994354,
0.0008435784257017076,
-0.014948560856282711,
-0.03828032687306404,
0.01635492593050003,
-0.08723510801792145,
-0.041709329932928085,
0.002625222085043788,
0.0004834041465073824,
-0.07107379287481308,
-0.0538146086037159,
-0.014761253260076046,
0.06558574736118317,
0.... | 0.073426 |
If you are instrumenting your own code, the [general rules of how to instrument code with a Prometheus client library](/docs/practices/instrumentation/) should be followed. When taking metrics from another monitoring or instrumentation system, things tend not to be so black and white. This document contains things you ... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.0767076313495636,
0.006863728631287813,
-0.04026151821017265,
0.0023976515512913465,
-0.05285897105932236,
-0.10373476147651672,
-0.03564046695828438,
0.04235408082604408,
-0.0101741598919034,
-0.0124670946970582,
-0.046394314616918564,
-0.08287575840950012,
0.007830914109945297,
-0.032... | 0.136685 |
these being measured as they come in, in some filter or when they get to the user’s code? And `requests\_total` is even worse, what type of requests? With direct instrumentation, a given metric should exist within exactly one file. Accordingly, within exporters and collectors, a metric should apply to exactly one subsy... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.09444534778594971,
0.01018691249191761,
-0.12294398248195648,
0.018942635506391525,
-0.052819717675447464,
-0.050114698708057404,
-0.009019057266414165,
0.05277000740170479,
0.04778276011347771,
-0.028227968141436577,
-0.00958909559994936,
-0.1332107037305832,
0.016082512214779854,
-0.0... | 0.111458 |
just DBAs. A `HELP` string with the original name can provide most of the same benefits as using the original names. ### Labels Read the [general advice](/docs/practices/instrumentation/#things-to-watch-out-for) on labels. Avoid `type` as a label name, it’s too generic and often meaningless. You should also try where p... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.05697852000594139,
-0.05017194524407387,
-0.07892973721027374,
-0.0023213308304548264,
-0.11148364096879959,
-0.018849194049835205,
0.08824153244495392,
0.055501025170087814,
0.0027273735031485558,
-0.007749095093458891,
-0.01742732897400856,
-0.07624677568674088,
0.07330704480409622,
0... | 0.156863 |
we end up with both the `digest\_text` label for humans and the `digest` label for uniqueness. ### Target labels, not static scraped labels If you ever find yourself wanting to apply the same label to all of your metrics, stop. There’s generally two cases where this comes up. The first is for some label it would be use... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.015187597833573818,
0.03498099371790886,
-0.059340838342905045,
-0.020449433475732803,
-0.005187090951949358,
-0.10167691856622696,
0.09032465517520905,
0.0155979935079813,
-0.033788517117500305,
-0.1022757887840271,
0.04993962496519089,
-0.08824783563613892,
0.07794307917356491,
-0.007... | 0.113891 |
need to calculate it. Quantiles have related issues, you may choose to drop them or put them in a Summary. ### Dotted strings Many monitoring systems don’t have labels, instead doing things like `my.class.path.mymetric.labelvalue1.labelvalue2.labelvalue3`. The [Graphite](https://github.com/prometheus/graphite\_exporter... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.11458490788936615,
0.06233352795243263,
-0.06124301627278328,
-0.0028044143691658974,
-0.06089210510253906,
-0.0390474759042263,
0.01039739791303873,
0.028260905295610428,
-0.021253440529108047,
-0.022964326664805412,
0.03527503088116646,
-0.13466976583003998,
-0.04659285023808479,
0.01... | 0.074071 |
probe your service with the [blackbox exporter](https://github.com/prometheus/blackbox\_exporter). There are two exceptions: The first is where running beside the application you are monitoring is completely nonsensical. The SNMP, blackbox and IPMI exporters are the main examples of this. The IPMI and SNMP exporters as... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.08594579249620438,
-0.0363154262304306,
-0.05309801921248436,
0.005562011618167162,
0.02391292341053486,
-0.1265091598033905,
-0.009445841424167156,
-0.015954483300447464,
0.010979153215885162,
-0.016346773132681847,
-0.04710911959409714,
-0.048121947795152664,
0.038705937564373016,
-0.... | 0.151309 |
in-memory state (probably best if you don’t need to persist over a reboot) or implement similar functionality to the textfile collector. ### Failed scrapes There are currently two patterns for failed scrapes where the application you’re talking to doesn’t respond or has other problems. The first is to return a 5xx erro... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/writing_exporters.md | main | prometheus | [
-0.10392200201749802,
0.015516411513090134,
-0.07273760437965393,
0.07495951652526855,
0.02748246118426323,
-0.0225534625351429,
0.023643765598535538,
0.046554356813430786,
-0.043545037508010864,
-0.004708645399659872,
-0.00640745647251606,
0.011519484221935272,
0.019194070249795914,
-0.08... | 0.056653 |
## Abstract This document specifies the different escaping schemes used by Prometheus during generation of text exposition for metric and label names that contain characters outside the legacy character set. These schemes are negotiated during scraping via the `escaping` parameter in the Accept and Content-Type headers... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/escaping_schemes.md | main | prometheus | [
-0.135807067155838,
0.06285402923822403,
0.019991567358374596,
0.03190276771783829,
-0.013394107110798359,
-0.04016602411866188,
0.024087904021143913,
-0.03338867053389549,
0.03161781653761864,
-0.018219230696558952,
0.013091642409563065,
-0.11064639687538147,
0.06949922442436218,
-0.00907... | 0.154243 |
As of Prometheus version 2.0, all processes that expose metrics to Prometheus must use a \*\*text\*\* format, by default. An alternative, \*\*protobuf\*\* format may be used behind [the HTTP negotiation](./content\_negotiation.md). There are various [client libraries](./clientlibs.md) that implement those formats for y... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exposition_formats.md | main | prometheus | [
-0.062357570976018906,
0.09456803649663925,
-0.026157179847359657,
-0.0142408711835742,
-0.020952830091118813,
-0.09940557926893234,
-0.02669922634959221,
0.010502382181584835,
0.035466961562633514,
0.002471921034157276,
-0.048345454037189484,
-0.047078538686037064,
0.006808664184063673,
0... | 0.17408 |
[ label\_pairs ] label\_pairs = label\_pair { "," label\_pair } [ "," ] label\_pair = label\_name "=" `"` escaped\_string `"` label\_name = identifier | `"` escaped\_string `"` ``` In the sample syntax: \* `identifier` carries the usual Prometheus expression language restrictions. \* `escaped\_string` consists of any U... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exposition_formats.md | main | prometheus | [
-0.10533132404088974,
0.059220846742391586,
-0.010045420378446579,
0.011956438422203064,
-0.08680154383182526,
-0.02131875604391098,
0.0833013728260994,
0.017779646441340446,
-0.01096875499933958,
-0.030647573992609978,
-0.00282586389221251,
-0.10376276820898056,
0.04620581120252609,
0.000... | 0.176245 |
Finally a summary, which has a complex representation, too: # HELP rpc\_duration\_seconds A summary of the RPC duration in seconds. # TYPE rpc\_duration\_seconds summary rpc\_duration\_seconds{quantile="0.01"} 3102 rpc\_duration\_seconds{quantile="0.05"} 3272 rpc\_duration\_seconds{quantile="0.5"} 4773 rpc\_duration\_s... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exposition_formats.md | main | prometheus | [
-0.05906568095088005,
0.07851258665323257,
-0.07559803873300552,
-0.004878805950284004,
0.02294207364320755,
-0.036494459956884384,
-0.02893660217523575,
0.08670177310705185,
0.05531966686248779,
-0.02038566768169403,
0.03813612088561058,
-0.10894088447093964,
-0.03948185220360756,
0.06794... | 0.186945 |
+ Supports Concatenation and Streaming + Composite Values| | \*\*Limitations\*\* | + Not human readable| | \*\*Supported metric primitives\*\* | + Counter + Gauge + Histogram + GaugeHistogram + Summary + Untyped| | \*\*Supported advanced features\*\* | + Unit metadata + Exemplars (Counters, Histogram, GaugeHistogram) +... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/exposition_formats.md | main | prometheus | [
-0.06096167489886284,
-0.003635892877355218,
-0.019257860258221626,
-0.052187297493219376,
-0.007552976720035076,
-0.046906545758247375,
0.016997842118144035,
0.05235520005226135,
0.014295454137027264,
-0.003634115681052208,
0.03348677605390549,
-0.11205991357564926,
-0.005687160883098841,
... | 0.232119 |
Before you can monitor your services, you need to add instrumentation to their code via one of the Prometheus client libraries. These implement the Prometheus [metric types](/docs/concepts/metric\_types/). Choose a Prometheus client library that matches the language in which your application is written. This lets you d... | https://github.com/prometheus/docs/blob/main/docs/instrumenting/clientlibs.md | main | prometheus | [
-0.06945423036813736,
-0.029927225783467293,
-0.05066113919019699,
-0.018106259405612946,
-0.038853567093610764,
-0.10765857994556427,
-0.016950400546193123,
0.007851645350456238,
0.020455479621887207,
-0.033712297677993774,
-0.054011765867471695,
-0.033024802803993225,
-0.003545314772054553... | 0.192505 |
Native histograms were introduced as an experimental feature in November 2022. They are a concept that touches almost every part of the Prometheus stack. The first version of the Prometheus server supporting native histograms was v2.40.0. The support had to be enabled via a feature flag `--enable-feature=native-histogr... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.006281678099185228,
-0.01660304330289364,
0.018718088045716286,
-0.013129517436027527,
0.015320125967264175,
-0.10243645310401917,
-0.04809904098510742,
-0.00746523542329669,
-0.07110724598169327,
0.006928950548171997,
-0.00981899257749319,
-0.05253070220351219,
-0.010983824729919434,
-... | 0.140361 |
the previously known \_sum\_ and \_count\_ plus a dynamic set of buckets. This is not limited to ingestion, but PromQL expressions may also return the new sample type where previously it was only possible to return float samples. Native histograms have the following key properties: 1. A sparse bucket representation, al... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.02630949392914772,
0.017806656658649445,
-0.0424017459154129,
-0.00650970172137022,
-0.053128473460674286,
-0.015105203725397587,
-0.006920363754034042,
0.03866589441895485,
0.013594222255051136,
0.025453153997659683,
-0.07545211911201477,
-0.08324392139911652,
0.04487447440624237,
0.019... | 0.129064 |
samples upon ingestion into Prometheus. - \_\_Sparse histogram\_\_ is an older, now deprecated name for \_native histogram\_. This name might still be found occasionally in older documentation. \_\_Sparse buckets\_\_ remains a meaningful term for the buckets of a native histogram. ## Data model This section describes t... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.04276476427912712,
0.012664076872169971,
-0.020928705111145973,
-0.03787951543927193,
-0.040892913937568665,
-0.09859449416399002,
0.01965217851102352,
0.0632486417889595,
0.013285435736179352,
-0.02686382085084915,
0.03853535279631615,
-0.0652182474732399,
0.05231785401701927,
0.000940... | 0.18745 |
negative histograms are only allowed as intermediate results and are otherwise considered invalid. They cannot be represented in any of the exchange formats (exposition formats, remote-write, OTLP) and they cannot be stored in the TSDB. Also see the [detailed section about negative histograms](#unary-minus-and-negative... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.04274040088057518,
0.02442334219813347,
-0.030431602150201797,
-0.09288972616195679,
-0.04898638650774956,
-0.04682758450508118,
-0.0021520620211958885,
0.07381811738014221,
0.025815896689891815,
0.03365783765912056,
-0.03620610386133194,
-0.10089118033647537,
0.0313139371573925,
0.01125... | 0.06592 |
half the resolution of schema \_n\_+1, which implies that a histogram with schema \_n\_+1 can be converted into a histogram with schema \_n\_ by merging neighboring buckets. For any standard schema \_n\_, the boundaries of a bucket with index \_i\_ calculated as follows (using Python syntax): - The upper inclusive limi... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.03817691653966904,
0.018567455932497978,
0.01352571602910757,
-0.09414207190275192,
-0.01880842261016369,
-0.048850588500499725,
-0.009298942051827908,
0.0060938093811273575,
-0.03893469646573067,
0.004543597809970379,
-0.01802702620625496,
-0.09555233269929886,
0.09713049978017807,
0.00... | 0.06062 |
this omission in a suitable way. When a TSDB implementation reads histograms from its permanent storage (excluding replaying the WAL/WBL), similar guidelines apply: Schemas between 9 and 52 MAY be converted to valid schemas. Otherwise, unknown schemas MUST return an error on retrieval, and the PromQL query that trigger... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.05580667033791542,
-0.00443352060392499,
-0.01205675583332777,
-0.014415711164474487,
-0.06421859562397003,
0.06458071619272232,
0.01995404250919819,
0.005989936646074057,
-0.01892893947660923,
0.017730319872498512,
-0.04974840208888054,
-0.05084297060966492,
0.021876253187656403,
0.0168... | 0.079634 |
producers of native histograms MAY pick whatever representation has the best resource trade-offs at that moment. For example, if a histogram is processed through various stages, it might be most efficient to only eliminate redundant spans after the last processing stage. In a similar spirit, there are situation where e... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.041287776082754135,
0.05007293447852135,
-0.004311290103942156,
-0.08442827314138412,
0.018290312960743904,
-0.020056741312146187,
-0.058271702378988266,
0.026493014767766,
-0.02623651921749115,
0.013361449353396893,
-0.06974035501480103,
-0.042285624891519547,
0.047510694712400436,
0.00... | 0.060191 |
such an overlap is happening, the observations that are counted in the regular bucket overlapping with the zero bucket MUST be outside of the [-threshold, +threshold] interval. To merge histograms with the same zero threshold, the two zero buckets are simply added. If the zero thresholds in the source histograms are di... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.022244296967983246,
-0.03979991748929024,
0.005392703227698803,
-0.04503297060728073,
-0.017261076718568802,
-0.030205311253666878,
0.02063056454062462,
0.016712410375475883,
0.008916092105209827,
-0.0011319038458168507,
0.052864450961351395,
-0.09162507951259613,
0.0275941863656044,
-0.... | 0.029648 |
histogram sample can have zero, one, or more exemplars. They work in the same way as conventional exemplars, but they are organized in a list (as there can be more than one), and they MUST have a timestamp. Exemplars exposed as part of a classic histogram MAY be used by native histograms, if they have a timestamp. ### ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.020669275894761086,
-0.01555574033409357,
-0.019107919186353683,
-0.06975055485963821,
-0.030927926301956177,
-0.032585930079221725,
0.008979002013802528,
0.02380107343196869,
0.03322712704539299,
0.06395165622234344,
0.05182693898677826,
-0.07703447341918945,
0.054056402295827866,
-0.0... | 0.089872 |
precise. If OTel counts NaN in the zero bucket, we have to add a note here.) OTel exponential histograms only support standard exponential bucketing schemas (as the name suggests). Therefore, NHCBs (or native histograms with other future bucketing schemas) cannot be cleanly converted to OTel exponential histograms. How... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.002829544013366103,
-0.0008730263216421008,
-0.04167424142360687,
-0.0798778235912323,
-0.06302724033594131,
-0.058025505393743515,
0.027255361899733543,
0.03525314852595329,
0.019835663959383965,
-0.007758185267448425,
-0.01522855181246996,
-0.1122853234410286,
0.09091603755950928,
0.04... | 0.179976 |
uint64 zero\_count = 7; // Count in zero bucket. double zero\_count\_float = 8; // Overrides sb\_zero\_count if > 0. // Negative buckets for the native histogram. repeated BucketSpan negative\_span = 9 [(gogoproto.nullable) = false]; // Use either "negative\_delta" or "negative\_count", the former for // regular histog... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.06724955886602402,
0.03533225879073143,
0.0016580265946686268,
-0.08453557640314102,
-0.08467015624046326,
0.0037756937090307474,
0.020469261333346367,
0.010881423950195312,
-0.03666377067565918,
-0.055549249053001404,
0.03515305742621422,
-0.09906408935785294,
0.027662325650453568,
0.03... | -0.01134 |
both a classic and a native version of the same histogram. Parsers have the freedom to pick either or both versions (see also the [scrape configuration section](#scrape-configuration)). - The bucket population is encoded as absolute numbers in case of float histograms, and as deltas to the previous bucket (or to zero f... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.03867973014712334,
-0.01845145970582962,
0.011623314581811428,
-0.06911616027355194,
0.011016760021448135,
-0.057356081902980804,
-0.030431613326072693,
0.020987749099731445,
0.014891396276652813,
0.0020852615125477314,
0.003437873674556613,
-0.09824683517217636,
0.008808864280581474,
-0... | 0.018565 |
format](#openmetrics) is a prerequisite. (TODO: Update this as needed.) This section does not cover details of how to use individual instrumentation libraries (see the documentation linked above for that) but focuses on the common usage patterns and also provides general guidelines how to implement native histogram sup... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.010547981597483158,
0.02471458725631237,
-0.050352245569229126,
-0.07304861396551132,
-0.031036455184221268,
-0.0032462812960147858,
-0.029180997982621193,
0.048929475247859955,
-0.038209959864616394,
-0.014843503944575787,
-0.01724061742424965,
-0.059179652482271194,
0.00841026846319437,... | 0.227896 |
populated for the first time. An unexpectedly broad distribution of observed values can lead to an unexpectedly high number of buckets, requiring more memory than anticipated. If the distribution of observed values can be manipulated from the outside, this could even be used as a DoS attack vector via exhausting all th... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.035966165363788605,
0.025636965408921242,
-0.016196923330426216,
-0.04965376481413841,
-0.03535909578204155,
-0.034535352140665054,
-0.00035316465073265135,
0.027650030329823494,
0.01875738799571991,
-0.004592807963490486,
-0.02762407250702381,
-0.038841649889945984,
0.007746165618300438,
... | 0.058763 |
has passed since the last reset, not only to remove the buckets but also to return to the initial values for the zero threshold and the bucket resolution. Note that this is treated like a reset for other reasons in all aspects, including updating the [start timestamp](#start-timestamp-handling). It is tempting to set a... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.01941712386906147,
0.026678863912820816,
0.03813726454973221,
-0.039902616292238235,
-0.025700965896248817,
-0.09883822500705719,
-0.018211092799901962,
0.02503533661365509,
0.017551371827721596,
0.03202271834015846,
0.0020692781545221806,
-0.030877605080604553,
0.02421567589044571,
-0.... | 0.058005 |
those cases, the current approach is to instrument with a classic histogram and configure the scraper to convert it to an NHCB upon ingestion. However, a more direct treatment of NHCBs in instrumentation libraries might happen in the future. ## Scrape configuration To enable the Prometheus server to scrape native histo... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.024790819734334946,
0.05193762853741646,
-0.034972283989191055,
-0.04551015421748161,
0.012185321189463139,
-0.09033090621232986,
-0.02717772126197815,
-0.014759521000087261,
-0.07797132432460785,
-0.022461947053670883,
-0.0530211366713047,
-0.12318284809589386,
0.05037054046988487,
0.0... | 0.164355 |
effect on NHCBs. Again, if the limit is exceeded, the resolution of the histogram is repeatedly reduced (by doubling the width of the buckets, i.e. decreasing the schema) until the limit is reached. However, once schema -4 is reached, the scrape will still succeed, even if a higher growth factor has been specified. Bot... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.012997614219784737,
0.045270707458257675,
0.005348069127649069,
-0.02024330198764801,
0.03797628730535507,
-0.11297332495450974,
-0.04249265417456627,
-0.007053439971059561,
-0.029121452942490578,
0.01037626713514328,
-0.0015022453153505921,
-0.05349801480770111,
0.05779580771923065,
0.... | 0.126527 |
the classic histogram parts, even if both are exposed for the same histogram. Prometheus will still scrape the classic histogram parts for histograms with no native histogram data. In situations like [migration scenarios](#migration-considerations), it might be desired to scrape both versions, classic and native, for t... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.0012324904091656208,
-0.023133350536227226,
0.03998818248510361,
-0.049684494733810425,
0.03199415281414986,
-0.07121796160936356,
-0.03163905069231987,
-0.03735454007983208,
-0.06038747727870941,
-0.03504727780818939,
-0.020539913326501846,
-0.03431053087115288,
0.03219233825802803,
-0.... | 0.050611 |
9) for integer histograms, and `record.FloatHistogramSamples` (string representation `float\_histogram\_samples`, numerical value 10) for float histograms. For backwards compatibility reasons, there are two more histogram record types: `record.HistogramSamplesLegacy` (`histogram\_samples\_legacy`, 7) and `record.FloatH... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.05051688477396965,
-0.007854181341826916,
-0.026223378255963326,
-0.02199944108724594,
0.010977945290505886,
-0.02022918313741684,
-0.002647649496793747,
0.02962569147348404,
-0.0064134965650737286,
-0.0638374611735344,
-0.06368150562047958,
-0.04427281394600868,
-0.025392455980181694,
... | 0.166774 |
layout, which contains the following information, \_shared by all histograms in the chunk\_: - The threshold of the zero bucket, using a custom encoding that encodes common values (zero or certain powers of two) in just one byte, but requires 9 bytes for arbitrary values. - The schema, encoded as varbit-int. - The posi... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.04674035683274269,
0.015024247579276562,
-0.05033715069293976,
-0.07160325348377228,
-0.027832964435219765,
0.0367463193833828,
-0.019603122025728226,
-0.0121171148493886,
-0.007191510405391455,
-0.05528808385133743,
-0.03368283435702324,
-0.08153680711984634,
0.0534602589905262,
-0.0138... | 0.155255 |
schema change (which means we need a new chunk layout, and a chunk can only have one chunk layout). - A change of the zero threshold (which changes the chunk layout, see above). - A change of the custom values (which changes the chunk layout, see above). - A staleness marker is followed by a regular sample (which does ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.03454780578613281,
-0.007063660770654678,
0.04950255900621414,
-0.010329697281122208,
0.052949562668800354,
-0.016463471576571465,
-0.07169275730848312,
-0.02383042871952057,
0.014977725222706795,
-0.05566587671637535,
0.0016654881183058023,
-0.03492291644215584,
-0.03679174184799194,
-... | 0.041178 |
treated as equivalent by the TSDB. ### Chunk size limit The size of float chunks is limited to 1024 bytes. The same size limitation is generally used for histogram chunks, too. However, individual histograms can become very large if they have many buckets, so blindly enforcing the size limit could lead to chunks with v... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.030114641413092613,
0.020176708698272705,
-0.012754399329423904,
-0.08050146698951721,
-0.03092338889837265,
-0.06010396033525467,
-0.024145973846316338,
0.0490264967083931,
-0.025258492678403854,
0.0014647124335169792,
-0.07965679466724396,
-0.006903710775077343,
0.0010978090576827526,
... | 0.109726 |
values is reconciled as described [below](#compatibility-between-histograms). At this point in the procedure, both histograms have the same schema and zero bucket width, either because this was the case from the beginning, or because one of the histograms was converted accordingly. (Note that NHCBs do not use the zero ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.020497020334005356,
-0.03226668760180473,
-0.004272459540516138,
0.011958561837673187,
0.0015602129278704524,
0.02158878557384014,
0.0119098462164402,
0.010634472593665123,
0.017265919595956802,
0.012997825630009174,
0.005317891016602516,
-0.09216716885566711,
0.05198955908417702,
0.0341... | 0.075167 |
type `CounterResetHint` in the Go types `Histogram` and `FloatHistogram`, using enumerated constants with the same names as the bit pattern constants above). For gauge histogram, the `CounterResetHint` is always `GaugeType`. Any other `CounterResetHint` value implies that the histogram in question is a counter histogra... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.05140289291739464,
-0.011374019086360931,
-0.0545872338116169,
0.03928175941109657,
-0.08707870543003082,
0.006334496196359396,
0.104758620262146,
-0.005573673639446497,
-0.00029314515995793045,
-0.06732437759637833,
0.014543051831424236,
-0.07794659584760666,
0.012654295191168785,
-0.0... | 0.102318 |
missed B and C so that only A and D were ingested, with a counter reset detected between A and D. Later, B and C are ingested (via out-of-order ingestion or as separate chunks later added to the TSDB as a separate block), with a counter reset detected between B and C. In this case, each sample goes into its own chunk, ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.08344858884811401,
-0.12696002423763275,
0.010979723185300827,
0.04217684641480446,
-0.04829738661646843,
0.029773641377687454,
0.06080801412463188,
-0.023129215463995934,
-0.002227411139756441,
0.028616342693567276,
0.0004586518043652177,
0.01775163970887661,
0.03636914864182472,
-0.00... | 0.031263 |
individual buckets. (See also the [exposition formats section](#exposition-formats).) Therefore, it is allowed (and in fact the common case) that a single native histogram sample comes with multiple exemplars attached. Exemplars may or may not change from one scrape to the next. Scrapers SHOULD detect unchanged exempla... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.04319136217236519,
-0.0766649842262268,
0.03143388032913208,
-0.012330240570008755,
0.015910889953374863,
0.04082397744059563,
0.02094179578125477,
-0.006527599412947893,
0.012017537839710712,
0.0068302094005048275,
-0.03035804256796837,
-0.04930019751191139,
0.04208506643772125,
-0.040... | 0.045135 |
the original NHCBs do not share any custom values. In this case, the new bucket set will only consist of the overflow bucket, taking all observations from all of the original buckets. - Any query requiring reconciliation of custom values is flagged with an info-level annotation. - Histograms with standard schemas can a... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.058545950800180435,
0.014505965635180473,
-0.00593004422262311,
-0.03111356310546398,
-0.012607275508344173,
0.010680587962269783,
-0.023538863286376,
0.00630227429792285,
0.002623547101393342,
-0.008636441081762314,
-0.04655291140079498,
-0.08978062868118286,
0.0451446957886219,
0.01425... | 0.05893 |
90th percentile at 190ms.) The worst case is an estimation at one end of a bucket where the actual value is at the other end of the bucket. Therefore, the maximum possible error is the whole width of a bucket. Not doing any interpolation and using some fixed midpoint within a bucket (for example the arithmetic mean or ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.011852721683681011,
0.04001053422689438,
-0.011197670362889767,
-0.10523511469364166,
-0.06601805984973907,
-0.029247691854834557,
-0.048435188829898834,
0.10316084325313568,
-0.03828906640410423,
0.0004718019044958055,
-0.1074647456407547,
-0.04355805739760399,
0.09703454375267029,
-0.0... | 0.071892 |
PromQL operation, but a warn-level annotation is returned with the result if some of the input samples have an inappropriate flavor (see [above](#gauge-histograms-vs-counter-histograms)). A mix of float samples and histogram samples is more problematic. Many functions that operate on range vectors will remove elements ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.04639462009072304,
0.03192465007305145,
-0.0018247767584398389,
0.04310375824570656,
-0.011457299813628197,
-0.006443291436880827,
0.1137656569480896,
-0.007393211591988802,
0.012942926958203316,
-0.03448035567998886,
0.010971740819513798,
-0.09430840611457825,
0.04852548614144325,
0.00... | 0.108511 |
(sample or scalar). This will lead to “scaled” and sometimes even negative histograms, which is usually only useful as intermediate results inside other expressions (see also [notes above](#unary-minus-and-negative-histograms)). Multiplication works for both counter histograms and gauge histograms, and their flavor is ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.07988068461418152,
0.009443937800824642,
-0.050267741084098816,
-0.003903476521372795,
-0.05622882768511772,
-0.06825140118598938,
0.032800208777189255,
0.014156472869217396,
0.029404794797301292,
-0.002204501535743475,
0.04538896679878235,
-0.03736794739961624,
0.04780668020248413,
0.0... | 0.130737 |
to the original interpolation heuristics.) - -Inf for the negative overflow bucket of a standard exponential histogram. - +Inf for the positive overflow bucket of a standard exponential histogram. - The arithmetic mean for all other buckets of an NHCB and for the zero bucket of a standard exponential histogram, taking ... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.060746658593416214,
0.04355083405971527,
0.022035861387848854,
-0.08657772094011307,
-0.008438464254140854,
-0.0658021867275238,
-0.009542523883283138,
0.07587546110153198,
0.018057366833090782,
0.017682485282421112,
-0.04148469492793083,
-0.06113657355308533,
0.08535822480916977,
-0.00... | 0.08588 |
unit tests via `promtool` can include native histograms. The histogram sample notation is complex and explained in the [documentation for rules unit testing](https://prometheus.io/docs/prometheus/latest/configuration/unit\_testing\_rules/#series). In the unit test framework there is an alternative `load` command called... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.003642098745331168,
0.03444107994437218,
-0.05081402510404587,
-0.014648089185357094,
-0.033540260046720505,
-0.08583194762468338,
-0.01014456246048212,
0.04100114479660988,
-0.03535950928926468,
-0.012206546030938625,
-0.078034408390522,
-0.07512954622507095,
0.07105071097612381,
0.009... | 0.213002 |
] } ``` `count` and `sum` directly correspond to the histogram fields of the same name. Each bucket is represented explicitly with its boundaries and count, including the zero bucket. Spans and the schema are therefore not part of the response, and the structure of the histogram object does not depend on the used schem... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.07139110565185547,
0.008818631060421467,
-0.03229795768857002,
-0.06358171999454498,
-0.030622340738773346,
0.03330208733677864,
-0.01177679467946291,
-0.00536887114867568,
0.036711547523736954,
-0.03523300960659981,
-0.017690377309918404,
-0.126833975315094,
0.05173571780323982,
0.02347... | 0.11198 |
bucket. The position of each bar on the \_x\_ axis is determined by the lower and upper limit of the corresponding bucket. The area of each bar is proportional to the population of the corresponding bucket (which is a core principle of rendering histograms in general). The graphical histogram allows a choice between an... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.014421619474887848,
-0.0007619932875968516,
-0.055349282920360565,
-0.09001605957746506,
-0.03589492663741112,
-0.067679762840271,
-0.049967631697654724,
0.027514023706316948,
0.019581137225031853,
0.03458661958575249,
0.032499223947525024,
-0.06962917745113373,
0.05648793652653694,
0.00... | 0.114576 |
scraping. Similarly, explicit OTel histograms SHOULD be converted to NHCBs during [OTLP ingestion](#otlp) already. TODO: A remaining possible problem with remote-write is what to do if multiple exemplars originally ingested for the same native histogram are sent in different remote-write requests. ## Federation Federat... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.032687656581401825,
0.014198913238942623,
-0.03729734569787979,
-0.08521706610918045,
0.009386069141328335,
-0.09556207060813904,
-0.04359539970755577,
-0.0060118502005934715,
-0.04284410923719406,
0.010799014009535313,
-0.021350819617509842,
-0.11743858456611633,
0.036778975278139114,
0... | 0.169187 |
metrics` - `promtool tsdb dump-openmetrics` - `promtool tsdb create-blocks-from openmetrics` TODO: Update as progress is made. See [tracking issue](https://github.com/prometheus/prometheus/issues/12146). ## `prom2json` [`prom2json`](https://github.com/prometheus/prom2json) is a small tool that scrapes a Prometheus `/me... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
-0.07008811086416245,
0.012255542911589146,
-0.03433404862880707,
0.017579030245542526,
-0.004316368140280247,
-0.07064216583967209,
-0.005837729200720787,
-0.011392978020012379,
-0.001949822879396379,
-0.012082922272384167,
-0.03909091651439667,
-0.0452256016433239,
-0.0021046216133981943,
... | 0.188013 |
shorter period. Thus, the query should only be used once native histograms have been collected for at least 1d. For a dashboard that displays the daily 90th percentile latency over the last month, it is tempting to craft a query that correctly switches from classic to native histograms at the right moment. While that i... | https://github.com/prometheus/docs/blob/main/docs/specs/native_histograms.md | main | prometheus | [
0.02665109559893608,
0.010052080266177654,
-0.007293968461453915,
-0.018799837678670883,
-0.0028644846752285957,
-0.09466983377933502,
-0.02297019027173519,
-0.0018847986357286572,
-0.04283596947789192,
-0.005114130210131407,
-0.024510527029633522,
-0.05446667596697807,
0.031211094930768013,... | 0.08003 |
- Version: 2.0.0-rc0 - Status: Experimental - Date: March 2026 - Authors: Arthur Silva Sens, Bartłomiej Płotka, David Ashpole, György Krajcsovits, Owen Williams, Richard Hartmann - Emeritus: Ben Kochie, Brian Brazil, Rob Skillington Created in 2012, Prometheus has been the default for cloud-native observability since 2... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.06826499849557877,
0.019104620441794395,
-0.030029715970158577,
0.007068147882819176,
0.0685267299413681,
-0.06910362094640732,
-0.030057769268751144,
0.012467948719859123,
0.02017151564359665,
0.011647540144622326,
-0.007530534639954567,
-0.029507532715797424,
-0.002242270391434431,
0.... | 0.234723 |
would be network interface counters, device temperatures, BGP connection states, latency distributions, and alert states. ## Normative Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be i... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.011289832182228565,
-0.07187257707118988,
-0.006200001575052738,
0.016826855018734932,
-0.01769193634390831,
0.05142993852496147,
0.052450209856033325,
-0.008372027426958084,
0.056710850447416306,
-0.05118771642446518,
0.032705552875995636,
-0.021818429231643677,
0.06032997742295265,
-0... | 0.211876 |
before or equal to the Sample's timestamp, if present. The timestamp SHOULD be after or equal to the Sample's start timestamp, if present. Exemplars of a Sample SHOULD have the same Label names to have a consistent style. The Exemplar's timestamp SHOULD be close to the point when it was observed, but doesn't have to be... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.1062951534986496,
0.03613162785768509,
-0.04812869057059288,
0.009646523743867874,
0.07861875742673874,
-0.06376513838768005,
0.008746287785470486,
0.0358356311917305,
0.041697513312101364,
-0.05216947942972183,
0.06854408979415894,
-0.08311203867197037,
-0.039595380425453186,
-0.101239... | 0.05655 |
A non-compliant example would be a gauge called `foo\_bucket` and a histogram called `foo`. Exposers negotiating the older OpenMetrics or Text formats, or ingestors which support only the older data model could end up storing the `foo` histogram in the classic representation (`foo\_bucket`, `foo\_count`, `foo\_sum`), w... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.06577989459037781,
0.01675419509410858,
0.006642194930464029,
-0.000874098448548466,
0.02434191294014454,
-0.08542487025260925,
-0.03643746301531792,
-0.005361318122595549,
0.0006839391426183283,
-0.0381350964307785,
0.022612106055021286,
-0.052094560116529465,
0.029587721452116966,
0.0... | 0.168055 |
be set to the approximate reset time. A Sample in a Metric with the type Counter MAY have exemplars. #### StateSet StateSets represent a series of related boolean values, also called a bitset. If ENUMs need to be encoded this MAY be done via StateSet. A StateSet is structured as a set of Metrics, one for each state, ca... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.03624391555786133,
-0.06404031813144684,
-0.04507650062441826,
-0.059463437646627426,
-0.018832437694072723,
0.007504588924348354,
0.04457559064030647,
-0.0006828746409155428,
0.05934552103281021,
-0.023032693192362785,
-0.025583384558558464,
-0.08571687340736389,
0.07356803119182587,
0... | 0.155162 |
and the Sum MUST be NaN. If a Histogram includes +Inf or -Inf measurement, then +Inf or -Inf MUST be counted in Count and MUST be added to the Sum, potentially resulting in +Inf, -Inf or NaN in the Sum, the latter for example in case of adding +Inf to -Inf. Note that in this case the Sum of finite measurements is maske... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.014131013303995132,
-0.060175441205501556,
0.020840521901845932,
-0.053112275898456573,
-0.008556489832699299,
0.03612589091062546,
0.05759543552994728,
0.012164163403213024,
0.028564851731061935,
0.01606222428381443,
0.015262301079928875,
-0.0901353731751442,
0.027935704216361046,
-0.0... | 0.06386 |
negative Native Buckets and MUST contain a zero Native Bucket. Empty positive or negative Native Buckets SHOULD NOT be present. In case of Standard Schemas, the boundaries of a positive or negative Native Bucket with index `i` MUST be calculated as follows (using Python syntax): The upper inclusive limit of a positive ... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.017695581540465355,
0.019711820408701897,
0.018149783834815025,
-0.0834651067852974,
-0.01150071807205677,
-0.10226454585790634,
0.011304649524390697,
0.03135838359594345,
-0.02081005461513996,
-0.011988400481641293,
-0.008753038942813873,
-0.11574409157037735,
0.050147607922554016,
0.0... | 0.008389 |
all the measured values currently in the GaugeHistogram. The Gsum is a gauge semantically. A GaugeHistogram MUST measure values that are not NaN in either [Classic Buckets](#classic-buckets) or [Native Buckets](#native-buckets) or both. Measuring NaN is different for Classic and Native Buckets, see in their respective ... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0351467989385128,
-0.059228088706731796,
0.011964317411184311,
-0.03633410111069679,
-0.011658428236842155,
-0.024965178221464157,
0.06180023029446602,
-0.06325940787792206,
0.014527582563459873,
0.01304399874061346,
0.04337533935904503,
-0.07661482691764832,
0.023746289312839508,
0.005... | 0.02527 |
be used when it is impossible to determine the types of individual metrics from 3rd party systems. A Sample in a metric with the Unknown Type MUST have a Number or CompositeValue value. ## Text Format The OpenMetrics formats are Regular Chomsky Grammars, making writing quick and small parsers possible. Partial or inval... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.08132179081439972,
0.005651479586958885,
-0.037883367389440536,
-0.04789028316736221,
0.04470035061240196,
-0.06253572553396225,
-0.04978064075112343,
0.061033304780721664,
0.03044876456260681,
-0.026460807770490646,
0.01990636996924877,
-0.08345036208629608,
-0.023405127227306366,
0.04... | 0.185284 |
= label-name-initial-char / DIGIT label-name-initial-char = ALPHA / "\_" escaped-string = \*escaped-char escaped-string-non-empty = 1\*escaped-char escaped-char = normal-char escaped-char =/ BS ("n" / DQUOTE / BS) escaped-char =/ BS normal-char ; Any unicode character, except newline, double quote, and backslash normal... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
0.05354464799165726,
0.021338313817977905,
-0.06940287351608276,
0.020429929718375206,
-0.11701451987028122,
0.11945895105600357,
0.06230199709534645,
0.07873844355344772,
-0.03172917291522026,
-0.050462886691093445,
0.027671443298459053,
-0.10951582342386246,
0.0743715688586235,
0.0036314... | 0.084519 |
be used. In these Metrics, the quoted metric name MUST be moved inside the brackets as the first item without a label name and equal sign, in accordance with the ABNF. The metric names MUST be enclosed in double quotes in TYPE, UNIT, and HELP lines. Quoting and the alternative metric syntax MAY be used for any metric n... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.11165636032819748,
0.05045650526881218,
-0.10266050696372986,
-0.004336467944085598,
-0.04421315714716911,
-0.003158275503665209,
0.06643211841583252,
0.05982619896531105,
0.018036384135484695,
-0.020322000607848167,
-0.010535120964050293,
-0.12340278178453445,
0.06211681663990021,
0.04... | 0.116666 |
unit being a suffix (or infix) of the MetricFamily name directly to end-users may reduce the usability due to confusion about what the metric's unit is. A valid example for a `foo\_seconds\_total` metric with a unit of "seconds": ```openmetrics-add-eof # TYPE foo\_seconds\_total counter # UNIT foo\_seconds\_total secon... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.08232398331165314,
-0.021140052005648613,
-0.06543070077896118,
0.010921263135969639,
-0.080656036734581,
0.00537197245284915,
0.0004008558753412217,
0.061244506388902664,
0.06284495443105698,
-0.018012074753642082,
0.046293750405311584,
-0.093123659491539,
0.05935223773121834,
0.042791... | 0.123147 |
Timestamp MUST be added right after it. If exemplar is present, the Start Timestamp MUST be added before it. An example with a Metric with no labels, and a Sample with no timestamp and no Start Timestamp: ```openmetrics-add-eof # TYPE foo\_total counter foo\_total 17.0 ``` An example with a Metric with no labels, and a... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.05180608853697777,
-0.009660369716584682,
-0.04461897164583206,
-0.02830054610967636,
-0.0003848738269880414,
0.002840809989720583,
-0.011149195022881031,
0.03449730947613716,
0.09613538533449173,
-0.0031070313416421413,
0.08082585781812668,
-0.10650244355201721,
-0.03736800327897072,
0... | 0.045249 |
labels: ```openmetrics-add-eof # TYPE foo\_info info foo\_info{entity="controller",name="pretty name",version="8.2.7"} 1.0 foo\_info{entity="replica",name="prettier name",version="8.1.9"} 1.0 ``` Metric labels and Sample value labels MAY be in any order. #### Summary The Sample's value MUST be a CompositeValue. The Com... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0602603554725647,
0.010052165947854519,
-0.03479543328285217,
-0.02897646836936474,
-0.04590507596731186,
0.03526921570301056,
0.019486498087644577,
0.03796897083520889,
0.08176149427890778,
0.007507385220378637,
0.07858876138925552,
-0.08008208870887756,
0.006507800426334143,
-0.029651... | 0.074289 |
lengths define the number of consecutive buckets in the list following the excluded buckets. An example of when to keep empty positive or negative Native Buckets is to reduce the number of spans needed to represent the case where the offset between two spans is just 1, meaning that with the inclusion of one empty bucke... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.02183019369840622,
0.08491791039705276,
-0.01403103582561016,
-0.03601918742060661,
-0.00148825126234442,
-0.03279571607708931,
-0.0021991597022861242,
0.02980426885187626,
0.025184879079461098,
-0.01790459454059601,
0.01347621064633131,
-0.11274682730436325,
0.06713920831680298,
-0.033... | 0.04027 |
and GaugeHistograms do not have Start Timestamp. An example of a Metric with no labels, and one Sample value with no Timestamp, and no Exemplars: ```openmetrics-add-eof # TYPE acme\_http\_request\_seconds gaugehistogram acme\_http\_request\_seconds{path="/api/v1",method="GET"} {gcount:59,gsum:1.2e2,schema:7,zero\_thres... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.014176367782056332,
0.011772158555686474,
-0.03345370665192604,
0.019876066595315933,
-0.0022830371744930744,
0.018228482455015182,
0.03364533185958862,
0.010492631234228611,
0.04974658042192459,
-0.025593850761651993,
0.020421462133526802,
-0.13021722435951233,
0.015789521858096123,
-0... | 0.073993 |
support for this 2.0 version, both syntactically and semantically. We want to allow monitoring systems to get usable information from an OpenMetrics exposition without undue burden. If one were to strip away all metadata and structure and just look at an OpenMetrics exposition as an unordered set of samples, it should ... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.06348130106925964,
-0.027171626687049866,
-0.04087335243821144,
0.013023676350712776,
-0.00042462715646252036,
-0.03737686201930046,
-0.015893500298261642,
0.024877676740288734,
0.0895279124379158,
-0.017320089042186737,
0.035346537828445435,
-0.06778797507286072,
0.07159633189439774,
0... | 0.141162 |
and Kelvin metric are unlikely. Ratios are the base unit, not percentages. Where possible, raw data in the form of gauges or counters for the given numerator and denominator should be exposed. This has better mathematical properties for analysis and aggregation in the ingestors. Decibels are not a base unit as firstly,... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.09197551012039185,
-0.013266942463815212,
-0.1179908737540245,
0.00779402581974864,
-0.07004600763320923,
-0.053707823157310486,
-0.08308708667755127,
0.01884075254201889,
0.052817072719335556,
-0.05926211550831795,
-0.0299531277269125,
-0.11940103024244308,
0.003393827471882105,
0.0453... | -0.006346 |
counter is not getting increments doesn't invalidate that it still has its current value. There are cases where it may make sense to stop exposing a given Metric; see the section on Missing Data. In general changing a MetricFamily's Type, or adding or removing a label from its Metrics will be breaking to ingestors. A n... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.02935517393052578,
-0.05211638659238815,
-0.025894729420542717,
-0.0349319726228714,
-0.05581875890493393,
0.06523880362510681,
0.041175950318574905,
0.02360094152390957,
0.057221218943595886,
-0.04345487803220749,
0.023692382499575615,
-0.07374338060617447,
0.019159933552145958,
0.0152... | 0.12586 |
and Namespaces We aim for a balance between understandability, avoiding clashes, and succinctness in the naming of metrics and label names. Names are separated through underscores, so metric names end up being in “snake\_case”. While we strongly recommend the practices recommended in this document, other metric systems... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.11437991261482239,
-0.06694098562002182,
-0.05809822306036949,
-0.051802340894937515,
-0.045449696481227875,
-0.08363357186317444,
-0.008682689629495144,
0.039495259523391724,
0.0998808816075325,
-0.058511219918727875,
0.01500023901462555,
-0.03963581845164299,
0.05727599188685417,
0.01... | 0.165732 |
DNS software, even though isc\_bind\_ would be the more usual naming. Metric names prefixed by scrape\_ are used by ingestors to attach information related to individual expositions, so should not be exposed by applications directly. Metrics that have already been consumed and passed through a general purpose monitorin... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.14550527930259705,
-0.08980480581521988,
-0.047473154962062836,
-0.02005039155483246,
-0.044452473521232605,
-0.09669046103954315,
-0.0029334481805562973,
0.04826551675796509,
0.09670986980199814,
-0.014776352792978287,
-0.007416106294840574,
-0.015288506634533405,
-0.005157496780157089,
... | 0.226137 |
a total sum alongside other metrics is wrong, as this would result in double-counting upon aggregation in downstream ingestors. ``` wrong\_metric{label="a"} 1 wrong\_metric{label="b"} 6 wrong\_metric{label="total"} 7 ``` Labels of a Metric should be to the minimum needed to ensure uniqueness as every extra label is one... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.044319037348032,
-0.04696958512067795,
-0.015328558161854744,
0.025019805878400803,
-0.05124212056398392,
0.051296453922986984,
0.1061115488409996,
0.04011023789644241,
0.07941129803657532,
-0.05102178454399109,
0.022782914340496063,
-0.06729932129383087,
0.046758022159338,
0.0418636426... | 0.082541 |
to provide the relevant target metadata to the ingestor. In pull-based consumption the push-based approach could be taken, but more typically the ingestor already knows the metadata of the target a-priori such as from a machine database or service discovery system, and associates it with the metrics as it consumes the ... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.00822620838880539,
-0.0023901278618723154,
-0.027268458157777786,
-0.039110757410526276,
0.05012037232518196,
-0.0209589134901762,
0.03822847828269005,
0.04934424161911011,
0.05458079278469086,
-0.03104432299733162,
0.0016817975556477904,
-0.06822732836008072,
0.017360730096697807,
0.01... | 0.119631 |
5 minutes. Letting the ingestor calculate the increase over the data points they have consumed across expositions has better mathematical properties and is more resilient to scrape failures. Another example is the average event size of a histogram/summary. Exposing the average rate of increase of a counter since an app... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
0.020407777279615402,
0.04769515246152878,
-0.07389698177576065,
-0.020541928708553314,
-0.09623967111110687,
-0.001114981947466731,
-0.04514400660991669,
0.04416263476014137,
0.005167881026864052,
-0.005022220313549042,
-0.05405893549323082,
-0.042485564947128296,
0.0037304272409528494,
0... | 0.111319 |
by 1 at time 123. This would be a correct way to expose it in the text format: ``` # HELP my\_counter Good increment example # TYPE my\_counter counter my\_counter\_total 1 ``` As per the parent section, ingestors should be free to attach their own timestamps, so this would be incorrect: ``` # HELP my\_counter Bad incr... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0553736612200737,
-0.004517617169767618,
-0.012226096354424953,
0.04387187212705612,
-0.07852523773908615,
0.09973365813493729,
0.048266325145959854,
0.09287039190530777,
0.01152743399143219,
-0.04706018790602684,
0.039788275957107544,
-0.08472754061222076,
0.04273153096437454,
0.030034... | 0.129618 |
of labels in an info value, or metric name/label name/label value/help character limits. Specific limits run the risk of preventing reasonable use cases, for example while a given exposition may have an appropriate number of labels after passing through a general purpose monitoring system a few target labels may have b... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
0.0023992429487407207,
0.023750046268105507,
-0.03836407512426376,
-0.02400391735136509,
0.07550676167011261,
0.03150065243244171,
0.07367362827062607,
0.0555151142179966,
0.09123396873474121,
-0.07716270536184311,
-0.0009452964877709746,
-0.021118363365530968,
0.0141761414706707,
0.045394... | 0.179992 |
per hour might indicate a use case for then the use case may be more like event logging, not metric time series. ## Security Implementors MAY choose to offer authentication, authorization, and accounting; if they so choose, this SHOULD be handled outside of OpenMetrics. All exposer implementations SHOULD be able to sec... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0970635712146759,
0.06007114797830582,
-0.013228476978838444,
-0.03170347958803177,
-0.02974851243197918,
-0.10598684847354889,
0.010841570794582367,
-0.005066006910055876,
0.07171773165464401,
-0.019659142941236496,
-0.03822958469390869,
-0.009888905100524426,
-0.004829958081245422,
0.... | 0.175191 |
- Version: 1.0 - Status: Published - Date: November 2020 - Authors: Richard Hartmann, Ben Kochie, Brian Brazil, Rob Skillington Created in 2012, Prometheus has been the default for cloud-native observability since 2015. A central part of Prometheus' design is its text metric exposition format, called the Prometheus exp... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.054278019815683365,
0.005869881249964237,
-0.007801094092428684,
-0.011779875494539738,
0.1189134269952774,
-0.06552928686141968,
-0.03912677988409996,
0.010038670152425766,
0.014580846764147282,
0.030424391850829124,
-0.005463479086756706,
-0.049925804138183594,
0.00029007927514612675,
... | 0.196757 |
Timestamps MUST be Unix Epoch in seconds. Negative timestamps MAY be used. #### Strings Strings MUST only consist of valid UTF-8 characters and MAY be zero length. NULL (ASCII 0x0) MUST be supported. #### Label Labels are key-value pairs consisting of strings. Label names beginning with underscores are RESERVED and MUS... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.06318012624979019,
0.017891280353069305,
-0.08855069428682327,
-0.06253617256879807,
-0.0568634532392025,
-0.009784881956875324,
0.03206011280417442,
0.06377767771482468,
0.022635743021965027,
-0.09502256661653519,
0.06998182088136673,
-0.13233047723770142,
0.012017614208161831,
-0.0282... | 0.218154 |
infix in the text format. ##### Help Help is a string and SHOULD be non-empty. It is used to give a brief description of the MetricFamily for human consumption and SHOULD be short enough to be used as a tooltip. ##### MetricSet A MetricSet is the top level object exposed by OpenMetrics. It MUST consist of MetricFamilie... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.0656631588935852,
-0.05227445438504219,
-0.014232007786631584,
0.005275443196296692,
-0.004537890199571848,
-0.0003333331842441112,
0.09528281539678574,
0.08141075074672699,
0.0337991863489151,
-0.04170335456728935,
-0.0041801538318395615,
-0.03359907492995262,
0.024177061393857002,
0.0... | 0.182624 |
version of a compiler. A MetricPoint of an Info Metric contains a LabelSet. An Info MetricPoint's LabelSet MUST NOT have a label name which is the same as the name of a label of the LabelSet of its Metric. Info MAY be used to encode ENUMs whose values do not change over time, such as the type of a network interface. Me... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
0.020628802478313446,
-0.03050813265144825,
-0.05024617537856102,
-0.07002752274274826,
-0.04366738721728325,
-0.004396116826683283,
0.06213650107383728,
0.029097918421030045,
0.0682251900434494,
-0.0337572805583477,
-0.0030850868206471205,
-0.09669636189937592,
0.04154239967465401,
-0.006... | 0.2241 |
MAY be used when Histograms are too expensive and/or an average event size is sufficient. They MAY also be used for backwards compatibility, because some existing instrumentation libraries expose precomputed quantiles and do not support Histograms. Precomputed quantiles SHOULD NOT be used, because quantiles are not agg... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.04942198470234871,
-0.003024469595402479,
-0.027419043704867363,
-0.06240523234009743,
-0.0892224982380867,
0.013388416729867458,
0.0224284827709198,
0.04052077606320381,
0.14570030570030212,
-0.007490505464375019,
0.01809821091592312,
-0.07183025032281876,
-0.017407815903425217,
0.0530... | 0.179929 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.