content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
for the MetricFamily existed. ```openmetrics-add-eof # TYPE foo\_seconds counter # UNIT foo\_seconds seconds # HELP foo\_seconds Some text and \n some \" escaping ``` See the UTF-8 Quoting section for circumstances where the metric name MUST be enclosed in double quotes. There MUST NOT be more than one of each type of ... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.030818384140729904,
0.00899129081517458,
-0.03179025650024414,
0.0021146652288734913,
-0.059514228254556656,
0.055864572525024414,
0.022906554862856865,
0.03853166848421097,
0.08107013255357742,
-0.04682180657982826,
0.03701670095324516,
-0.12211400270462036,
0.04596922919154167,
0.0375... | 0.115156 |
present, the Start Timestamp MUST be added before it. Be aware that exposing metrics without `\_total` being a suffix of the MetricFamily name directly to end-users may reduce the usability due to confusion about what the metric's type is. An example with a Metric with no labels, and a MetricPoint with no timestamp and... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.03419598564505577,
-0.009023532271385193,
-0.028618915006518364,
-0.02270684763789177,
-0.013198229484260082,
0.025037214159965515,
0.0026063176337629557,
0.0395621620118618,
0.08904922753572464,
-0.009053030982613564,
0.05199912562966347,
-0.10226523131132126,
-0.01079041138291359,
0.0... | 0.068971 |
Timestamp MUST be added before it. Start Timestamp MUST be appended to all Quantile Values, to the MetricPoint's Sum and MetricPoint's Count. An example of a Metric with no labels and a MetricPoint with Sum, Count and Start Timestamp values: ```openmetrics-add-eof # TYPE foo summary foo\_count 17.0 st@1520430000.123 fo... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.021176112815737724,
0.02026320993900299,
0.02315508760511875,
-0.0356004424393177,
-0.04258497804403305,
0.01016277726739645,
0.029892226681113243,
0.030903026461601257,
0.07821477204561234,
-0.022783737629652023,
0.012553291395306587,
-0.13393214344978333,
-0.02112163044512272,
-0.0186... | 0.036945 |
unpopulated buckets). The 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 in... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0259237177670002,
0.0658784881234169,
-0.006383566651493311,
-0.02428573928773403,
0.023036567494273186,
-0.03103071264922619,
-0.0008311103447340429,
0.02287500537931919,
0.044637154787778854,
-0.009864121675491333,
0.019453920423984528,
-0.11584366858005524,
0.0766739547252655,
-0.048... | 0.05052 |
MUST be encoded in binary and MUST have `application/openmetrics-protobuf; version=1.0.0` as their content type. All payloads MUST be a single binary encoded MetricSet message, as defined by the OpenMetrics protobuf schema. ##### Version The protobuf format MUST follow the proto3 version of the protocol buffer language... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.029037123546004295,
-0.0011195566039532423,
-0.0163011122494936,
-0.1053817868232727,
-0.008565518073737621,
-0.07268780469894409,
-0.04149680212140083,
-0.006781305652111769,
-0.02338303253054619,
0.004412363283336163,
-0.0046932278200984,
-0.15624767541885376,
-0.007970776408910751,
0... | 0.050017 |
that a MetricFamily's unit is duplicated in the name so that the unit is available for systems that don't understand the unit metadata. The "le" label is a normal label value, rather than getting its own special syntax, so that ingestors don't have to add special histogram handling code to ingest them. As a further exa... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
0.0021132677793502808,
-0.021954700350761414,
-0.033313602209091187,
0.009003500454127789,
-0.020153816789388657,
-0.0060057989321649075,
-0.03145787492394447,
0.04359063506126404,
0.08996710181236267,
-0.07681203633546829,
0.05489273741841316,
-0.11090461909770966,
0.052181825041770935,
0... | 0.148853 |
The wire format defined by OpenMetrics is stateless across expositions. What information has been exposed before MUST have no impact on future expositions. Each exposition is a self-contained snapshot of the current state of the exposer. The same self-contained exposition MUST be provided to existing and new ingestors.... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.08581959456205368,
-0.03174678236246109,
-0.02022889256477356,
-0.007798205129802227,
0.04644666239619255,
0.057416707277297974,
-0.01765964739024639,
-0.003683866932988167,
0.11176442354917526,
-0.029893597587943077,
0.005994025617837906,
-0.02048824541270733,
-0.02473803423345089,
0.0... | 0.119726 |
For example frequent changes may cause performance issues for ingestors. A Help string that varies from exposition to exposition may cause each Help value to be stored. Frequently switching between int and float values could prevent efficient compression. ### NaN NaN is a number like any other in OpenMetrics, usually r... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.045255064964294434,
-0.048784494400024414,
-0.02237221784889698,
-0.016456427052617073,
0.07843489199876785,
-0.0374588668346405,
-0.034936923533678055,
0.02870253100991249,
0.0625036209821701,
0.019406694918870926,
0.06562580168247223,
0.007734722923487425,
-0.0037819447461515665,
0.01... | 0.172536 |
clash across its constituent libraries. Across a given deployment of a monitoring system as a whole the aim is that clashes where the same metric name means different things are uncommon. For example acme\_http\_router\_request\_seconds might end up in hundreds of different applications developed by A Company Manufactu... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.09856666624546051,
-0.08426894247531891,
-0.06943747401237488,
-0.05560065805912018,
-0.03700346127152443,
-0.06703770905733109,
0.033164940774440765,
-0.00011779362830566242,
0.09008970111608505,
-0.07291430979967117,
0.03528348356485367,
-0.03815668076276779,
0.03243272006511688,
0.00... | 0.09043 |
in the metric names contained in your instrumentation. For example a MetricFamily name should not contain the string "openmetrics" merely because it happens to be currently exposed via OpenMetrics somewhere, or "prometheus" merely because your current monitoring system is Prometheus. ### Label Namespacing For label nam... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.07157133519649506,
-0.011783238500356674,
-0.08584138751029968,
-0.018783951178193092,
-0.019706444814801216,
-0.09430072456598282,
0.04485089331865311,
0.012321972288191319,
0.03195453807711601,
-0.05504671111702919,
0.020986171439290047,
-0.08707311004400253,
0.02510691247880459,
0.03... | 0.217395 |
text exposition format and the ecosystem which formed around it. Backwards compatibility is a core design goal. Expanding or contracting the set of characters that are supported by the Prometheus text format would work against that goal. Breaking backwards compatibility would have wider implications than just the wire ... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
0.0030489808414131403,
0.005282691679894924,
-0.012001197785139084,
-0.02430872805416584,
0.05946919322013855,
-0.027649182826280594,
-0.020333299413323402,
0.012647215276956558,
0.027136191725730896,
-0.05694691836833954,
-0.0011154436506330967,
-0.020045746117830276,
0.02077483758330345,
... | 0.175053 |
rest of the exposition before applying business logic based on its content. Exposers MUST NOT add target metadata labels to all Metrics from an exposition, unless explicitly configured for a specific ingestor. Exposers MUST NOT prefix MetricFamily names or otherwise vary MetricFamily names based on target metadata. Gen... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.026125136762857437,
-0.08487824350595474,
-0.039539869874715805,
0.0009737041546031833,
-0.000036520093999570236,
0.007744161412119865,
0.03839291259646416,
-0.010046207346022129,
0.07040444016456604,
-0.08020682632923126,
0.028536859899759293,
-0.08571845293045044,
0.03675350174307823,
... | 0.114311 |
within around 20 hours. While losing 1KB of precision over the course of years for a 100Gbps network interface is unlikely to be a problem in practice, int64s are an option for integral data with such a high throughput. Summary quantiles must be float64, as they are estimates and thus fundamentally inaccurate. ### Expo... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0205233171582222,
0.05819981172680855,
0.015244473703205585,
0.006144888699054718,
0.05039144679903984,
-0.094589963555336,
-0.05376679077744484,
-0.004448857624083757,
0.017336757853627205,
-0.013544096611440182,
0.035264886915683746,
-0.009497862309217453,
-0.008124650456011295,
-0.01... | 0.041058 |
same exposition. Similarly it is possible that a "st@" for a MetricPoint could appear to be slightly after an exemplar or sample timestamp for that same MetricPoint. Keep in mind that there are monitoring systems in common use which support everything from nanosecond to second resolution, so having two MetricPoints tha... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.0434427335858345,
-0.0099343778565526,
-0.016225216910243034,
-0.027428653091192245,
0.04453838989138603,
0.008044315502047539,
0.029574427753686905,
0.04517696797847748,
0.13185378909111023,
-0.06220078840851784,
-0.027827361598610878,
-0.019115516915917397,
0.016859982162714005,
0.029... | 0.102819 |
of 2020, 10 million time series in total is considered a large amount and is commonly the order of magnitude of the upper bound of any single-instance ingestor. Any single exposition should not go above 10k time series without due diligence. One common consideration is horizontal scaling: What happens if you scale your... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.027145788073539734,
-0.0725102573633194,
-0.003859192132949829,
-0.02486993372440338,
-0.01143696904182434,
-0.02394770085811615,
-0.004721228498965502,
0.04683602973818779,
0.07211735844612122,
-0.026913341134786606,
-0.06269962340593338,
-0.029040323570370674,
0.011112140491604805,
0.... | 0.079596 |
to register two MIME types, `application/openmetrics-text` and `application/openmetrics-proto`. | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_2_0.md | main | prometheus | [
-0.047383781522512436,
-0.054900288581848145,
-0.0603276751935482,
-0.059876974672079086,
-0.011324204504489899,
-0.07244695723056793,
0.020229844376444817,
0.12812408804893494,
-0.0065379757434129715,
-0.04447131231427193,
0.06269260495901108,
-0.017411241307854652,
0.04009103775024414,
0... | 0.169833 |
- 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 |
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.1 - Status: Draft - Date: TBD - 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 exposition format... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.05961916968226433,
0.006247097160667181,
-0.00884675420820713,
-0.01723664253950119,
0.11754748970270157,
-0.054177358746528625,
-0.04164974391460419,
0.007378827780485153,
0.010809316299855709,
0.0330796018242836,
-0.01503997202962637,
-0.044680457562208176,
0.004545900970697403,
0.032... | 0.189088 |
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 MUST NOT be us... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.06016639620065689,
0.018883882090449333,
-0.09193136543035507,
-0.058912355452775955,
-0.052312325686216354,
-0.015078071504831314,
0.01902354136109352,
0.07077410072088242,
0.02196653187274933,
-0.10167244076728821,
0.0738600417971611,
-0.13423416018486023,
0.007978731766343117,
-0.034... | 0.227055 |
in the text format. Be aware that exposing metrics without the unit being a suffix of the MetricFamily name directly to end-users may reduce the usability due to confusion about what the metric's unit is. ##### Help Help is a string and SHOULD be non-empty. It is used to give a brief description of the MetricFamily for... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.05439973622560501,
-0.02534199319779873,
-0.055895622819662094,
0.012365302070975304,
-0.029369506984949112,
0.022361116483807564,
0.08222529292106628,
0.07044766843318939,
0.02045457437634468,
-0.057215843349695206,
0.028368765488266945,
-0.08585163205862045,
0.02101370319724083,
0.020... | 0.151133 |
Unit string. #### Info Info metrics are used to expose textual information which SHOULD NOT change during process lifetime. Common examples are an application's version, revision control commit, and the version of a compiler. A MetricPoint of an Info Metric contains a LabelSet. An Info MetricPoint's LabelSet MUST NOT h... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.009236393496394157,
-0.02610653080046177,
-0.067385233938694,
-0.06324175000190735,
-0.05518033728003502,
-0.016452299430966377,
0.06926886737346649,
0.04621626064181328,
0.07147146016359329,
-0.03114628605544567,
0.010637112893164158,
-0.06917085498571396,
0.05727797746658325,
-0.00875... | 0.256825 |
Exemplars SHOULD be put into the bucket with the highest value. A bucket MUST NOT have more than one exemplar. #### Summary Summaries also measure distributions of discrete events and MAY be used when Histograms are too expensive and/or an average event size is sufficient. They MAY also be used for backwards compatibil... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.04327964782714844,
-0.002332280855625868,
-0.004768273793160915,
-0.06590873748064041,
-0.05844195932149887,
-0.004724416416138411,
-0.008157334290444851,
0.038041356950998306,
0.12671314179897308,
0.004262737929821014,
0.02197784185409546,
-0.09935267269611359,
-0.03862081840634346,
0.... | 0.144196 |
help SP metricname SP escaped-string LF metric-descriptor =/ HASH SP unit SP metricname SP \*metricname-char LF metric = \*sample metric-type = counter / gauge / histogram / gaugehistogram / stateset metric-type =/ info / summary / unknown sample = metricname [labels] SP number [SP timestamp] [exemplar] LF exemplar = S... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.00783015601336956,
0.030823221430182457,
-0.05212849751114845,
-0.0682934895157814,
-0.03287214785814285,
0.06834576278924942,
0.08218614757061005,
0.05089893192052841,
-0.02526051737368107,
-0.08920901268720627,
0.06006721034646034,
-0.12128838151693344,
0.05054306611418724,
-0.0132202... | 0.035432 |
be used to encode nanosecond resolution timestamps. Arbitrary integer and floating point rendering of numbers MUST NOT be used for "quantile" and "le" label values as in section "Canonical Numbers". They MAY be used anywhere else numbers are used. ###### Considerations: Canonical Numbers Numbers in the "le" label value... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.04553860053420067,
0.036656610667705536,
-0.0843614712357521,
-0.07596807181835175,
-0.03470909222960472,
-0.012188156135380268,
0.040332820266485214,
0.050119612365961075,
0.08667443692684174,
-0.028216881677508354,
-0.009295299649238586,
-0.02330821007490158,
0.02148764207959175,
0.01... | 0.153555 |
exposed, the MetricFamily MUST be of type Unknown. If a unit is specified it MUST be provided in a UNIT metadata line. In addition, an underscore and the unit SHOULD 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\_se... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.09577789157629013,
-0.03433140739798546,
-0.05228801444172859,
0.030486954376101494,
-0.09310076385736465,
0.05000389739871025,
0.0038966815918684006,
0.04626286402344704,
0.03761224448680878,
-0.037819575518369675,
0.04098798334598541,
-0.11598369479179382,
0.043808579444885254,
0.0415... | 0.144736 |
Metric with no labels and two MetricPoints with timestamps: ```openmetrics-add-eof # TYPE foo gauge foo 17.0 123 foo 18.0 456 ``` ##### Counter The MetricPoint's Total Value Sample MetricName SHOULD have the suffix `\_total`. If present the MetricPoint's Created Value Sample MetricName MUST have the suffix `\_created`.... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.05481324717402458,
-0.040522221475839615,
-0.04260237142443657,
0.01741282269358635,
-0.030592478811740875,
-0.01780896633863449,
0.03380373492836952,
0.0012925759656354785,
0.132868692278862,
-0.04085777699947357,
0.07683785259723663,
-0.11581934988498688,
0.0317050963640213,
0.0532666... | 0.080011 |
foo summary foo\_count 17.0 foo\_sum 324789.3 foo\_created 1520430000.123 ``` An example of a Metric with no labels and a MetricPoint with two quantiles: ```openmetrics-add-eof # TYPE foo summary foo{quantile="0.95"} 123.7 foo{quantile="0.99"} 150.0 ``` Quantiles MAY be in any order. ##### Histogram The MetricPoint's B... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.0400574691593647,
-0.003635726636275649,
0.025999821722507477,
-0.06502227485179901,
-0.03748196363449097,
-0.005522506777197123,
0.06170978397130966,
0.036035701632499695,
0.10800206661224365,
-0.010376866906881332,
0.014778370968997478,
-0.10703135281801224,
0.028438225388526917,
-0.0... | 0.05615 |
MUST be in Unix epoch seconds as an int64 and a non-negative fraction of a second at nanosecond resolution as an int32 that counts forward from the seconds timestamp component. It MUST be within 0 to 999,999,999 inclusive. #### Protobuf schema Protobuf schema is currently available [here](https://github.com/prometheus/... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.02093154564499855,
0.04755048081278801,
-0.024869080632925034,
-0.02863098494708538,
0.025112001225352287,
-0.1127161905169487,
-0.08064711838960648,
0.019469797611236572,
0.028825359418988228,
0.014955710619688034,
0.019274914637207985,
-0.12366359680891037,
-0.004178108647465706,
0.02... | 0.161805 |
gauge metrics. ### Units and Base Units For consistency across systems and to avoid confusion, units are largely based on SI base units. Base units include seconds, bytes, joules, grams, meters, ratios, volts, amperes, and celsius. Units should be provided where they are applicable. For example, having all duration met... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.050864510238170624,
0.008372042328119278,
-0.05254049971699715,
0.01442481018602848,
-0.040068719536066055,
0.010691097006201744,
0.007852158509194851,
0.041264962404966354,
0.13008777797222137,
-0.046783577650785446,
0.01128186471760273,
-0.11785557121038437,
0.013343066908419132,
0.04... | 0.136087 |
how often ingestors are consuming expositions. ### Exposition Across Time and Metric Evolution Metrics are most useful when their evolution over time can be analysed, so accordingly expositions must make sense over time. Thus, it is not sufficient for one single exposition on its own to be useful and valid. Some change... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.06840915232896805,
-0.06466188281774521,
-0.021220773458480835,
0.0016315629472956061,
0.005261434707790613,
0.05855074152350426,
0.014795147813856602,
-0.011153900064527988,
0.11289060860872269,
-0.051124151796102524,
-0.006138014607131481,
-0.04797527939081192,
-0.025438513606786728,
... | 0.138286 |
and in particular MUST NOT be used as a marker for missing or otherwise bad data. ### Missing Data There are valid cases when data stops being present. For example a filesystem can be unmounted and thus its Gauge Metric for free disk space no longer exists. There is no special marker or signal for this situation. Subse... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.03952361270785332,
0.008738142438232899,
-0.01077977940440178,
-0.0012662315275520086,
0.019564533606171608,
0.00790215190500021,
-0.052834652364254,
0.001809348352253437,
0.08244936168193817,
-0.007464622147381306,
-0.008711174130439758,
-0.01354011707007885,
0.006678266450762749,
-0.0... | 0.134723 |
the better namespaced its metric names should be to reduce the risk of such scenarios arising. acme\_ is not a bad choice for internal use within a company, but these companies might for example choose the prefixes acmeverything\_ or acorpme\_ for code shared outside their company. After namespacing by company or organ... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.1380939930677414,
-0.13077078759670258,
-0.07235757261514664,
-0.015362648293375969,
-0.05258661508560181,
-0.09223154187202454,
0.0008439318626187742,
0.022122448310256004,
0.06766016036272049,
-0.06474859267473221,
-0.011052530258893967,
-0.06272411346435547,
0.025843920186161995,
0.0... | 0.161393 |
HTTP-related metrics "method" would be a better label name if you were distinguishing between GET, POST, and PUT requests. While there is metadata about metric names such as HELP, TYPE and UNIT there is no metadata for label names. This is as it would be bloating the format for little gain. Out-of-band documentation is... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.05758367106318474,
0.0046110437251627445,
-0.07515840977430344,
0.02430865168571472,
-0.0565476268529892,
-0.040528539568185806,
0.014734468422830105,
0.07864120602607727,
0.0710596814751625,
-0.019771702587604523,
0.0026295315474271774,
-0.09928617626428604,
0.05954064428806305,
-0.002... | 0.149752 |
deployment, or production or testing. This can be achieved by either the exposer or the ingestor adding labels to all Metrics that capture this metadata. Doing this through the ingestor is preferred as it is more flexible and carries less overhead. On flexibility, the hardware maintenance team might care about which se... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
0.008640582673251629,
-0.02524757571518421,
-0.05844073370099068,
-0.033953119069337845,
0.06658434867858887,
-0.08115945011377335,
-0.018603183329105377,
0.033593371510505676,
0.06615890562534332,
0.022801298648118973,
0.01441279798746109,
-0.014670351520180702,
0.05919479951262474,
-0.03... | 0.196309 |
many individual targets, and thus may expose multiple target info Metrics. The metrics may already have had target metadata added to them as labels as part of ingestion. The metric names MUST NOT be varied based on target metadata. For example it would be incorrect for all metrics to end up being prefixed with staging\... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.04460291564464569,
-0.015189907513558865,
-0.04991165176033974,
0.015010549686849117,
0.012266509234905243,
0.012987770140171051,
0.012142285704612732,
0.04708751663565636,
0.09638528525829315,
-0.00849887728691101,
-0.03486165031790733,
-0.09561175853013992,
0.06329146027565002,
0.0576... | 0.116503 |
a hard problem and data should be internally consistent in each system. As such, ingestors should be able to attach the current timestamp from their perspective to data rather than based on the system time of the exposer device. With timestamped metrics it is not generally possible to detect the time when a Metric went... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.056585296988487244,
-0.011062448844313622,
0.008754223585128784,
0.031211236491799355,
0.021983418613672256,
0.04974587261676788,
0.03751073405146599,
0.04528368264436722,
0.06216725707054138,
-0.0697140023112297,
0.048074107617139816,
-0.09601888805627823,
0.0437573567032814,
0.0380176... | 0.11741 |
deployment model, or over time. A certain amount of CPU usage may be acceptable in one setting and undesirable in another. Aggregation of values can further change acceptable values. In such a system, exposing bounds could be counter-productive. For example the maximum size of a queue may be exposed alongside the numbe... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.03352685645222664,
-0.030473314225673676,
-0.06256023794412613,
0.038117289543151855,
-0.009835979901254177,
-0.009860849007964134,
0.09762632846832275,
0.03083086758852005,
0.03707412630319595,
-0.002239218447357416,
-0.01763230375945568,
-0.021788721904158592,
0.08496803790330887,
-0.... | 0.220106 |
set of time series, then each additional targets' strings poses no incremental cost to most reasonably modern monitoring systems. If however each target has unique strings, there is such a cost. As an extreme example, a single 10k character metric name used by many targets is on its own very unlikely to be a problem in... | https://github.com/prometheus/docs/blob/main//docs/specs/om/open_metrics_spec_1_1.md | main | prometheus | [
-0.04912496730685234,
-0.009166914038360119,
-0.04275388643145561,
-0.00410922197625041,
0.0010015390580520034,
-0.04117578640580177,
0.04439260810613632,
0.01430037897080183,
0.0872533842921257,
-0.030667398124933243,
-0.011453991755843163,
0.0026024116668850183,
0.02308063954114914,
0.00... | 0.109949 |
- 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 systems 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.05490702763199806,
0.014795856550335884,
0.03679685294628143,
0.012803459540009499,
0.04469121992588043,
-0.13479134440422058,
0.006387431174516678,
-0.029778234660625458,
0.02376280538737774,
0.020304368808865547,
-0.03637233003973961,
-0.0403827466070652,
0.022220635786652565,
-0.0065... | 0.261104 |
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, Grafana Loki is designed for just that. See L... | https://github.com/prometheus/docs/blob/main//docs/introduction/faq.md | main | prometheus | [
-0.09883362054824829,
-0.026297636330127716,
-0.0329730361700058,
-0.014098123647272587,
-0.025091230869293213,
-0.12468792498111725,
-0.0016969074495136738,
0.032494232058525085,
0.014342566952109337,
0.024300184100866318,
-0.03523597493767738,
-0.03729286044836044,
-0.0003215202013961971,
... | 0.204361 |
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 precision issues after over 285 years... | https://github.com/prometheus/docs/blob/main//docs/introduction/faq.md | main | prometheus | [
0.011185874231159687,
-0.07957983762025833,
-0.09085790067911148,
-0.06676825135946274,
-0.08231686800718307,
0.023503361269831657,
-0.019619448110461235,
0.03139055520296097,
0.0015405256999656558,
0.014718159101903439,
-0.06614252924919128,
-0.036477550864219666,
0.007982345297932625,
-0... | 0.080128 |
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" view within the "Graph" 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 ex... | https://github.com/prometheus/docs/blob/main//docs/introduction/first_steps.md | main | prometheus | [
-0.049320220947265625,
-0.016143858432769775,
-0.060567792505025864,
0.03900573402643204,
-0.04713572934269905,
-0.0871112197637558,
-0.01685129851102829,
0.006061614491045475,
0.021192340180277824,
0.0064310720190405846,
-0.03266379237174988,
-0.0782318115234375,
0.015397364273667336,
0.0... | 0.105371 |
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 |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.