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 |
|---|---|---|---|---|---|
metric-type =/ info / summary / unknown sample = metricname [labels] SP number [SP timestamp] [exemplar] LF exemplar = SP HASH SP labels SP number [SP timestamp] labels = "{" [label \*(COMMA label)] "}" label = label-name EQ DQUOTE escaped-string DQUOTE number = realnumber ; Case insensitive number =/ [SIGN] ("inf" / "... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.003763437271118164,
0.03204803913831711,
-0.03548821061849594,
-0.11621585488319397,
0.0058744498528540134,
0.013415931724011898,
0.04755428805947304,
0.07408197969198227,
0.005151193588972092,
-0.05153995379805565,
0.04446031525731087,
-0.06980657577514648,
0.05329766497015953,
0.01612... | 0.073237 |
They MAY be used anywhere else numbers are used. ###### Considerations: Canonical Numbers Numbers in the "le" label values of histograms and "quantile" label values of summary metrics are special in that they're label values, and label values are intended to be opaque. As end users will likely directly interact with th... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.08225053548812866,
0.03470780700445175,
-0.0780077576637268,
-0.06738819926977158,
-0.03336648643016815,
0.02565235272049904,
0.05688583478331566,
0.04879702255129814,
0.11391419172286987,
-0.05826359614729881,
0.004223851952701807,
-0.009629656560719013,
-0.007844984531402588,
0.008500... | 0.139375 |
be the suffix of the MetricFamily name. A valid example for a foo\_seconds metric with a unit of "seconds": ``` # TYPE foo\_seconds counter # UNIT foo\_seconds seconds ``` An invalid example, where the unit is not a suffix on the name: ``` # TYPE foo counter # UNIT foo seconds ``` It is also valid to have: ``` # TYPE f... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.07905760407447815,
-0.004689470864832401,
-0.02651786245405674,
0.014502840116620064,
-0.09507223218679428,
0.03603595867753029,
0.024296743795275688,
0.038885992020368576,
0.059758782386779785,
-0.03478415682911873,
0.02885502576828003,
-0.10468059033155441,
0.05817650631070137,
0.0499... | 0.131778 |
suffix `\_total`. If present the MetricPoint's Created Value Sample MetricName MUST have the suffix `\_created`. An example with a Metric with no labels, and a MetricPoint with no timestamp and no created: ``` # TYPE foo counter foo\_total 17.0 ``` An example with a Metric with no labels, and a MetricPoint with a times... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.06235724315047264,
-0.05174030736088753,
-0.005960563197731972,
0.018298272043466568,
-0.057488031685352325,
-0.01829330436885357,
0.04609304666519165,
0.018509604036808014,
0.13847312331199646,
-0.012294059619307518,
0.06868094950914383,
-0.08608616888523102,
0.030912894755601883,
0.03... | 0.104567 |
MUST also appear in a Sample with a MetricName with the suffix "\_count". Buckets MUST be sorted in number increasing order of "le", and the value of the "le" label MUST follow the rules for Canonical Numbers. An example of a Metric with no labels and a MetricPoint with Sum, Count, and Created values, and with 12 bucke... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
0.04458596184849739,
0.0016966280527412891,
0.04421239346265793,
-0.07925049215555191,
-0.031175674870610237,
0.021492596715688705,
0.04639361426234245,
0.015379988588392735,
0.03035365231335163,
-0.02362448163330555,
-0.04713094234466553,
-0.10133349150419235,
0.08160047233104706,
0.00748... | 0.002731 |
which do not provide hard or soft real time guarantees, so it can not make any real time guarantees itself. Latency and jitter properties of OpenMetrics are as imprecise as the underlying network, operating systems, CPUs, and the like. It is sufficiently accurate for aggregations to be used as a basis for decision-maki... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.04584924131631851,
0.02609839290380478,
-0.028418419882655144,
-0.036601822823286057,
-0.0037141980137676,
-0.09467143565416336,
-0.02394620142877102,
0.03562219813466072,
0.0631491169333458,
0.0004319424042478204,
0.0028914541471749544,
0.0065636648796498775,
-0.0039764088578522205,
-0... | 0.193454 |
of emergent behaviour of complex systems. As values can be floating point, sub-base-unit precision is built into the standard. Similarly, mixing bits and bytes is confusing, so bytes are chosen as the base. While Kelvin is a better base unit in theory, in practice most existing hardware exposes Celsius. Kilograms are t... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.05490642413496971,
-0.006106055807322264,
-0.08166094869375229,
-0.01336196344345808,
-0.03790827840566635,
-0.06858514249324799,
-0.02627803012728691,
0.046541761606931686,
0.11714519560337067,
0.005135586950927973,
-0.038107845932245255,
-0.1504487246274948,
0.034494731575250626,
0.05... | 0.092023 |
for exposition easier. Metrics and samples SHOULD NOT appear and disappear from exposition to exposition, for example a counter is only useful if it has history. In principle, a given Metric should be present in exposition from when the process starts until the process terminates. It is often not possible to know in ad... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.08187277615070343,
-0.07039482146501541,
-0.039561010897159576,
-0.008569637313485146,
0.003760735737159848,
0.08868413418531418,
0.044292058795690536,
0.004752771463245153,
0.1793539971113205,
-0.050057634711265564,
-0.0012567919911816716,
-0.03015301190316677,
0.01563004031777382,
0.0... | 0.135541 |
exposition SHOULD take no more than a second. Metrics from legacy systems serialized through OpenMetrics may take longer. For this reason, no hard performance assumptions can be made. Exposition SHOULD be of the most recent state. For example, a thread serving the exposition request SHOULD NOT rely on cached values, to... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.1077611967921257,
-0.025860201567411423,
-0.038101039826869965,
-0.0637703612446785,
-0.02439587563276291,
0.0007864524959586561,
-0.016845494508743286,
-0.0086622079834342,
0.08488423377275467,
-0.037361834198236465,
-0.06898291409015656,
-0.07278935611248016,
0.00903740618377924,
0.02... | 0.205846 |
metric is given its metric name. For a common very well known existing piece of software, the name of the software itself may be sufficiently distinguishing. For example bind\_ is probably sufficient for the DNS software, even though isc\_bind\_ would be the more usual naming. Metric names prefixed by scrape\_ are used... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.12368429452180862,
-0.08637081831693649,
-0.04726659879088402,
-0.03476274758577347,
-0.033356960862874985,
-0.0825769305229187,
0.007190247066318989,
0.05569213256239891,
0.10723918676376343,
-0.03280545771121979,
-0.021860914304852486,
-0.05253266543149948,
0.017091380432248116,
0.001... | 0.220528 |
it's not always useful. For example, mixing voltage and fan speed is not meaningful. As a reminder, OpenMetrics is built with the assumption that ingestors can process and perform aggregations on data. Exposing a total sum alongside other metrics is wrong, as this would result in double-counting upon aggregation in dow... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.053763385862112045,
-0.023918667808175087,
-0.04545227065682411,
-0.004489392042160034,
-0.006120576523244381,
0.05258942022919655,
0.059135518968105316,
0.023923836648464203,
0.10026390850543976,
-0.06342681497335434,
0.02810313180088997,
-0.046423304826021194,
0.05737786740064621,
0.0... | 0.113926 |
an exposer. Common examples would be software version, compiler version, or Git commit SHA. #### Supporting Target Metadata in both Push-based and Pull-based Systems In push-based consumption, it is typical for the exposer to provide the relevant target metadata to the ingestor. In pull-based consumption the push-based... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.01654793508350849,
-0.018660584464669228,
-0.030784402042627335,
-0.03591447323560715,
0.060576628893613815,
-0.04828004539012909,
-0.030077021569013596,
0.06800619512796402,
0.06994769722223282,
0.018509332090616226,
0.02333689294755459,
-0.02137828804552555,
0.008294143714010715,
-0.0... | 0.179599 |
Exposition should be of raw values which are useful over arbitrary time periods. As an example, you should not expose a gauge with the average rate of increase of a counter over the last 5 minutes. Letting the ingestor calculate the increase over the data points they have consumed across expositions has better mathemat... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
0.01420663297176361,
0.05840581655502319,
-0.06230537220835686,
-0.012772141955792904,
-0.053779661655426025,
0.08025040477514267,
-0.01127445138990879,
0.04409920424222946,
0.03984558954834938,
-0.013747749850153923,
-0.052195485681295395,
-0.05953768640756607,
0.008627480827271938,
0.049... | 0.106602 |
should be up to the ingestor to apply their own timestamps to samples they ingest. #### Tracking When Metrics Last Changed Presume you had a counter my\_counter which was initialized, and then later incremented by 1 at time 123. This would be a correct way to expose it in the text format: ``` # HELP my\_counter Good in... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.06931750476360321,
-0.012591267935931683,
0.023899808526039124,
0.027781065553426743,
-0.038983236998319626,
0.08357764780521393,
0.05416264757514,
0.09928543120622635,
0.01893138326704502,
-0.05900125950574875,
0.04210691154003143,
-0.09378746151924133,
0.037318598479032516,
0.05913530... | 0.143704 |
standard does not prescribe any particular limits on the number of samples exposed by a single exposition, the number of labels that may be present, the number of states a stateset may have, the number of labels in an info value, or metric name/label name/label value/help character limits. Specific limits run the risk ... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
0.0236801877617836,
-0.00021435650705825537,
-0.04171663150191307,
-0.042240310460329056,
0.06675533205270767,
0.07154583185911179,
0.03216021507978439,
0.056096043437719345,
0.05819128081202507,
-0.053002290427684784,
-0.001235772273503244,
-0.04343738779425621,
-0.005096442997455597,
0.0... | 0.148878 |
these strings change over time older strings will still need to be stored for at least some time, incurring extra cost. Assuming the 10 million times series from the last paragraph, 100MB of unique strings per hour might indicate a use case for then the use case may be more like event logging, not metric time series. T... | https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec.md | main | prometheus | [
-0.08409638702869415,
0.048964496701955795,
-0.03294972702860832,
-0.02480650506913662,
-0.06538158655166626,
-0.05429316684603691,
0.0035381470806896687,
0.004325122106820345,
0.11571758985519409,
-0.04471566528081894,
0.007537065539509058,
0.020391222089529037,
0.014147724024951458,
0.03... | 0.10662 |
- Version: 1.0 - Status: Published - Date: April 2023 This document is intended to define and standardise the API, wire format, protocol and semantics of the existing, widely and organically adopted protocol, and not to propose anything new. The remote write specification is intended to document the standard for how Pr... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec.md | main | prometheus | [
-0.12627026438713074,
0.017381537705659866,
-0.005345076322555542,
0.017850574105978012,
0.01238823588937521,
-0.09251546859741211,
-0.03756026551127434,
-0.010267634876072407,
-0.04074301943182945,
0.049150966107845306,
0.01830320991575718,
0.016750166192650795,
0.03441139683127403,
0.023... | 0.194433 |
the HTTP request: - `Content-Encoding: snappy` - `Content-Type: application/x-protobuf` - `User-Agent: ` - `X-Prometheus-Remote-Write-Version: 0.1.0` Clients MAY allow users to send custom HTTP headers; they MUST NOT allow users to configure them in such a way as to send reserved headers. For more info see https://gith... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec.md | main | prometheus | [
-0.1072574108839035,
0.02168719656765461,
0.0038661241997033358,
-0.057221919298172,
-0.03242459520697594,
-0.14881983399391174,
-0.09439253807067871,
0.005200520623475313,
-0.054898060858249664,
0.02859068289399147,
-0.018993448466062546,
-0.0011318385368213058,
0.03135545179247856,
-0.01... | 0.033079 |
server. They MUST NOT retry write requests on HTTP 2xx and 4xx responses other than 429. They MAY retry on HTTP 429 responses, which could result in senders "falling behind" if the server cannot keep up. This is done to ensure data is not lost when there are server side errors, and progress is made when there are clien... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec.md | main | prometheus | [
-0.10641966015100479,
-0.030628224834799767,
0.03897492587566376,
0.03463388979434967,
0.02218683995306492,
-0.1381368190050125,
-0.026448411867022514,
-0.06387398391962051,
0.02588774636387825,
0.04127594828605652,
0.004119888413697481,
0.026504192501306534,
-0.0021373520139604807,
-0.027... | 0.203238 |
"instance" label, as these are typically added by service discovery in the Sender. These are not mandatory. ## Future Plans This section contains speculative plans that are not considered part of protocol specification, but are mentioned here for completeness. \*\*Transactionality\*\* Prometheus aims at being "transact... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec.md | main | prometheus | [
-0.12412522733211517,
0.04059860482811928,
0.014755924232304096,
0.02817573770880699,
-0.012025220319628716,
-0.1018570140004158,
0.024579836055636406,
-0.03718238323926926,
-0.00967281311750412,
0.009413903579115868,
-0.013803262263536453,
-0.07500036060810089,
0.04295427352190018,
0.0004... | 0.157227 |
to ensure the integrity of the ecosystem and to prevent confusing/forking the community into "prometheus-agents-that-can-write-to-prometheus" and those that can’t. | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec.md | main | prometheus | [
-0.08416544646024704,
0.048389505594968796,
0.02130708657205105,
-0.0006652945885434747,
0.05735423415899277,
-0.1072070300579071,
0.012420912273228168,
-0.013109838590025902,
0.07981771975755692,
0.021985750645399094,
0.02358202449977398,
-0.012897753156721592,
-0.032643791288137436,
-0.0... | 0.349499 |
\* Version: 2.0-rc.4 \* Status: \*\*Experimental\*\* \* Date: May 2024 The Remote-Write specification, in general, is intended to document the standard for how Prometheus and Prometheus Remote-Write compatible senders send data to Prometheus or Prometheus Remote-Write compatible receivers. This document is intended to ... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.06802971661090851,
0.02528221160173416,
0.03595561534166336,
-0.0039005805738270283,
0.03920230269432068,
-0.11377301812171936,
-0.05900757759809494,
0.03999771922826767,
-0.03908455744385719,
0.06181204691529274,
0.007319889031350613,
-0.0016187271103262901,
0.01910504326224327,
-0.000... | 0.153088 |
e.g. usually it means storing received data in a database, but also just validating, splitting or enhancing it. \* `Written` refers to data the `Receiver` has received and is accepting. Whether or not it has ingested this data to persistent storage, written it to a WAL, etc. is up to the `Receiver`. The only distinctio... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.0902414545416832,
0.026555592194199562,
-0.08878970891237259,
-0.008014948107302189,
-0.04011351242661476,
-0.01914300210773945,
0.04465542733669281,
0.029492970556020737,
0.032132938504219055,
0.011720990762114525,
0.015397853218019009,
0.02266153320670128,
0.09975966811180115,
-0.0459... | 0.289543 |
Messages might not have this feature. #### X-Prometheus-Remote-Write-Version ``` X-Prometheus-Remote-Write-Version: ``` When talking to 1.x Receivers, Senders MUST use `X-Prometheus-Remote-Write-Version: 0.1.0` for backward compatibility. Otherwise, Senders SHOULD use the newest Remote-Write version it is compatible wi... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.037799105048179626,
0.022984975948929787,
0.030659107491374016,
-0.004910647869110107,
-0.004453206434845924,
-0.12550818920135498,
-0.012595669366419315,
-0.02765188366174698,
-0.010859964415431023,
0.016814041882753372,
0.004218072630465031,
0.001440740656107664,
0.04783153161406517,
... | 0.10637 |
contains some invalid or otherwise unwritten samples, which represents a partial write case. In such a case, the Receiver MUST return non-2xx status code following the [Invalid Samples](#invalid-samples) and [Retry on Partial Writes](#retries-on-partial-writes) sections. #### Unsupported Request Content Receivers MUST ... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.010667910799384117,
-0.033004503697156906,
0.04352925345301628,
-0.057211242616176605,
0.020074578002095222,
-0.0604611299932003,
-0.05510096997022629,
-0.003512165043503046,
0.04487134888768196,
0.0551249235868454,
-0.036025624722242355,
0.010708479210734367,
0.03557989373803139,
0.013... | 0.024999 |
protocol is breaking compatibility with 1.x by introducing a new, mandatory `io.prometheus.write.v2.Request` Protobuf Message and deprecating the `prometheus.WriteRequest`. 2.x Senders MAY support 1.x Receivers by allowing users to configure what content type Senders should use. 2.x Senders also MAY automatically fall ... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.057784173637628555,
-0.005897320806980133,
0.06061524525284767,
-0.0022035026922822,
0.011847474612295628,
-0.1378539651632309,
-0.02530479058623314,
-0.024406764656305313,
-0.029419170692563057,
0.041262634098529816,
0.0032395843882113695,
-0.026568280532956123,
0.02263452671468258,
0.... | 0.117793 |
exemplar in ms. // // For Go, see github.com/prometheus/prometheus/model/timestamp/timestamp.go // for conversion from/to time.Time to Prometheus timestamp. int64 timestamp = 3; } // Sample represents series sample. message Sample { // value of the sample. double value = 1; // timestamp represents timestamp of the samp... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.07986880093812943,
0.023419992998242378,
-0.04406045004725456,
0.0022092582657933235,
-0.007180177606642246,
-0.07305485755205154,
-0.03345957025885582,
0.07896945625543594,
0.06207594275474548,
-0.0567086786031723,
0.030684402212500572,
-0.05484975874423981,
-0.02092786878347397,
0.009... | 0.187299 |
or `Metadata.help\_ref` are not provided. References MUST point to the existing index in the `symbols` string array. #### Series Labels The complete set of labels MUST be sent with each `Sample` or `Histogram` sample. Additionally, the label set associated with samples: \* SHOULD contain a `\_\_name\_\_` label. \* MUST... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.05626453831791878,
0.016417615115642548,
-0.06783279776573181,
-0.04921405762434006,
-0.08327396214008331,
0.03693149611353874,
0.13011600077152252,
0.014413261786103249,
-0.0023691921960562468,
-0.043157245963811874,
0.019518215209245682,
-0.09336040914058685,
0.05920892953872681,
0.03... | 0.104376 |
(e.g. deduplicate) incoming exemplars. ## Out of Scope The same as in [1.0](./remote\_write\_spec.md#out-of-scope). ## Future Plans This section contains speculative plans that are not considered part of protocol specification yet but are mentioned here for completeness. Note that 2.0 specification completed [2 of 3 fu... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.1081060916185379,
0.03380798548460007,
0.05387163534760475,
0.000035516986827133223,
-0.003034243592992425,
-0.13981427252292633,
-0.058259084820747375,
0.013129185885190964,
-0.006632656790316105,
0.052637916058301926,
-0.003930505830794573,
-0.01651529222726822,
0.01777774840593338,
0... | 0.088839 |
queues, and then writes happen sequentially in each queue. This guarantees samples for the same series are delivered in order, but samples for different series are sent in parallel - and potentially "out of order" between different series. \*\*What are the differences between Remote-Write 2.0 and OpenTelemetry's OTLP p... | https://github.com/prometheus/docs/blob/main/docs/specs/prw/remote_write_spec_2_0.md | main | prometheus | [
-0.04853193834424019,
-0.014019817113876343,
-0.009404624812304974,
0.008999197743833065,
-0.07501833140850067,
-0.1251135766506195,
-0.0402723029255867,
-0.008326179347932339,
0.08511830866336823,
0.015426955185830593,
-0.001103030750527978,
0.02436155267059803,
-0.02983861416578293,
-0.0... | 0.177445 |
## What is Prometheus? [Prometheus](https://github.com/prometheus) is an open-source systems monitoring and alerting toolkit originally built at [SoundCloud](http://soundcloud.com). Since its inception in 2012, many companies and organizations have adopted Prometheus, and the project has a very active developer and use... | https://github.com/prometheus/docs/blob/main/docs/introduction/overview.md | main | prometheus | [
-0.08597481995820999,
-0.0132818054407835,
-0.008691787719726562,
-0.002795935608446598,
0.04465567693114281,
-0.09295661747455597,
-0.00480693532153964,
-0.03561750054359436,
0.08952896296977997,
-0.01847437210381031,
-0.026146873831748962,
-0.02567369118332863,
0.0015038152923807502,
-0.... | 0.270323 |
go to during an outage to allow you to quickly diagnose problems. Each Prometheus server is standalone, not depending on network storage or other remote services. You can rely on it when other parts of your infrastructure are broken, and you do not need to setup extensive infrastructure to use it. ## When does it not f... | https://github.com/prometheus/docs/blob/main/docs/introduction/overview.md | main | prometheus | [
-0.031075824052095413,
0.017427988350391388,
0.00864025391638279,
0.01736881397664547,
-0.023667629808187485,
-0.1335451304912567,
-0.029957963153719902,
0.025159478187561035,
-0.01780412718653679,
-0.0045721204951405525,
-0.03145924583077431,
-0.010336154140532017,
-0.0008428739383816719,
... | 0.105944 |
## Prometheus vs. Graphite ### Scope [Graphite](http://graphite.readthedocs.org/en/latest/) focuses on being a passive time series database with a query language and graphing features. Any other concerns are addressed by external components. Prometheus is a full monitoring and trending system that includes built-in and... | https://github.com/prometheus/docs/blob/main/docs/introduction/comparison.md | main | prometheus | [
-0.11456006020307541,
-0.006496779154986143,
0.012721355073153973,
0.02273395285010338,
0.03467169776558876,
-0.11998394876718521,
-0.031242715194821358,
0.03351248800754547,
-0.01667981781065464,
0.03692391514778137,
-0.023274002596735954,
-0.005040992517024279,
0.0018251502187922597,
0.0... | 0.253056 |
as labels, which are called tags. In addition, InfluxDB has a second level of labels called fields, which are more limited in use. InfluxDB supports timestamps with up to nanosecond resolution, and float64, int64, bool, and string data types. Prometheus, by contrast, supports the float64 data type with limited support ... | https://github.com/prometheus/docs/blob/main/docs/introduction/comparison.md | main | prometheus | [
-0.07058680802583694,
0.01975681446492672,
-0.008315197192132473,
0.021525397896766663,
0.018117748200893402,
-0.08915097266435623,
-0.014189889654517174,
0.0011877118377014995,
0.0873064175248146,
0.0023750714026391506,
-0.013666825369000435,
-0.020084552466869354,
0.003157681552693248,
0... | 0.177449 |
label values, while OpenTSDB is more restrictive. OpenTSDB also lacks a full query language, only allowing simple aggregation and math via its API. ### Storage [OpenTSDB](http://opentsdb.net/)'s storage is implemented on top of [Hadoop](http://hadoop.apache.org/) and [HBase](http://hbase.apache.org/). This means that i... | https://github.com/prometheus/docs/blob/main/docs/introduction/comparison.md | main | prometheus | [
-0.018589027225971222,
0.017520340159535408,
-0.05166777968406677,
0.044181399047374725,
-0.01164232101291418,
-0.06853767484426498,
-0.04377429932355881,
0.08548645675182343,
0.007885885424911976,
-0.009150044061243534,
-0.07015787065029144,
-0.017106585204601288,
0.03292640671133995,
-0.... | 0.201227 |
for collecting multi-dimensional metrics via labels and annotations. Both have extensive integrations, and Sensu natively supports collecting metrics from all Prometheus exporters. Both are capable of forwarding observability data to third-party data platforms (e.g. event stores or TSDBs). Where Sensu and Prometheus di... | https://github.com/prometheus/docs/blob/main/docs/introduction/comparison.md | main | prometheus | [
-0.0523071363568306,
-0.06557667255401611,
-0.01602456159889698,
0.02554710954427719,
0.029772885143756866,
-0.06577031314373016,
0.0006380414706654847,
0.04226433113217354,
0.052679311484098434,
0.05923180654644966,
-0.01902424730360508,
-0.09316529333591461,
-0.04421241208910942,
0.06298... | 0.325361 |
Prometheus LTS are selected releases of Prometheus that receive bugfixes for an extended period of time. Every 6 weeks, a new Prometheus minor release cycle begins. After those 6 weeks, minor releases generally no longer receive bugfixes. If a user is impacted by a bug in a minor release, they often need to upgrade to ... | https://github.com/prometheus/docs/blob/main/docs/introduction/release-cycle.md | main | prometheus | [
-0.09433530271053314,
-0.005882890895009041,
0.08408952504396439,
-0.01225019246339798,
0.021858923137187958,
-0.1184353157877922,
-0.09030942618846893,
-0.02011989802122116,
-0.0676836371421814,
-0.011081667616963387,
0.027138618752360344,
0.0598946139216423,
0.005804151296615601,
-0.0177... | 0.130451 |
### Alert An alert is the outcome of an alerting rule in Prometheus that is actively firing. Alerts are sent from Prometheus to the Alertmanager. ### Alertmanager The [Alertmanager](/docs/alerting/latest/overview/) takes in alerts, aggregates them into groups, de-duplicates, applies silences, throttles, and then sends ... | https://github.com/prometheus/docs/blob/main/docs/introduction/glossary.md | main | prometheus | [
-0.08557609468698502,
0.007567031309008598,
-0.01990678533911705,
0.016307413578033447,
0.026291154325008392,
-0.10358461737632751,
0.06213643029332161,
0.015139307826757431,
0.06921569257974625,
-0.013134032487869263,
-0.043012794107198715,
-0.03799626976251602,
0.07806293666362762,
0.002... | 0.310303 |
is a Prometheus feature that allows sending ingested samples on the fly to other systems, such as long term storage. ### Remote Write Adapter Not all systems directly support remote write. A remote write adapter sits between Prometheus and another system, converting the samples in the remote write into a format the oth... | https://github.com/prometheus/docs/blob/main/docs/introduction/glossary.md | main | prometheus | [
-0.08468729257583618,
0.006299886386841536,
-0.002434821566566825,
0.029919501394033432,
0.04821792617440224,
-0.11987574398517609,
0.031105902045965195,
-0.0249394029378891,
0.06455647200345993,
-0.02151060663163662,
-0.002115484792739153,
0.0068140109069645405,
0.05441746488213539,
-0.02... | 0.265869 |
## General ### What is Prometheus? Prometheus is an open-source system monitoring and alerting toolkit with an active ecosystem. It is the only system directly supported by [Kubernetes](https://kubernetes.io/) and the de facto standard across the [cloud native ecosystem](https://landscape.cncf.io/). See the [overview](... | https://github.com/prometheus/docs/blob/main/docs/introduction/faq.md | main | prometheus | [
-0.05473778396844864,
0.015363489277660847,
0.03735745698213577,
0.012973708100616932,
0.04458623006939888,
-0.1350136697292328,
0.00654272036626935,
-0.029564496129751205,
0.023115424439311028,
0.02014726586639881,
-0.035966869443655014,
-0.04097677394747734,
0.022572550922632217,
-0.0060... | 0.259705 |
and process metrics, not an event logging system. The Grafana blog post [Logs and Metrics and Graphs, Oh My!](https://grafana.com/blog/2016/01/05/logs-and-metrics-and-graphs-oh-my/) provides more details about the differences between logs and metrics. If you want to extract Prometheus metrics from application logs, Gra... | https://github.com/prometheus/docs/blob/main/docs/introduction/faq.md | main | prometheus | [
-0.08253920823335648,
-0.02476665750145912,
-0.01305016502737999,
-0.012913764454424381,
-0.02250048704445362,
-0.11380671709775925,
0.011651728302240372,
0.028279980644583702,
0.03899722546339035,
0.027291230857372284,
-0.04461129382252693,
-0.05796753615140915,
-0.02330469898879528,
0.05... | 0.205219 |
if you need integer precision above 253 but below 263. In principle, support for different sample value types (including some kind of big integer, supporting even more than 64 bit) could be implemented, but it is not a priority right now. A counter, even if incremented one million times per second, will only run into p... | https://github.com/prometheus/docs/blob/main/docs/introduction/faq.md | main | prometheus | [
0.007048817351460457,
-0.07816898822784424,
-0.08374636620283127,
-0.08976607769727707,
-0.10242223739624023,
0.01053618174046278,
-0.028897162526845932,
0.02395090088248253,
0.0006072943797335029,
0.00014110305346548557,
-0.0693964809179306,
-0.023156648501753807,
0.011934323236346245,
-0... | 0.057311 |
See the [github.com/prometheus/proposals](https://github.com/prometheus/proposals) repository to see all the past and current proposals for the Prometheus Ecosystem. If you are interested in creating a new proposal, read our [proposal process](https://github.com/prometheus/proposals#proposal-process). ## Problem statem... | https://github.com/prometheus/docs/blob/main/docs/introduction/design-doc.md | main | prometheus | [
-0.06075328588485718,
0.02074912190437317,
0.037803489714860916,
-0.016389362514019012,
0.023731183260679245,
-0.10701010376214981,
-0.142466738820076,
0.017117032781243324,
0.008684000931680202,
0.015162668190896511,
-0.07396457344293594,
-0.0065230028703808784,
-0.012129269540309906,
-0.... | 0.156011 |
Welcome to Prometheus! Prometheus is a monitoring platform that collects metrics from monitored targets by scraping metrics HTTP endpoints on these targets. This guide will show you how to install, configure and monitor our first resource with Prometheus. You'll download, install and run Prometheus. You'll also downloa... | https://github.com/prometheus/docs/blob/main/docs/introduction/first_steps.md | main | prometheus | [
-0.011091533116996288,
0.015371989458799362,
-0.08834008127450943,
0.030206743627786636,
0.04170955717563629,
-0.11057576537132263,
0.006511716637760401,
0.019586661830544472,
0.013881971128284931,
0.019326617941260338,
-0.04346970468759537,
-0.044138289988040924,
-0.036948103457689285,
-0... | 0.20917 |
and choose the "Table" tab. As you can gather from http://localhost:9090/metrics, one metric that Prometheus exports about itself is called `promhttp\_metric\_handler\_requests\_total` (the total number of `/metrics` requests the Prometheus server has served). Go ahead and enter this into the expression console: ``` pr... | https://github.com/prometheus/docs/blob/main/docs/introduction/first_steps.md | main | prometheus | [
-0.05142828822135925,
-0.016163591295480728,
-0.05695071816444397,
0.04078379645943642,
-0.05303625762462616,
-0.09421661496162415,
-0.013263950124382973,
-0.0020345922093838453,
0.033792950212955475,
-0.006278757005929947,
-0.03632224351167679,
-0.07647441327571869,
0.011412312276661396,
... | 0.117864 |
The following is only a selection of some of the major features we plan to implement in the near future. To get a more complete overview of planned features and current work, see the issue trackers for the various repositories, for example, the [Prometheus server](https://github.com/prometheus/prometheus/issues). ### S... | https://github.com/prometheus/docs/blob/main/docs/introduction/roadmap.md | main | prometheus | [
-0.08999001234769821,
0.04301057010889053,
-0.022052355110645294,
0.004593526944518089,
-0.007911288179457188,
-0.11779878288507462,
-0.032061174511909485,
-0.007020608521997929,
0.013159925118088722,
0.008606119081377983,
-0.02518051490187645,
-0.028953278437256813,
0.048374127596616745,
... | 0.214927 |
There is a [subreddit](https://www.reddit.com/r/prometheusmonitoring) collecting all Prometheus-related resources on the internet. The following selection of resources are particularly useful to get started with Prometheus. [Awesome Prometheus](https://github.com/roaldnefs/awesome-prometheus) contains a more comprehens... | https://github.com/prometheus/docs/blob/main/docs/introduction/media.md | main | prometheus | [
-0.1077973023056984,
-0.060717128217220306,
0.010691646486520767,
-0.011937092989683151,
0.034004468470811844,
-0.09112885594367981,
-0.011142204515635967,
-0.027609914541244507,
-0.05431016534566879,
-0.027348343282938004,
-0.0255705788731575,
-0.028116270899772644,
0.023228183388710022,
... | 0.221582 |
Prometheus has the ability to log all the queries run by the engine to a log file, as of 2.16.0. This guide demonstrates how to use that log file, which fields it contains, and provides advanced tips about how to operate the log file. ## Enable the query log The query log can be toggled at runtime. It can therefore be ... | https://github.com/prometheus/docs/blob/main/docs/guides/query-log.md | main | prometheus | [
-0.005958943162113428,
0.028088737279176712,
0.011187826283276081,
0.05999673530459404,
0.017139332368969917,
-0.15893951058387756,
0.009931282140314579,
-0.019419699907302856,
-0.011540981009602547,
0.011111492291092873,
-0.03772079199552536,
-0.027782928198575974,
0.009242943488061428,
-... | 0.147992 |
``` ## Rotating the query log Prometheus will not rotate the query log itself. Instead, you can use external tools to do so. One of those tools is logrotate. It is enabled by default on most Linux distributions. Here is an example of file you can add as `/etc/logrotate.d/prometheus`: ``` /prometheus/query.log { daily r... | https://github.com/prometheus/docs/blob/main/docs/guides/query-log.md | main | prometheus | [
-0.04193637892603874,
0.060661863535642624,
0.003927378915250301,
0.03616829216480255,
-0.019411582499742508,
-0.07902400940656662,
-0.02583712339401245,
-0.01832893118262291,
0.005229400470852852,
0.03357605263590813,
-0.013754122890532017,
0.04638804495334625,
0.025188369676470757,
-0.00... | 0.081289 |
Prometheus supports [basic authentication](https://en.wikipedia.org/wiki/Basic\_access\_authentication) (aka "basic auth") for connections to the Prometheus [expression browser](/docs/visualization/browser) and [HTTP API](/docs/prometheus/latest/querying/api). NOTE: This tutorial covers basic auth connections \*to\* Pr... | https://github.com/prometheus/docs/blob/main/docs/guides/basic-auth.md | main | prometheus | [
-0.11404556781053543,
0.013533986173570156,
-0.07934417575597763,
-0.009403443895280361,
-0.043312832713127136,
-0.15540902316570282,
0.03584231808781624,
0.0025307978503406048,
-0.035598330199718475,
-0.026681432500481606,
-0.012046818621456623,
-0.01909218169748783,
0.07787299901247025,
... | 0.123664 |
This guide will introduce you to the multi-target exporter pattern. To achieve this we will: \* describe the multi-target exporter pattern and why it is used, \* run the [blackbox](https://github.com/prometheus/blackbox\_exporter) exporter as an example of the pattern, \* configure a custom query module for the blackbo... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.0863836407661438,
-0.004055566154420376,
-0.07572845369577408,
0.032623618841171265,
0.011734803207218647,
-0.07057487964630127,
-0.01784924976527691,
-0.00751826586201787,
-0.03356665372848511,
-0.04502281919121742,
-0.029890067875385284,
-0.10588066279888153,
0.04114013537764549,
-0.0... | 0.182081 |
TYPE process\_open\_fds gauge process\_open\_fds 7 # HELP process\_resident\_memory\_bytes Resident memory size in bytes. # TYPE process\_resident\_memory\_bytes gauge process\_resident\_memory\_bytes 7.8848e+06 # HELP process\_start\_time\_seconds Start time of the process since unix epoch in seconds. # TYPE process\_... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.02011239156126976,
0.04606717452406883,
-0.1025824174284935,
0.044537656009197235,
0.030223289504647255,
-0.09366254508495331,
0.03990292176604271,
0.10842816531658173,
0.0704093649983406,
-0.004330567549914122,
-0.024394575506448746,
-0.05267831310629845,
-0.03531459718942642,
-0.01819... | 0.267 |
inside the docker container called `config.yml` which is a copy of [blackbox.yml](https://github.com/prometheus/blackbox\_exporter/blob/master/blackbox.yml) in the github repo. We will copy this file, [adapt](https://github.com/prometheus/blackbox\_exporter/blob/master/CONFIGURATION.md) it to our own needs and tell the... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.0005993319791741669,
0.028755279257893562,
-0.06623563170433044,
0.03296617791056633,
0.04934310540556908,
-0.07506456971168518,
-0.0743294209241867,
-0.01727929897606373,
-0.017468344420194626,
-0.03888747841119766,
-0.04117470979690552,
-0.04840948432683945,
0.004278924781829119,
-0.0... | 0.086327 |
HELP probe\_http\_ssl Indicates if SSL was used for the final redirect # TYPE probe\_http\_ssl gauge probe\_http\_ssl 1 # HELP probe\_http\_status\_code Response HTTP status code # TYPE probe\_http\_status\_code gauge probe\_http\_status\_code 200 # HELP probe\_http\_uncompressed\_body\_length Length of uncompressed re... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.05731205642223358,
0.052011191844940186,
-0.04961185157299042,
0.0318681001663208,
0.012906293384730816,
-0.06364616006612778,
-0.02824266441166401,
-0.07909481227397919,
0.025734495371580124,
-0.038162700831890106,
0.020114919170737267,
-0.04387823864817619,
0.003142748260870576,
0.042... | 0.066581 |
`metrics\_path` to `/probe` and the parameters under `params:` in the Prometheus config file `prometheus.yml`: ```yaml global: scrape\_interval: 5s scrape\_configs: - job\_name: blackbox # To get metrics about the exporter itself metrics\_path: /metrics static\_configs: - targets: - localhost:9115 # For Windows and mac... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.04759059101343155,
0.025485754013061523,
-0.01666887477040291,
0.05516517534852028,
0.03272964432835579,
-0.13296861946582794,
-0.028223708271980286,
-0.015842106193304062,
-0.022030746564269066,
-0.042351868003606796,
-0.04182611405849457,
-0.08224841207265854,
0.0014397810446098447,
-... | 0.107151 |
# Target to probe with http - https://prometheus.io # Target to probe with https - http://example.com:8080 # Target to probe with http on port 8080 ``` `relabel\_configs` contains the new relabeling rules: ```yaml relabel\_configs: - source\_labels: [\_\_address\_\_] target\_label: \_\_param\_target - source\_labels: [... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.01881244219839573,
0.0669308453798294,
-0.0343388095498085,
-0.0051567815244197845,
0.010884505696594715,
-0.09261874109506607,
-0.0029996957164257765,
-0.06353715807199478,
0.014621051028370857,
-0.042153678834438324,
0.026375800371170044,
-0.07016868144273758,
0.0239899642765522,
-0.0... | 0.060856 |
targets and icmp module - prometheus.io - example.com labels: module: icmp relabel\_configs: - source\_labels: [\_\_address\_\_] target\_label: \_\_param\_target - source\_labels: [\_\_param\_target] target\_label: instance - source\_labels: [module] target\_label: \_\_param\_module - target\_label: \_\_address\_\_ rep... | https://github.com/prometheus/docs/blob/main/docs/guides/multi-target-exporter.md | main | prometheus | [
-0.012838070280849934,
0.011907266452908516,
-0.06364501267671585,
0.012139569967985153,
0.03678586706519127,
-0.04842992499470711,
0.004925374872982502,
-0.015533184632658958,
-0.01623905822634697,
-0.0688386783003807,
-0.004930274095386267,
-0.11207114905118942,
0.024853145703673363,
-0.... | 0.166962 |
Prometheus supports [Transport Layer Security](https://en.wikipedia.org/wiki/Transport\_Layer\_Security) (TLS) encryption for connections to Prometheus instances (i.e. to the expression browser or [HTTP API](/docs/prometheus/latest/querying/api/)). If you would like to enforce TLS for those connections, you would need ... | https://github.com/prometheus/docs/blob/main/docs/guides/tls-encryption.md | main | prometheus | [
-0.142243891954422,
0.053788162767887115,
-0.01871166191995144,
0.005222248379141092,
-0.02052859589457512,
-0.1608119010925293,
0.03808188438415527,
-0.07145524770021439,
0.016511695459485054,
-0.05264989659190178,
-0.0313398577272892,
-0.049022480845451355,
0.07147364318370819,
0.0063426... | 0.094603 |
[cAdvisor](https://github.com/google/cadvisor) (short for \*\*c\*\*ontainer \*\*Advisor\*\*) analyzes and exposes resource usage and performance data from running containers. cAdvisor exposes Prometheus metrics out of the box. In this guide, we will: \* create a local multi-container [Docker Compose](https://docs.docke... | https://github.com/prometheus/docs/blob/main/docs/guides/cadvisor.md | main | prometheus | [
-0.020971082150936127,
0.008398809470236301,
-0.061955392360687256,
0.026203235611319542,
0.009815460070967674,
-0.161782905459404,
-0.021081283688545227,
0.015784593299031258,
-0.036386266350746155,
-0.012311195954680443,
-0.07374022901058197,
-0.07508820295333862,
0.014293895103037357,
0... | 0.208266 |
in the Prometheus image) - `gid: "65534"` - The numeric group ID (65534 = `nobody` group) - `mode: 0400` - File permissions (read-only for owner) Omitting these fields or using string values like `"nobody"` will cause the following error: ``` strconv.Atoi: parsing "nobody": invalid syntax ``` ## Exploring the cAdvisor ... | https://github.com/prometheus/docs/blob/main/docs/guides/cadvisor.md | main | prometheus | [
-0.002525622956454754,
0.04948493465781212,
-0.0695938840508461,
-0.04656873270869255,
0.020707570016384125,
-0.1627519726753235,
-0.028521213680505753,
0.004230585880577564,
-0.025266915559768677,
0.02503209374845028,
0.02425380051136017,
-0.08388391137123108,
0.04328448697924614,
0.01668... | 0.126256 |
The Prometheus [\*\*Node Exporter\*\*](https://github.com/prometheus/node\_exporter) exposes a wide variety of hardware- and kernel-related metrics. In this guide, you will: \* Start up a Node Exporter on `localhost` \* Start up a Prometheus instance on `localhost` that's configured to scrape metrics from the running N... | https://github.com/prometheus/docs/blob/main/docs/guides/node-exporter.md | main | prometheus | [
-0.08081940561532974,
0.005555629264563322,
-0.03531133010983467,
0.0639275535941124,
0.05704851448535919,
-0.10061054676771164,
-0.031547293066978455,
0.03746503219008446,
-0.025267619639635086,
-0.015956968069076538,
-0.03804749995470047,
-0.06546510756015778,
-0.05333277955651283,
-0.02... | 0.227105 |
The average amount of CPU time spent in system mode, per second, over the last minute (in seconds) [`node\_filesystem\_avail\_bytes`](http://localhost:9090/graph?g0.range\_input=1h&g0.expr=node\_filesystem\_avail\_bytes&g0.tab=1) | The filesystem space available to non-root users (in bytes) [`rate(node\_network\_receiv... | https://github.com/prometheus/docs/blob/main/docs/guides/node-exporter.md | main | prometheus | [
0.005801190156489611,
0.007918301038444042,
-0.05815393477678299,
0.03462410718202591,
0.011886242777109146,
-0.11990422755479813,
0.0071641686372458935,
0.09837615489959717,
-0.024181313812732697,
0.06262316554784775,
0.004373103845864534,
-0.016472717747092247,
0.03474819287657738,
-0.03... | 0.120351 |
Prometheus can discover targets in a [Docker Swarm][swarm] cluster, as of v2.20.0. This guide demonstrates how to use that service discovery mechanism. ## Docker Swarm service discovery architecture The [Docker Swarm service discovery][swarmsd] contains 3 different roles: nodes, services, and tasks. The first role, \*\... | https://github.com/prometheus/docs/blob/main/docs/guides/dockerswarm.md | main | prometheus | [
-0.06184406206011772,
0.033220380544662476,
-0.05223458260297775,
-0.006382779683917761,
0.05127596855163574,
-0.10311463475227356,
0.05248868465423584,
-0.0707831010222435,
-0.02522885985672474,
0.04351017251610756,
-0.036252740770578384,
-0.03482801839709282,
0.04578341171145439,
-0.0002... | 0.237842 |
over the API. In our example, we only \*\*keep\*\* the targets that should be running. It prevents monitoring tasks that should be shut down. ```yaml - source\_labels: [\_\_meta\_dockerswarm\_service\_label\_prometheus\_job] regex: .+ action: keep ``` When we deployed our cadvisor, we have added a label `prometheus-job... | https://github.com/prometheus/docs/blob/main/docs/guides/dockerswarm.md | main | prometheus | [
-0.09304892271757126,
0.07592908293008804,
-0.03834342956542969,
0.012602045200765133,
0.07814156264066696,
-0.11763464659452438,
0.06392306834459305,
-0.06407785415649414,
0.013844666071236134,
-0.017145181074738503,
-0.012021278962492943,
-0.02562100812792778,
0.014055733568966389,
-0.00... | 0.188742 |
Prometheus has an official [Go client library](https://github.com/prometheus/client\_golang) that you can use to instrument Go applications. In this guide, we'll create a simple Go application that exposes Prometheus metrics via HTTP. NOTE: For comprehensive API documentation, see the [GoDoc](https://godoc.org/github.c... | https://github.com/prometheus/docs/blob/main/docs/guides/go-application.md | main | prometheus | [
-0.05013475939631462,
0.026726070791482925,
-0.05739057436585426,
-0.03421372175216675,
-0.10208519548177719,
-0.06873827427625656,
-0.007560097612440586,
0.05999113991856575,
-0.017483482137322426,
-0.05705958977341652,
-0.01040442381054163,
-0.022610343992710114,
-0.01839078776538372,
0.... | 0.186751 |
Prometheus offers a variety of [service discovery options](https://github.com/prometheus/prometheus/tree/main/discovery) for discovering scrape targets, including [Kubernetes](/docs/prometheus/latest/configuration/configuration/#kubernetes\_sd\_config), [Consul](/docs/prometheus/latest/configuration/configuration/#cons... | https://github.com/prometheus/docs/blob/main/docs/guides/file-sd.md | main | prometheus | [
-0.0577358677983284,
-0.004531577229499817,
0.005986978765577078,
-0.0254280436784029,
0.03256271407008171,
-0.07658813148736954,
-0.011801538988947868,
-0.023264972493052483,
0.029975702986121178,
0.031445108354091644,
-0.005086970515549183,
-0.053864460438489914,
-0.005342143587768078,
0... | 0.172341 |
will automatically be notified of the new list of targets. The [`up{job="node"}`](http://localhost:9090/graph?g0.range\_input=1h&g0.expr=up%7Bjob%3D%22node%22%7D&g0.tab=1) metric should display two instances with `instance` labels `localhost:9100` and `localhost:9200`. ## Summary In this guide, you installed and ran a ... | https://github.com/prometheus/docs/blob/main/docs/guides/file-sd.md | main | prometheus | [
-0.08161810785531998,
-0.029799576848745346,
-0.0329938605427742,
0.014128127135336399,
0.05069200322031975,
-0.0908849686384201,
-0.0038316072896122932,
-0.04225078597664833,
-0.048212215304374695,
-0.00731409527361393,
-0.0261687058955431,
-0.07361668348312378,
0.0233622919768095,
-0.007... | 0.130491 |
This guide covers the changes from OpenMetrics (OM) 1.0 to OpenMetrics 2.0 that affect client library (i.e. exposers) implementations. Sections are organized so you can implement changes incrementally, starting with version negotiation and working through metric types, syntax, and metadata. This guide may contain error... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.09169206768274307,
-0.0013816443970426917,
0.0005928765749558806,
-0.030386773869395256,
0.007343672215938568,
-0.07873179018497467,
-0.06594695150852203,
0.019704703241586685,
-0.04229690134525299,
0.0032484526745975018,
0.00909247063100338,
0.01286656130105257,
0.008906793780624866,
-... | 0.106354 |
multiple exemplars](#mandatory-timestamps) | Optional timestamp; max 1 | Mandatory timestamp; multiple allowed | Mixed | | [Size limit / W3C keys / histogram placement](#size-limit-relaxation) | 128-char limit; bucket-level | Soft limit; W3C keys; sample-level | Mixed | | [\*\*Unknown Type\*\*](#unknown-type) | | | | |... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.0426916740834713,
0.06295511871576309,
-0.01886066421866417,
-0.039279136806726456,
0.05766647681593895,
-0.06379787623882294,
-0.012582824565470219,
-0.008789549581706524,
0.019530275836586952,
-0.01880204863846302,
0.007815041579306126,
-0.08470316231250763,
0.029091833159327507,
-0.0... | 0.052471 |
name and sample Metric Name could differ. In OM 2.0, the MetricFamily name must exactly match every Metric's Name. There is no implicit suffix stripping. For counters, this means the TYPE line must include `\_total` if the samples use it. OM 1.0: ``` # TYPE http\_requests counter # HELP http\_requests Total HTTP reques... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.08115372061729431,
0.0021682416554540396,
-0.000017231464880751446,
0.016544917598366737,
0.0026518492959439754,
-0.09658576548099518,
0.015281738713383675,
0.05299720913171768,
0.03310544788837433,
-0.017993122339248657,
0.0070231021381914616,
-0.10675594210624695,
-0.040809039026498795,... | 0.07356 |
well with the relaxed `\_total` suffix rule described in [Naming Changes](#naming-changes) (see [Counter and Info Suffix Rules](#counter-suffix-rules)), since dropping `\_total` gives you cleaner dotted metric names. Be aware that not all Prometheus ecosystem tools support UTF-8 metric names yet. ### Metric Name Quotin... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.11441875994205475,
0.023302143439650536,
-0.005642905831336975,
0.03824209049344063,
-0.04458500072360039,
-0.10201553255319595,
0.07017665356397629,
0.04212970286607742,
0.059436310082674026,
0.00005594588947133161,
-0.01297159492969513,
-0.09994284063577652,
0.056087594479322433,
0.02... | 0.148896 |
EOF ``` See also: [Exemplars](#exemplars) See: [Counter](../specs/om/open\_metrics\_spec\_2\_0.md#counter) and [Histogram with Classic Buckets](../specs/om/open\_metrics\_spec\_2\_0.md#histogram-with-classic-buckets) in the OM 2.0 spec. ## CompositeValues \*\*Breaking\*\*: Traditional multiline complex types are no lon... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.010270657017827034,
0.029574966058135033,
0.007166974246501923,
-0.018359696492552757,
-0.026383670046925545,
-0.026443710550665855,
0.024349763989448547,
0.08517096936702728,
0.02233949676156044,
-0.018604371696710587,
-0.05297601595520973,
-0.06799644976854324,
0.008130808360874653,
-... | 0.137985 |
The quantile map moves inside the CompositeValue block. Count and sum are now mandatory fields. If there are no observations, use `quantile:[]` (empty quantile list). See: [Summary](../specs/om/open\_metrics\_spec\_2\_0.md#summary) in the OM 2.0 spec. ### Histogram OM 1.0: ``` # TYPE http\_request\_duration\_seconds hi... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
0.0060525089502334595,
0.07720369845628738,
-0.0009370658663101494,
-0.03253580257296562,
-0.02865213342010975,
-0.06893334537744522,
-0.0078062876127660275,
0.02857126109302044,
0.024931777268648148,
-0.018717389553785324,
-0.0025797737762331963,
-0.12436018884181976,
-0.04901973158121109,
... | 0.066827 |
defining the zero bucket boundary [-threshold, +threshold]. - `zero\_count` -- number of observations in the zero bucket. - `positive\_spans` -- list of `offset:length` pairs mapping bucket indices (see below). - `positive\_buckets` -- list of observation counts, one per bucket. Spans are `offset:length` pairs that des... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.018401557579636574,
0.032349102199077606,
0.04962841048836708,
-0.009824122302234173,
0.02063392847776413,
-0.07716711610555649,
0.02696755714714527,
0.006765907164663076,
0.057716332376003265,
-0.017113499343395233,
0.03250109404325485,
-0.11167635023593903,
0.032396603375673294,
-0.00... | 0.03085 |
{trace\_id="xyz789",span\_id="uvw012"} 1.0 1709999800 ``` ### W3C Trace Context Keys OM 2.0 recommends using `trace\_id` and `span\_id` as exemplar label keys, following W3C Trace Context conventions. The examples above already demonstrate this. Using consistent key names lets consumers correlate metrics with distribut... | https://github.com/prometheus/docs/blob/main/docs/guides/open_metrics_2_0_migration.md | main | prometheus | [
-0.06922054290771484,
0.02328140288591385,
-0.04702477157115936,
0.00982929952442646,
0.07247781753540039,
-0.08914957195520401,
0.029049787670373917,
0.04453789070248604,
-0.006976809818297625,
-0.07825917750597,
0.046231094747781754,
-0.054343197494745255,
-0.00888034701347351,
-0.086235... | 0.064917 |
Prometheus supports [OTLP](https://opentelemetry.io/docs/specs/otlp) (aka "OpenTelemetry Protocol") ingestion through [HTTP](https://opentelemetry.io/docs/specs/otlp/#otlphttp). ## Enable the OTLP receiver By default, the OTLP receiver is disabled, similarly to the Remote Write receiver. This is because Prometheus can ... | https://github.com/prometheus/docs/blob/main/docs/guides/opentelemetry.md | main | prometheus | [
-0.03467080742120743,
0.04403049498796463,
-0.01459406316280365,
0.002961972961202264,
-0.015833673998713493,
-0.15625205636024475,
0.001361602684482932,
-0.03451826050877571,
0.02071968838572502,
0.012716848403215408,
-0.0012884774478152394,
-0.03751690313220024,
0.013312879018485546,
0.0... | 0.154162 |
`service.name`, are translated to labels on the special `target\_info` metric. This means that, for OTel resource attributes you are not promoting, you can still include the corresponding labels in your queries, through joining with `target\_info`. To accomplish this, we recommend enabling the experimental PromQL funct... | https://github.com/prometheus/docs/blob/main/docs/guides/opentelemetry.md | main | prometheus | [
-0.049310293048620224,
0.017369400709867477,
-0.06904125958681107,
0.05754261463880539,
-0.04157838970422745,
-0.03212402015924454,
0.11701386421918869,
-0.01432948000729084,
0.04598933830857277,
-0.0533735491335392,
0.03719966486096382,
-0.10710156708955765,
0.09432531148195267,
-0.007976... | 0.165552 |
that when Prometheus announces through content negotiation that it allows UTF-8 characters, it does not require that metric names contain previously-unsupported characters. The OTLP metrics may be converted in several different ways, depending on the configuration of the endpoint. So while UTF-8 is enabled by default i... | https://github.com/prometheus/docs/blob/main/docs/guides/opentelemetry.md | main | prometheus | [
-0.056471191346645355,
0.0272746030241251,
0.0252701323479414,
-0.008806731551885605,
-0.06463264673948288,
-0.09400839358568192,
-0.0035355889704078436,
-0.03177548199892044,
0.04069142788648605,
-0.043270137161016464,
0.01365240290760994,
-0.08028236031532288,
0.016901273280382156,
0.050... | 0.144086 |
## Introduction Versions of Prometheus before 3.0 required that metric and label names adhere to a strict set of character requirements. With Prometheus 3.0, all UTF-8 strings are valid names, but there are some manual changes needed for other parts of the ecosystem to introduce names with any UTF-8 characters. There m... | https://github.com/prometheus/docs/blob/main/docs/guides/utf8.md | main | prometheus | [
-0.073841392993927,
0.03453437611460686,
0.002822472946718335,
-0.040401481091976166,
-0.07652866095304489,
-0.0454043410718441,
0.01260040421038866,
-0.025006763637065887,
0.025921287015080452,
-0.06484212726354599,
0.035998012870550156,
-0.07867191731929779,
-0.0038673896342515945,
0.083... | 0.109065 |
names in Prometheus 3.0. There is no way to enforce the legacy character set validation with Remote Write 2.0. ## OTLP Metrics OTLP receiver in Prometheus 3.0 still normalizes all names to Prometheus format by default. You can change this in `otlp` section of the Prometheus configuration as follows: otlp: # Ingest OTLP... | https://github.com/prometheus/docs/blob/main/docs/guides/utf8.md | main | prometheus | [
-0.06598126888275146,
-0.000251551071414724,
0.01954658515751362,
-0.005589703097939491,
-0.10618637502193451,
-0.08822345733642578,
-0.00501765962690115,
-0.035273559391498566,
0.02571876160800457,
-0.037521958351135254,
0.01642412133514881,
-0.0930158719420433,
0.05710720270872116,
0.035... | 0.1018 |
Prometheus fundamentally stores all data as [\_time series\_](http://en.wikipedia.org/wiki/Time\_series): streams of timestamped values belonging to the same metric and the same set of labeled dimensions. Besides stored time series, Prometheus may generate temporary derived time series as the result of queries. ## Metr... | https://github.com/prometheus/docs/blob/main/docs/concepts/data_model.md | main | prometheus | [
-0.14783228933811188,
0.02892029471695423,
-0.04134160652756691,
-0.004164521582424641,
-0.04043596237897873,
-0.10169757157564163,
0.03158271312713623,
0.009280902333557606,
0.06616973876953125,
-0.03629840537905693,
-0.02653643861413002,
-0.07577680796384811,
0.007141585927456617,
0.0157... | 0.165796 |
The Prometheus instrumentation libraries offer four core metric types. With the exception of native histograms, these are currently only differentiated in the API of instrumentation libraries and in the exposition protocols. The Prometheus server does not yet make use of the type information and flattens all types exce... | https://github.com/prometheus/docs/blob/main/docs/concepts/metric_types.md | main | prometheus | [
-0.06381679326295853,
-0.029441576451063156,
-0.022814052179455757,
-0.003232283052057028,
-0.04830053821206093,
-0.06904705613851547,
-0.005084186792373657,
0.024620553478598595,
-0.004817260429263115,
-0.040043722838163376,
-0.0789475291967392,
-0.08268851786851883,
-0.011618662625551224,
... | 0.198567 |
classic histograms suffer from possible partial transfer because their constituent time series are transferred independently). Their bucketing schema ensures that they are always aggregatable with each other, even if the resolution might have changed, while classic histograms with different bucket boundaries are not ge... | https://github.com/prometheus/docs/blob/main/docs/concepts/metric_types.md | main | prometheus | [
0.046723149716854095,
0.023585453629493713,
0.035437896847724915,
-0.10752494633197784,
-0.022844860330224037,
-0.010696387849748135,
-0.07532161474227905,
0.013359145261347294,
-0.04748373478651047,
-0.05950697138905525,
-0.05741968750953674,
-0.04139786958694458,
0.006670915521681309,
0.... | 0.110997 |
In Prometheus terms, an endpoint you can scrape is called an \_instance\_, usually corresponding to a single process. A collection of instances with the same purpose, a process replicated for scalability or reliability for example, is called a \_job\_. For example, an API server job with four replicated instances: \* j... | https://github.com/prometheus/docs/blob/main/docs/concepts/jobs_instances.md | main | prometheus | [
-0.14000941812992096,
0.0055521223694086075,
-0.032773714512586594,
0.01786160282790661,
0.04028195142745972,
-0.1357657015323639,
-0.0039033314678817987,
-0.09786858409643173,
0.06796043366193771,
-0.06125156953930855,
0.014675776474177837,
-0.05364323779940605,
0.021948957815766335,
-0.0... | 0.18494 |
Prometheus supports four types of metrics: \* Counter \* Gauge \* Histogram \* Summary ## Counter Counter is a metric value that can only increase or reset i.e. the value cannot reduce than the previous value. It can be used for metrics like the number of requests, no of errors, etc. Type the below query in the query b... | https://github.com/prometheus/docs/blob/main/docs/tutorials/understanding_metric_types.md | main | prometheus | [
-0.07035426795482635,
0.005530242808163166,
-0.08974676579236984,
0.0400068499147892,
-0.06914792209863663,
-0.07966098189353943,
0.03895050287246704,
0.015644192695617676,
0.06061866134405136,
-0.029743732884526253,
0.014254630543291569,
-0.044374775141477585,
0.032241225242614746,
0.0340... | 0.187999 |
They are calculated on the application level hence aggregation of metrics from multiple instances of the same process is not possible. They are used when the buckets of a metric are not known beforehand, but it is highly recommended to use histograms over summaries whenever possible. In this tutorial, we covered the ty... | https://github.com/prometheus/docs/blob/main/docs/tutorials/understanding_metric_types.md | main | prometheus | [
-0.003640528069809079,
-0.06638586521148682,
-0.04100087657570839,
-0.036395564675331116,
-0.09660198539495468,
-0.01764405146241188,
0.015483986586332321,
0.057086050510406494,
0.09465581923723221,
-0.025930792093276978,
0.0018842897843569517,
-0.08343430608510971,
0.0668100044131279,
0.0... | 0.113561 |
In this tutorial we will create alerts on the `ping\_request\_count` metric that we instrumented earlier in the [Instrumenting HTTP server written in Go](./instrumenting\_http\_server\_in\_go.md) tutorial. For the sake of this tutorial we will alert when the `ping\_request\_count` metric is greater than 5. Check out re... | https://github.com/prometheus/docs/blob/main/docs/tutorials/alerting_based_on_metrics.md | main | prometheus | [
0.03752811253070831,
-0.017004968598484993,
-0.039795514196157455,
0.023782067000865936,
0.02381589449942112,
-0.0996084213256836,
0.062146227806806564,
-0.018532361835241318,
0.06933990865945816,
-0.0010564482072368264,
-0.043189894407987595,
-0.029509151354432106,
0.020094316452741623,
0... | 0.187704 |
## What is Prometheus ? Prometheus is a system monitoring and alerting system. It was opensourced by SoundCloud in 2012 and is the second project both to join and to graduate within Cloud Native Computing Foundation after Kubernetes. Prometheus stores all metrics data as time series, i.e metrics information is stored a... | https://github.com/prometheus/docs/blob/main/docs/tutorials/getting_started.md | main | prometheus | [
-0.03907622769474983,
-0.007314687129110098,
-0.02019949071109295,
-0.011251652613282204,
-0.03458179906010628,
-0.06913444399833679,
0.013727017678320408,
-0.014116047881543636,
0.11001881957054138,
-0.009404095821082592,
-0.032321494072675705,
-0.05229882895946503,
-0.0017230430385097861,
... | 0.235362 |
an API which allows to query metrics which have been stored by scraping. This API is used to query the metrics, create dashboards/charts on it etc. PromQL is used to query these metrics. A simple Line chart created on the Request Count metric will look like this [](/asse... | https://github.com/prometheus/docs/blob/main/docs/tutorials/getting_started.md | main | prometheus | [
-0.07021408528089523,
0.0021923515014350414,
-0.07377122342586517,
0.004054427146911621,
-0.035681020468473434,
-0.11715331673622131,
-0.010628404095768929,
0.081532321870327,
0.026441223919391632,
-0.021947937086224556,
-0.0023527750745415688,
-0.0632842555642128,
0.05706442892551422,
0.0... | 0.208802 |
In this tutorial we will create a simple Go HTTP server and instrument it by adding a counter metric to keep count of the total number of requests processed by the server. Here we have a simple HTTP server with `/ping` endpoint which returns `pong` as response. ```go package main import ( "fmt" "net/http" ) func ping(w... | https://github.com/prometheus/docs/blob/main/docs/tutorials/instrumenting_http_server_in_go.md | main | prometheus | [
0.008870858699083328,
0.036772970110177994,
-0.0885418951511383,
-0.03281967714428902,
-0.08996371179819107,
-0.08380568027496338,
0.01714266650378704,
0.03264497220516205,
0.028797512874007225,
0.012663863599300385,
-0.020534126088023186,
-0.033119212836027145,
-0.05638263002038002,
-0.00... | 0.080557 |
In this tutorial we will create a simple dashboard using [Grafana](https://github.com/grafana/grafana) to visualize the `ping\_request\_count` metric that we instrumented in the [previous tutorial](./instrumenting\_http\_server\_in\_go.md). If you are wondering why one should use a tool like Grafana when one can query ... | https://github.com/prometheus/docs/blob/main/docs/tutorials/visualizing_metrics_using_grafana.md | main | prometheus | [
-0.02625415101647377,
-0.008242607116699219,
-0.0597614161670208,
0.017769889906048775,
-0.03100624494254589,
-0.13098269701004028,
-0.006712370552122593,
0.031654536724090576,
0.02501729689538479,
0.039458200335502625,
-0.01172863133251667,
-0.05700173228979111,
0.02921377308666706,
0.006... | 0.218011 |
\*\*The Zen of Prometheus\*\* is beginner friendly set of core values and guidelines for instrumenting your applications and writing idiomatic alerts using Prometheus. This is a document that's intended to maintained by the Prometheus community. Feel free to [contribute](https://github.com/prometheus/docs). ## Instrume... | https://github.com/prometheus/docs/blob/main/docs/practices/the_zen.md | main | prometheus | [
-0.08401978760957718,
0.009783712215721607,
-0.07664874196052551,
0.03785831108689308,
-0.000599486636929214,
-0.08228028565645218,
0.08116664737462997,
-0.0008429852314293385,
-0.020025579258799553,
-0.06968231499195099,
0.01747005060315132,
-0.0357351154088974,
0.04550766572356224,
-0.03... | 0.265004 |
sum, never sum then rate](https://www.robustperception.io/rate-then-sum-never-sum-then-rate). As a rule of thumb, the only mathematical operations you can safely directly apply to a counter's values are `rate`, `irate`, `increase`, and `resets`. Anything else will cause you problems. ## If you can log it, you can have ... | https://github.com/prometheus/docs/blob/main/docs/practices/the_zen.md | main | prometheus | [
0.0025595047045499086,
-0.021193621680140495,
0.00044022451038472354,
0.015410514548420906,
-0.040906623005867004,
-0.05687270313501358,
0.015838773921132088,
0.04913083091378212,
0.03965180739760399,
-0.01720644347369671,
-0.04514020308852196,
-0.08033405244350433,
0.026314355432987213,
0... | 0.119827 |
more information, check out [Setting Thresholds on Alerts](https://www.robustperception.io/setting-thresholds-on-alerts). ## Context is king Preserve common and useful labels for your alerts. They are most useful for routing and silencing. The inspiration behind the idea comes from [The Zen of Go](https://the-zen-of-go... | https://github.com/prometheus/docs/blob/main/docs/practices/the_zen.md | main | prometheus | [
-0.046514637768268585,
0.0393485426902771,
-0.022305196151137352,
0.03220673277974129,
0.04354409873485565,
-0.09100843966007233,
0.11926590651273727,
0.050346601754426956,
-0.0017148118931800127,
-0.08188468962907791,
-0.0050668600015342236,
0.02301900088787079,
0.07808031886816025,
0.023... | 0.189387 |
The Pushgateway is an intermediary service which allows you to push metrics from jobs which cannot be scraped. For details, see [Pushing metrics](/docs/instrumenting/pushing/). ## Should I be using the Pushgateway? \*\*We only recommend using the Pushgateway in certain limited cases.\*\* There are several pitfalls when... | https://github.com/prometheus/docs/blob/main/docs/practices/pushing.md | main | prometheus | [
-0.11320324242115021,
-0.05996596813201904,
-0.009883327409625053,
0.011884380131959915,
-0.010590124875307083,
-0.1441977471113205,
-0.035939138382673264,
-0.008277755230665207,
-0.0012185198720544577,
-0.02628740854561329,
-0.01808808371424675,
-0.003811771050095558,
0.006390739232301712,
... | 0.175603 |
Prometheus implements sane defaults for remote write, but many users have different requirements and would like to optimize their remote settings. This page describes the tuning parameters available via the [remote write configuration.](/docs/prometheus/latest/configuration/configuration/#remote\_write) ## Remote write... | https://github.com/prometheus/docs/blob/main/docs/practices/remote_write.md | main | prometheus | [
-0.006975420750677586,
0.010403850115835667,
-0.011252270080149174,
0.0618281289935112,
-0.015491331927478313,
-0.10567589849233627,
-0.008695119060575962,
-0.026967933401465416,
-0.004047861788421869,
0.059154219925403595,
-0.04208119586110115,
0.08091817051172256,
0.045443642884492874,
-... | 0.143267 |
data is backed up. ### `min\_shards` Min shards configures the minimum number of shards used by Prometheus, and is the number of shards used when remote write starts. If remote write falls behind, Prometheus will automatically scale up the number of shards so most users do not have to adjust this parameter. However, in... | https://github.com/prometheus/docs/blob/main/docs/practices/remote_write.md | main | prometheus | [
-0.03402216359972954,
-0.011869269423186779,
0.032534681260585785,
0.03776203468441963,
-0.026534153148531914,
-0.14816604554653168,
-0.04036012291908264,
0.014420496299862862,
0.014003424905240536,
0.030498895794153214,
-0.029122745618224144,
0.02136996015906334,
0.03804752230644226,
-0.0... | 0.167902 |
We recommend that you read [My Philosophy on Alerting](https://docs.google.com/a/boxever.com/document/d/199PqyG3UsyXlwieHaqbGiWVa8eMWi8zzAn0YfcApr8Q/edit) based on Rob Ewaschuk's observations at Google. To summarize: keep alerting simple, alert on symptoms, have good consoles to allow pinpointing causes, and avoid havi... | https://github.com/prometheus/docs/blob/main/docs/practices/alerting.md | main | prometheus | [
0.0059149921871721745,
-0.03988317400217056,
0.017409028485417366,
0.06342310458421707,
0.0563974529504776,
-0.04051392525434494,
0.16821910440921783,
0.03640373796224594,
0.07300058007240295,
-0.0761643648147583,
-0.006602404173463583,
-0.012246614322066307,
0.06650937348604202,
0.0760836... | 0.09267 |
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/practices/consoles.md | main | prometheus | [
-0.007063572760671377,
0.03720250353217125,
-0.03825486823916435,
-0.06113893911242485,
0.058655377477407455,
-0.09419544041156769,
-0.012342619709670544,
0.07879690080881119,
0.0037057306617498398,
0.001457297126762569,
-0.050465118139982224,
-0.038344595581293106,
0.01707177236676216,
0.... | 0.136422 |
Histograms and summaries are more complex metric types. For historical reasons, histograms exist in two variants: classic histograms and native histograms, the latter even come in a number of sub-variants. This document helps to understand the difference between all those metric types, how to use them correctly, and ho... | https://github.com/prometheus/docs/blob/main/docs/practices/histograms.md | main | prometheus | [
0.018774710595607758,
0.007555022835731506,
0.01923442631959915,
-0.0850391536951065,
-0.04230717569589615,
0.03592205047607422,
-0.03961998224258423,
0.06693979352712631,
0.029690980911254883,
-0.012501775287091732,
-0.03251982480287552,
-0.08019303530454636,
0.024826863780617714,
0.06511... | 0.147417 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.