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 |
|---|---|---|---|---|---|
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.005801215302199125,
0.007918312214314938,
-0.058153945952653885,
0.0346241295337677,
0.011886216700077057,
-0.11990423500537872,
0.00716417608782649,
0.09837611764669418,
-0.024181297048926353,
0.06262314319610596,
0.004373049363493919,
-0.0164727121591568,
0.03474816679954529,
-0.036027... | 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 out 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.0905914381146431,
0.07675222307443619,
-0.037707023322582245,
0.011532112024724483,
0.07364816963672638,
-0.12023293972015381,
0.06117301061749458,
-0.06385260820388794,
0.008603189140558243,
-0.015391628257930279,
-0.015129666775465012,
-0.029144199565052986,
0.01599307730793953,
-0.00... | 0.182662 |
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 |
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 |
in your queries, through joining with `target\_info`. To accomplish this, we recommend enabling the experimental PromQL function `info` for easy joining via the following flag: ```shell --enable-feature=promql-experimental-functions ``` An example of such a query can look like the following: ```promql info(rate(http\_s... | https://github.com/prometheus/docs/blob/main//docs/guides/opentelemetry.md | main | prometheus | [
-0.015856636688113213,
0.03829459846019745,
-0.07153042405843735,
0.09912464022636414,
-0.05519511178135872,
-0.05156926065683365,
0.014782324433326721,
-0.024090591818094254,
0.05187214910984039,
-0.004918649327009916,
0.037020243704319,
-0.13348087668418884,
0.026877058669924736,
-0.0311... | 0.143631 |
in several different ways, depending on the configuration of the endpoint. So while UTF-8 is enabled by default in Prometheus storage and UI, you need to set the `translation\_strategy` for OTLP metrics receiver, which by default is set to old normalization `UnderscoreEscapingWithSuffixes`. There are four possible tran... | https://github.com/prometheus/docs/blob/main//docs/guides/opentelemetry.md | main | prometheus | [
-0.04778510704636574,
0.026780569925904274,
0.022760555148124695,
-0.020636117085814476,
-0.061888761818408966,
-0.08893255144357681,
0.005428904201835394,
-0.024177026003599167,
0.04150073230266571,
-0.05732535198330879,
0.03564628213644028,
-0.07803349196910858,
0.007120814640074968,
0.0... | 0.149249 |
## 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 client libraries offer four core metric types. These are currently only differentiated in the client libraries (to enable APIs tailored to the usage of the specific types) and in the wire protocol. The Prometheus server does not yet make use of the type information and flattens all data into untyped time... | https://github.com/prometheus/docs/blob/main//docs/concepts/metric_types.md | main | prometheus | [
-0.11982858180999756,
-0.024216748774051666,
-0.030918674543499947,
0.036509737372398376,
-0.08741186559200287,
-0.0735243707895279,
0.00437829690054059,
0.03934084251523018,
0.07810349017381668,
-0.008722692728042603,
-0.06823515146970749,
-0.01468629390001297,
-0.0016750048380345106,
0.0... | 0.240994 |
See [histograms and summaries](/docs/practices/histograms) for detailed explanations of φ-quantiles, summary usage, and differences to [histograms](#histogram). NOTE: Beginning with Prometheus v3.0, the values of the `quantile` label are normalized during ingestion to follow the format of [OpenMetrics Canonical Numbers... | https://github.com/prometheus/docs/blob/main//docs/concepts/metric_types.md | main | prometheus | [
-0.07348328828811646,
0.019621895626187325,
0.003037183778360486,
-0.057931676506996155,
-0.06521213054656982,
-0.053628772497177124,
-0.006227564532309771,
0.07671601325273514,
0.030502917245030403,
-0.03730061277747154,
0.04013947769999504,
-0.018652604892849922,
-0.0026230677030980587,
... | 0.200166 |
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 instrumentation 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 p... | https://github.com/prometheus/docs/blob/main//docs/tutorials/instrumenting_http_server_in_go.md | main | prometheus | [
0.002206863835453987,
0.033909957855939865,
-0.08342047780752182,
-0.02652384713292122,
-0.07803872227668762,
-0.08325179666280746,
0.011590751819312572,
0.03126553073525429,
0.017115652561187744,
0.0023271767422556877,
-0.024742761626839638,
-0.02697891555726528,
-0.05107283964753151,
0.0... | 0.080382 |
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 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 |
NOTE: This document predates native histograms (added as an experimental feature in Prometheus v2.40 and becoming stable in v3.8). The intention is to thoroughly update this document in the foreseeable future. Histograms and summaries are more complex metric types. Not only does a single histogram or summary create a m... | https://github.com/prometheus/docs/blob/main//docs/practices/histograms.md | main | prometheus | [
-0.0388038344681263,
0.006587460171431303,
0.017741067335009575,
-0.03748418018221855,
-0.04063202440738678,
-0.02060331031680107,
-0.02427229844033718,
0.028106944635510445,
0.029453227296471596,
-0.02248437888920307,
-0.04349777474999428,
-0.06493143737316132,
0.0031570345163345337,
0.03... | 0.163519 |
The calculation does not exactly match the traditional Apdex score, as it includes errors in the satisfied and tolerable parts of the calculation. ## Quantiles You can use both summaries and histograms to calculate so-called φ-quantiles, where 0 ≤ φ ≤ 1. The φ-quantile is the observation value that ranks at number φ\*N... | https://github.com/prometheus/docs/blob/main//docs/practices/histograms.md | main | prometheus | [
-0.003125161863863468,
-0.0006324162823148072,
0.021519651636481285,
-0.06031498685479164,
-0.09216372668743134,
-0.007240990176796913,
0.05164829269051552,
0.057241540402173996,
0.05992782115936279,
0.05230364203453064,
-0.01329750008881092,
-0.0008371639414690435,
0.09726287424564362,
0.... | 0.063452 |
of that estimation. Continuing the histogram example from above, imagine your usual request durations are almost all very close to 220ms, or in other words, if you could plot the "true" histogram, you would see a very sharp spike at 220ms. In the Prometheus histogram metric as configured above, almost all observations,... | https://github.com/prometheus/docs/blob/main//docs/practices/histograms.md | main | prometheus | [
-0.04529622942209244,
0.016474341973662376,
0.022627413272857666,
-0.006387361790984869,
-0.017974399030208588,
-0.14133521914482117,
-0.0233145859092474,
0.038786232471466064,
0.032614145427942276,
0.0021562627516686916,
-0.03647179156541824,
-0.028483839705586433,
0.02055996283888817,
-0... | 0.112248 |
all the difference between clearly within the SLO vs. clearly outside the SLO. The bottom line is: If you use a summary, you control the error in the dimension of φ. If you use a histogram, you control the error in the dimension of the observed value (via choosing the appropriate bucket layout). With a broad distributi... | https://github.com/prometheus/docs/blob/main//docs/practices/histograms.md | main | prometheus | [
-0.03243512287735939,
-0.004495371598750353,
0.03418203443288803,
-0.017397549003362656,
-0.02960839308798313,
-0.0017836698098108172,
0.026723714545369148,
0.09268207103013992,
0.0542488656938076,
-0.020570293068885803,
0.0074697453528642654,
-0.013736672699451447,
0.05268038436770439,
0.... | 0.062254 |
This page provides an opinionated set of guidelines for instrumenting your code. ## How to instrument The short answer is to instrument everything. Every library, subsystem and service should have at least a few metrics to give you a rough idea of how it is performing. Instrumentation should be an integral part of your... | https://github.com/prometheus/docs/blob/main//docs/practices/instrumentation.md | main | prometheus | [
-0.05810242146253586,
-0.03883606940507889,
-0.0821116641163826,
-0.007504737004637718,
-0.04096081852912903,
-0.07251296192407608,
0.05029921233654022,
0.05514949560165405,
-0.0038494900800287724,
0.012117601931095123,
-0.09764636307954788,
0.011236324906349182,
0.02809976600110531,
-0.04... | 0.160538 |
batch jobs that take more than a few minutes to run, it is useful to also scrape them using pull-based monitoring. This lets you track the same metrics over time as for other types of jobs, such as resource usage and latency when talking to other systems. This can aid debugging if the job starts to get slow. For batch ... | https://github.com/prometheus/docs/blob/main//docs/practices/instrumentation.md | main | prometheus | [
-0.07560916990041733,
-0.04326498880982399,
-0.06888870894908905,
-0.005298887845128775,
0.05065843462944031,
-0.02305210381746292,
0.05090181529521942,
0.023522814735770226,
0.006191854830831289,
-0.05535828322172165,
-0.09500358253717422,
0.02176378108561039,
-0.05380474030971527,
-0.005... | 0.183004 |
being batch job durations. This is because both represent information about that particular push/scrape, rather than tracking multiple durations over time. ## Things to watch out for There are some general things to be aware of when doing monitoring, and also Prometheus-specific ones in particular. ### Use labels Few m... | https://github.com/prometheus/docs/blob/main//docs/practices/instrumentation.md | main | prometheus | [
-0.1084587424993515,
-0.018917134031653404,
-0.059943534433841705,
0.04035313427448273,
-0.01018618606030941,
-0.12503628432750702,
-0.008138417266309261,
-0.009389077313244343,
0.05186905339360237,
-0.016719061881303787,
-0.03457745164632797,
-0.10994603484869003,
0.025659983977675438,
0.... | 0.193375 |
useful for snapshots of state, such as in-progress requests, free/total memory, or temperature. You should never take a `rate()` of a gauge. Summaries and histograms are more complex metric types discussed in [their own section](/docs/practices/histograms/). ### Timestamps, not time since If you want to track the amoun... | https://github.com/prometheus/docs/blob/main//docs/practices/instrumentation.md | main | prometheus | [
-0.08060932904481888,
0.05068068206310272,
-0.06878022104501724,
-0.004102279432117939,
-0.024634703993797302,
-0.042047400027513504,
0.0063273306004703045,
0.04097447171807289,
0.06221088767051697,
0.009304466657340527,
-0.026258444413542747,
-0.04190460219979286,
-0.033061433583498,
-0.0... | 0.221842 |
A consistent naming scheme for [recording rules](/docs/prometheus/latest/configuration/recording\_rules/) makes it easier to interpret the meaning of a rule at a glance. It also avoids mistakes by making incorrect or meaningless calculations stand out. This page documents proper naming conventions and aggregation for r... | https://github.com/prometheus/docs/blob/main//docs/practices/rules.md | main | prometheus | [
-0.10833407193422318,
0.003270357847213745,
-0.059481482952833176,
-0.010398929007351398,
-0.06277137994766235,
-0.08238214254379272,
0.01930384151637554,
0.03621946647763252,
0.043039388954639435,
0.005834827199578285,
0.03402178734540939,
-0.04167431220412254,
0.01964709348976612,
0.0121... | 0.230337 |
names. When there is no aggregation, the levels always match. If this is not the case a mistake has likely been made in the rules. | https://github.com/prometheus/docs/blob/main//docs/practices/rules.md | main | prometheus | [
-0.06585077196359634,
-0.021221406757831573,
0.01732475310564041,
0.016835952177643776,
-0.01274912804365158,
-0.007537319324910641,
-0.07160042971372604,
-0.035075489431619644,
0.06561124324798584,
-0.07749775797128677,
0.036353591829538345,
-0.08857043832540512,
0.05377952381968498,
0.01... | 0.015174 |
The metric and label conventions presented in this document are not required for using Prometheus, but can serve as both a style-guide and a collection of best practices. Individual organizations may want to approach some of these practices, e.g. naming conventions, differently. ## Metric names A metric name... \* ...M... | https://github.com/prometheus/docs/blob/main//docs/practices/naming.md | main | prometheus | [
-0.08810777962207794,
-0.026478691026568413,
-0.05418635159730911,
-0.03347761929035187,
-0.08209337294101715,
-0.09861331433057785,
0.021993152797222137,
0.01951814442873001,
0.060722071677446365,
-0.05418270826339722,
-0.00259384629316628,
-0.09201232343912125,
0.04947726055979729,
0.034... | 0.214981 |
etc.). Prometheus strongly recommends including unit and type in a metric name, even if you store that information elsewhere, because of the following practical reasons: \* \*\*Metric consumption reliability and UX\*\*: When interacting with a modern UI to use such a metric in PromQL, it's possible to display rich info... | https://github.com/prometheus/docs/blob/main//docs/practices/naming.md | main | prometheus | [
-0.0837639793753624,
-0.01994572952389717,
-0.061163280159235,
0.03556559234857559,
-0.05071864649653435,
-0.07562148571014404,
0.05558919161558151,
0.012111138552427292,
0.08125723898410797,
-0.04400710389018059,
-0.013534323312342167,
-0.08212225139141083,
0.03446168079972267,
0.04180802... | 0.16168 |
In addition to [client libraries](/docs/instrumenting/clientlibs/) and [exporters and related libraries](/docs/instrumenting/exporters/), there are numerous other generic integration points in Prometheus. This page lists some of the integrations with these. Not all integrations are listed here, due to overlapping funct... | https://github.com/prometheus/docs/blob/main//docs/operating/integrations.md | main | prometheus | [
-0.12926450371742249,
-0.008755042217671871,
-0.018874481320381165,
-0.0371791236102581,
0.007534502074122429,
-0.10935021191835403,
-0.02757241390645504,
-0.0003206812252756208,
-0.014256316237151623,
0.006309200543910265,
0.003232128219678998,
0.00555304205045104,
-0.008959013968706131,
... | 0.255328 |
NOTE: Before we dive into the technical details below, we would like to emphasize that Prometheus, as a monitoring system, collects and serves information about the systems it is monitoring. Therefore, the HTTP endpoints provided by Prometheus components should not be exposed to publicly accessible networks like the in... | https://github.com/prometheus/docs/blob/main//docs/operating/security.md | main | prometheus | [
-0.06587506085634232,
0.05335148051381111,
-0.02097502537071705,
-0.027328507974743843,
0.002041097264736891,
-0.10420674830675125,
0.0007124757976271212,
0.014459004625678062,
-0.006020498927682638,
-0.0015585018554702401,
-0.013369197025895119,
-0.0013795677805319428,
0.012362179346382618,... | 0.195025 |
HTTP endpoint and logs. They have access to all time series information contained in the database, plus a variety of operational/debugging information. It is also presumed that only trusted users have the ability to change the command line, configuration file, rule files and other aspects of the runtime environment of ... | https://github.com/prometheus/docs/blob/main//docs/operating/security.md | main | prometheus | [
-0.09915172308683395,
0.029987191781401634,
-0.05403592064976692,
0.014905615709722042,
0.043343059718608856,
-0.13768179714679718,
0.01328761875629425,
-0.046433307230472565,
0.02201336994767189,
-0.00147820555139333,
0.008574265986680984,
-0.007310973014682531,
0.014516563154757023,
0.00... | 0.156052 |
all the existing metric groups. This is disabled by default. If enabled, administrative functionality will be accessible under the `/api/\*/admin/` paths. ## Exporters Exporters generally only talk to one configured instance with a preset set of commands/requests, which cannot be expanded via their HTTP endpoint. There... | https://github.com/prometheus/docs/blob/main//docs/operating/security.md | main | prometheus | [
-0.13671773672103882,
0.025667719542980194,
-0.08266819268465042,
-0.004947133827954531,
0.005639124661684036,
-0.05690912902355194,
-0.0021987969521433115,
-0.04427679628133774,
0.02948693558573723,
-0.014029432088136673,
-0.006595502607524395,
-0.053503695875406265,
0.02493172138929367,
... | 0.072411 |
`up{job=""}` would become `up{job=""} or some\_metric{zzz=""}` if the `` was `"} or some\_metric{zzz="`. For those using Grafana note that [dashboard permissions are not data source permissions](https://grafana.com/docs/grafana/latest/permissions/#data-source-permissions), so do not limit a user's ability to run arbitr... | https://github.com/prometheus/docs/blob/main//docs/operating/security.md | main | prometheus | [
-0.17660632729530334,
0.07153895497322083,
-0.08978372067213058,
-0.013814489357173443,
-0.04771992936730385,
-0.12989015877246857,
0.013097974471747875,
-0.05755448341369629,
-0.010625625029206276,
0.013920546509325504,
-0.009979113936424255,
-0.01373912114650011,
0.05944603309035301,
0.0... | 0.129938 |
# Deep Links Deep links allow users to quickly redirect to third-party systems, such as Splunk, Datadog, etc. from the Argo CD user interface. Argo CD administrator will be able to configure links to third-party systems by providing deep link templates configured in `argocd-cm`. The templates can be conditionally rende... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/deep_links.md | master | argo-cd | [
-0.0644453689455986,
-0.05487976223230362,
-0.010494858957827091,
0.01508379727602005,
0.007176340091973543,
-0.027446210384368896,
-0.016155757009983063,
0.01792391762137413,
-0.02610427886247635,
0.07153359055519104,
-0.033556465059518814,
0.025250360369682312,
-0.03584355115890503,
-0.0... | 0.213524 |
github.com/expr-lang/expr is used for evaluation of conditions - url: https://mycompany.splunk.com?search={{.app.spec.destination.namespace}} title: Splunk if: application.spec.project == "default" - url: https://{{.app.metadata.annotations.splunkhost}}?search={{.app.spec.destination.namespace}} title: Splunk if: app.m... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/deep_links.md | master | argo-cd | [
-0.03204105794429779,
0.08218932896852493,
0.013816493563354015,
0.03919801488518715,
0.11673428118228912,
-0.05234293267130852,
0.05318768694996834,
-0.0017954002832993865,
0.052740562707185745,
0.03217901661992073,
0.01624155603349209,
-0.06166282668709755,
0.013585529290139675,
0.072995... | 0.097944 |
- [apps/DaemonSet/restart](https://github.com/argoproj/argo-cd/blob/master/resource\_customizations/apps/DaemonSet/actions/restart/action.lua) - [apps/Deployment/pause](https://github.com/argoproj/argo-cd/blob/master/resource\_customizations/apps/Deployment/actions/pause/action.lua) - [apps/Deployment/restart](https://... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/resource_actions_builtin.md | master | argo-cd | [
-0.06524304300546646,
-0.06628420948982239,
-0.05959296599030495,
0.022877182811498642,
-0.030929215252399445,
-0.00786945503205061,
0.03865282982587814,
0.037157509475946426,
-0.057059455662965775,
0.042130693793296814,
0.07036729156970978,
0.03489137068390846,
-0.08063314110040665,
-0.02... | 0.157794 |
# Architectural Overview  ## Components ### API Server The API server is a gRPC/REST server which exposes the API consumed by the Web UI, CLI, and CI/CD systems. It has the following responsibilities: \* application management and status reporting \* invoking o... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/architecture.md | master | argo-cd | [
-0.0585024431347847,
0.016590533778071404,
-0.0797123834490776,
-0.017354046925902367,
-0.039338018745183945,
-0.07018882781267166,
0.07129060477018356,
-0.026033226400613785,
0.10707369446754456,
0.08633776009082794,
0.011146791279315948,
-0.02092180773615837,
-0.031703781336545944,
-0.06... | 0.291636 |
# Verification of Argo CD Artifacts ## Prerequisites - cosign `v2.0.0` or higher [installation instructions](https://docs.sigstore.dev/cosign/installation) - slsa-verifier [installation instructions](https://github.com/slsa-framework/slsa-verifier#installation) - crane [installation instructions](https://github.com/goo... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/signed-release-assets.md | master | argo-cd | [
-0.06889514625072479,
0.05110940337181091,
-0.07827474921941757,
-0.08648765832185745,
0.01796175166964531,
-0.08759522438049316,
-0.0014689257368445396,
-0.04146130010485649,
-0.0938638374209404,
0.013655939139425755,
0.11966057121753693,
-0.04699878767132759,
-0.03945942968130112,
-0.043... | 0.098509 |
full tag), use the `--source-versioned-tag` which performs semantic versioning verification: ```shell slsa-verifier verify-artifact argocd-linux-amd64 \ --provenance-path argocd-cli.intoto.jsonl \ --source-uri github.com/argoproj/argo-cd \ --source-versioned-tag v2 # Note: May use v2.7 for minor version verification. `... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/signed-release-assets.md | master | argo-cd | [
-0.04981352761387825,
-0.0019182437099516392,
-0.10641827434301376,
-0.03211977332830429,
0.10945044457912445,
-0.08957281708717346,
-0.00563135975971818,
-0.02610677294433117,
-0.016802137717604637,
0.05682177469134331,
0.04547882452607155,
-0.03741338849067688,
-0.031561240553855896,
0.0... | 0.049835 |
# Cluster Management This guide is for operators looking to manage clusters on the CLI. If you want to use Kubernetes resources for this, check out [Declarative Setup](./declarative-setup.md#clusters). Not all commands are described here, see the [argocd cluster Command Reference](../user-guide/commands/argocd\_cluster... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/cluster-management.md | master | argo-cd | [
0.045324672013521194,
-0.03872201219201088,
-0.09110189974308014,
-0.013335955329239368,
-0.0118184145539999,
0.027268365025520325,
0.054943881928920746,
-0.07981230318546295,
0.06366202235221863,
0.04607628658413887,
-0.007703879382461309,
-0.0663089007139206,
-0.028691045939922333,
-0.03... | 0.167175 |
# TLS configuration Argo CD provides three inbound TLS endpoints that can be configured: \* The user-facing endpoint of the `argocd-server` workload, which serves the UI and the API \* The endpoint of the `argocd-repo-server`, which is accessed by `argocd-server` and `argocd-application-controller` workloads to request... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/tls.md | master | argo-cd | [
-0.0919865220785141,
0.009719999507069588,
-0.10528473556041718,
-0.004178436938673258,
-0.08876169472932816,
-0.08812163770198822,
0.05981855094432831,
0.0003997264429926872,
0.05128249526023865,
0.01454800646752119,
-0.00776482280343771,
0.03715473413467407,
-0.010649643838405609,
-0.000... | 0.094497 |
contains only information for TLS configuration to be used by `argocd-server` and is safe to be managed via third-party tools such as `cert-manager` or `SealedSecrets` To create this secret manually from an existing key pair, you can use `kubectl`: ```shell kubectl create -n argocd secret tls argocd-server-tls \ --cert... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/tls.md | master | argo-cd | [
-0.03541472926735878,
0.010514582507312298,
-0.08042287081480026,
-0.027092715725302696,
-0.08770595490932465,
-0.041981130838394165,
0.03334865719079971,
-0.04254409298300743,
0.08647093921899796,
0.05814306065440178,
0.00973318051546812,
0.009751955047249794,
-0.02321024425327778,
-0.027... | 0.057953 |
to use for its gRPC endpoint on startup. Because the `argocd-repo-server` has no means to connect to the K8s control plane API, this certificate is not available to outside consumers for verification. These components will use a non-validating connection to the `argocd-repo-server` for this reason. To change this behav... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/tls.md | master | argo-cd | [
-0.026236020028591156,
-0.00008016487845452502,
-0.12580683827400208,
-0.04707915708422661,
-0.05091476812958717,
-0.05285891517996788,
0.05629172548651695,
-0.007760519161820412,
0.05565875023603439,
0.07915721088647842,
0.01899776980280876,
0.0006134598515927792,
-0.02344745770096779,
0.... | 0.041314 |
handle all aspects of TLS to `argocd-repo-server`'s TLS sidecar proxy. ### Disabling TLS to argocd-dex-server In some scenarios where mTLS through sidecar proxies is involved (e.g. in a service mesh), you may want to configure the connections between `argocd-server` to `argocd-dex-server` to not use TLS at all. In this... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/tls.md | master | argo-cd | [
-0.03386267274618149,
0.0434284470975399,
-0.024811385199427605,
-0.01859356090426445,
-0.08759038895368576,
-0.09448359906673431,
0.025227459147572517,
-0.05501701310276985,
-0.0007744061294943094,
0.04401515796780586,
0.0001622432318981737,
0.02572767436504364,
-0.005339893512427807,
-0.... | -0.032064 |
# Custom Tooling Argo CD bundles preferred versions of its supported templating tools (helm, kustomize, ks, jsonnet) as part of its container images. Sometimes, it may be desired to use a specific version of a tool other than what Argo CD bundles. Some reasons to do this might be: \* To upgrade/downgrade to a specific ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/custom_tools.md | master | argo-cd | [
-0.042080916464328766,
0.04413945600390434,
0.0030757123604416847,
-0.03800203278660774,
-0.008475502952933311,
-0.0309456754475832,
0.02014816179871559,
-0.01455781888216734,
0.03604874759912491,
0.08091671019792557,
0.03536318987607956,
-0.040257833898067474,
-0.03917841985821724,
-0.030... | 0.116261 |
# Troubleshooting Tools The document describes how to use `argocd admin` subcommands to simplify Argo CD settings customizations and troubleshot connectivity issues. ## Settings Argo CD provides multiple ways to customize system behavior and has a lot of settings. It might be dangerous to modify settings on Argo CD use... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/troubleshooting.md | master | argo-cd | [
-0.006169790402054787,
0.017693866044282913,
-0.07389405369758606,
0.008932968601584435,
-0.04366099089384079,
-0.1320198029279709,
0.071260966360569,
-0.02570996806025505,
-0.1219044104218483,
0.06282982230186462,
0.03483681380748749,
0.020623575896024704,
-0.015451311133801937,
-0.038962... | 0.072626 |
# Disaster Recovery You can use `argocd admin` to import and export all Argo CD data. Make sure you have `~/.kube/config` pointing to your Argo CD cluster. Figure out what version of Argo CD you're running: ```bash argocd version | grep server # ... export VERSION=v1.0.1 ``` Export to a backup: ```bash docker run -v ~/... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/disaster_recovery.md | master | argo-cd | [
0.024650827050209045,
-0.020518483594059944,
-0.05840311944484711,
-0.031767718493938446,
0.02151261642575264,
-0.026826240122318268,
0.028102455660700798,
-0.025097230449318886,
-0.01728869043290615,
0.09327027201652527,
-0.02716575562953949,
-0.013031402602791786,
-0.02069779671728611,
-... | 0.084882 |
# Resource Actions ## Overview Argo CD allows operators to define custom actions which users can perform on specific resource types. This is used internally to provide actions like `restart` for a `DaemonSet`, or `retry` for an Argo Rollout. Operators can add actions to custom resources in form of a Lua script and expa... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/resource_actions.md | master | argo-cd | [
-0.05962533876299858,
-0.037995096296072006,
-0.07025322318077087,
0.032504551112651825,
-0.07386011630296707,
-0.023722657933831215,
0.07138300687074661,
0.011233159340918064,
-0.005242952611297369,
0.07782164961099625,
-0.0115117272362113,
0.028221802785992622,
-0.07281363010406494,
-0.0... | 0.271484 |
actions. ```yaml resource.customizations.actions.argoproj.io\_Rollout: | mergeBuiltinActions: true discovery.lua: | actions = {} actions["do-things"] = {} return actions definitions: - name: do-things action.lua: | return obj ``` #### Creating new resources with a custom action > [!IMPORTANT] > Creating resources via t... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/resource_actions.md | master | argo-cd | [
-0.11516625434160233,
-0.07148426026105881,
-0.05206884443759918,
0.03337813913822174,
-0.03449356555938721,
-0.06875338405370712,
0.10839350521564484,
0.0145671796053648,
-0.013506368733942509,
0.12770892679691315,
0.03656068071722984,
0.009975324384868145,
-0.04394051432609558,
0.0282488... | 0.094988 |
so it does not get deleted cm1.metadata.annotations["argocd.argoproj.io/sync-options"] = "Prune=false" -- Keep the App synced even though it has a resource that is not in Git cm1.metadata.annotations["argocd.argoproj.io/compare-options"] = "IgnoreExtraneous" cm1.data = {} cm1.data.myKey1 = "myValue1" impactedResource1 ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/resource_actions.md | master | argo-cd | [
-0.056589409708976746,
0.0031610189471393824,
-0.028404248878359795,
0.0890674814581871,
0.04165700823068619,
-0.0701148733496666,
0.11003430932760239,
-0.041209835559129715,
-0.001072598504833877,
0.03876474127173424,
0.0484725646674633,
-0.009446612559258938,
0.01935991644859314,
-0.0595... | 0.067593 |
# Reconcile Optimization By default, an Argo CD Application is refreshed every time a resource that belongs to it changes. Kubernetes controllers often update the resources they watch periodically, causing continuous reconcile operation on the Application and a high CPU usage on the `argocd-application-controller`. Arg... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/reconcile.md | master | argo-cd | [
-0.004405757412314415,
0.038102034479379654,
-0.011882714927196503,
0.04743354767560959,
0.02802743762731552,
-0.07331067323684692,
0.06198399141430855,
-0.08621157705783844,
0.08157984167337418,
0.07266721874475479,
-0.042788341641426086,
0.034930575639009476,
-0.05027887597680092,
-0.079... | 0.149868 |
to confirm that your resource ignore rules are being applied. > [!NOTE] > These logs are at the `debug` level. Configure the application-controller's log level to `debug`. ## Examples ### argoproj.io/Application ```yaml apiVersion: v1 kind: ConfigMap metadata: name: argocd-cm data: resource.customizations.ignoreResourc... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/reconcile.md | master | argo-cd | [
-0.08398199081420898,
0.0299371387809515,
-0.012576578184962273,
0.028695233166217804,
0.05875756964087486,
-0.08111798763275146,
0.06829657405614853,
-0.08830258250236511,
-0.008752101100981236,
0.04909490421414375,
0.0122408801689744,
-0.01392615307122469,
-0.0029639217536896467,
0.01750... | 0.104766 |
# High Availability Argo CD is largely stateless. All data is persisted as Kubernetes objects, which in turn is stored in Kubernetes' etcd. Redis is only used as a throw-away cache and can be lost. When lost, it will be rebuilt without loss of service. A set of [HA manifests](https://github.com/argoproj/argo-cd/tree/st... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
0.015057990327477455,
-0.020619116723537445,
-0.054799553006887436,
0.020297013223171234,
-0.021315740421414375,
-0.023356517776846886,
-0.01376358512789011,
0.008771348744630814,
-0.008768412284553051,
0.08007725328207016,
-0.012841496616601944,
0.05348126217722893,
-0.07776259630918503,
... | 0.190126 |
Management Plugins (CMP), `argocd-repo-server` copies the repository (or only the files specified via the `argocd.argoproj.io/manifest-generate-paths` annotation) into a separate directory for each plugin. This can place a heavy load on disk resources for a \*\*argocd-repo-server\*\*, especially if the repository conta... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
-0.043388668447732925,
-0.05478610098361969,
-0.08965133875608444,
0.0449792705476284,
0.0465097576379776,
-0.12607087194919586,
0.06073056161403656,
-0.012778162024915218,
0.027776215225458145,
0.10461734235286713,
0.010379304178059101,
0.02131490409374237,
-0.04886496439576149,
0.0279692... | 0.102503 |
will be calculated on the fly by the application controller. \* The shard distribution algorithm of the `argocd-application-controller` can be set by using the `--sharding-method` parameter. Supported sharding methods are: - `legacy` mode uses an `uid` based distribution (non-uniform). - `round-robin` uses an equal dis... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
0.055596306920051575,
-0.02468273602426052,
-0.08212944120168686,
0.00009302073158323765,
-0.029874781146645546,
-0.07915390282869339,
-0.026900898665189743,
-0.023819996044039726,
0.016247976571321487,
0.043341014534235,
-0.008155022747814655,
0.04339208826422691,
0.04705045744776726,
-0.... | 0.040792 |
time duration string, e.g. `1ms`, `1s`, `1m`, `1h`. The default value is `100ms`. The variable is used only when `ARGOCD\_CLUSTER\_CACHE\_BATCH\_EVENTS\_PROCESSING` is set to `true`. \* `ARGOCD\_APPLICATION\_TREE\_SHARD\_SIZE` - environment variable controlling the max number of resources stored in one Redis key. Split... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
0.02301897294819355,
0.00030139877344481647,
-0.11932072788476944,
0.02206776663661003,
-0.05494732782244682,
-0.06831225752830505,
0.01820257678627968,
0.043663088232278824,
0.07570668309926987,
0.02678222395479679,
0.0038128395099192858,
-0.039288781583309174,
0.008346609771251678,
-0.08... | 0.199077 |
affect repositories with multiple applications. You can use the `argocd.argoproj.io/manifest-generate-paths` Application CRD annotation to solve this problem and improve performance. Note: The `argocd.argoproj.io/manifest-generate-paths` annotation is available for use with webhooks. Since Argo CD v2.11, this annotatio... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
-0.06446056067943573,
0.059903256595134735,
-0.03990354388952255,
-0.03016759641468525,
0.01886136084794998,
-0.0858679935336113,
0.05179149657487869,
-0.004063492640852928,
0.0007514390163123608,
0.023658357560634613,
-0.028901133686304092,
-0.04322797805070877,
-0.015509641729295254,
-0.... | 0.125636 |
expires. With a large number of applications, this will cause a spike in the refresh queue and can cause a spike to the repo-server component. To avoid this, you can set a jitter to the sync timeout which will spread out the refreshes and give time to the repo-server to catch up. The jitter is the maximum duration that... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
-0.09994211047887802,
-0.06322696805000305,
-0.09231600165367126,
0.019960271194577217,
-0.04279115051031113,
-0.056076232343912125,
0.027727492153644562,
-0.05782778188586235,
0.05152791365981102,
0.03451518714427948,
0.02685404010117054,
0.0676124095916748,
-0.021887466311454773,
-0.0509... | 0.087101 |
When `WORKQUEUE\_FAILURE\_COOLDOWN\_NS` = 0 : ``` backoff = WORKQUEUE\_BASE\_DELAY\_NS ``` ## HTTP Request Retry Strategy In scenarios where network instability or transient server errors occur, the retry strategy ensures the robustness of HTTP communication by automatically resending failed requests. It uses a combina... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/high_availability.md | master | argo-cd | [
-0.08121256530284882,
0.008099477738142014,
-0.006222970318049192,
0.07577970623970032,
-0.11859835684299469,
-0.07006615400314331,
0.0051174648106098175,
-0.03257374092936516,
-0.024881500750780106,
0.06760883331298828,
-0.03442159667611122,
0.06217353418469429,
0.021808408200740814,
-0.0... | 0.126346 |
# Dynamic Cluster Distribution > [!WARNING] > \*\*Alpha Feature (Since v2.9.0)\*\* > > This is an experimental, [alpha-quality](https://github.com/argoproj/argoproj/blob/main/community/feature-status.md#alpha) feature. > It may be removed in future releases or modified in backwards-incompatible ways. \*Current Status: ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/dynamic-cluster-distribution.md | master | argo-cd | [
0.004859904292970896,
-0.03804651275277138,
-0.024852484464645386,
0.03064982034265995,
-0.007653703447431326,
-0.05450699105858803,
-0.015338176861405373,
-0.03944425284862518,
-0.017172079533338547,
0.03241407126188278,
-0.018006734549999237,
0.04627498611807823,
-0.0345723032951355,
0.0... | 0.121643 |
instead reads the replica count directly from the Application Controller Deployment. The controller identifies the change in the number of replicas by comparing the replica count in the Application Controller Deployment and the number of mappings in the `argocd-app-controller-shard-cm` ConfigMap. In the scenario when t... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/dynamic-cluster-distribution.md | master | argo-cd | [
0.036302391439676285,
-0.09925195574760437,
-0.0728602409362793,
0.027489420026540756,
0.007787507493048906,
-0.02458682842552662,
0.03281412646174431,
-0.03731539472937584,
0.037691131234169006,
0.0712357610464096,
0.10180587321519852,
0.017364656552672386,
0.08007307350635529,
-0.0861421... | 0.099349 |
# Git Webhook Configuration ## Overview Argo CD polls Git repositories every three minutes to detect changes to the manifests. To eliminate this delay from polling, the API server can be configured to receive webhook events. Argo CD supports Git webhook notifications from GitHub, GitLab, Bitbucket, Bitbucket Server, Az... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/webhook.md | master | argo-cd | [
-0.059090469032526016,
-0.017648225650191307,
-0.070318304002285,
0.022459309548139572,
0.01161844190210104,
-0.10955356061458588,
0.05629619210958481,
-0.049583449959754944,
0.049501027911901474,
0.07524536550045013,
-0.011724567972123623,
-0.0736764445900917,
0.009892686270177364,
-0.065... | 0.10643 |
```yaml apiVersion: v1 kind: Secret metadata: name: argocd-secret namespace: argocd type: Opaque data: ... stringData: # github webhook secret webhook.github.secret: shhhh! it's a GitHub secret # gitlab webhook secret webhook.gitlab.secret: shhhh! it's a GitLab secret # bitbucket webhook secret webhook.bitbucket.uuid: ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/webhook.md | master | argo-cd | [
-0.09144816547632217,
0.03557056188583374,
-0.08267013728618622,
0.017776215448975563,
0.022922109812498093,
-0.07911008596420288,
0.047126952558755875,
-0.06577657908201218,
0.06141462177038193,
0.11353844404220581,
0.0550287626683712,
-0.052062198519706726,
0.03552505373954773,
-0.077977... | 0.023781 |
# Secret Management There are two general ways to populate secrets when doing GitOps: on the destination cluster, or in Argo CD during manifest generation. We strongly recommend the former, as it is more secure and provides a better user experience. For further discussion, see [#1364](https://github.com/argoproj/argo-c... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/secret-management.md | master | argo-cd | [
-0.07298282533884048,
-0.010777129791676998,
-0.02597903646528721,
0.04499034583568573,
-0.01670246385037899,
-0.007850020192563534,
0.04915313050150871,
0.024331163614988327,
0.05842016637325287,
0.098200723528862,
0.023366013541817665,
0.03146803379058838,
-0.01665925420820713,
-0.080706... | 0.224366 |
# Declarative Setup Argo CD applications, projects and settings can be defined declaratively using Kubernetes manifests. These can be updated using `kubectl apply`, without needing to touch the `argocd` command-line tool. ## Quick Reference All resources, including `Application` and `AppProject` specs, have to be insta... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
0.004411245230585337,
-0.017645129933953285,
-0.039430469274520874,
-0.043529216200113297,
-0.06358867138624191,
-0.03483472764492035,
0.02541244961321354,
0.017670942470431328,
0.009519657120108604,
0.07286752760410309,
0.009052547626197338,
-0.07585958391427994,
-0.04057663679122925,
-0.... | 0.142178 |
specified instead of the `path` attribute within `spec.source`. ```yaml spec: project: default source: repoURL: https://argoproj.github.io/argo-helm chart: argo ``` > [!WARNING] > Without the `resources-finalizer.argocd.argoproj.io` finalizer, deleting an application will not delete the resources it manages. To perform... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.026006875559687614,
-0.014226432889699936,
-0.048867784440517426,
-0.014532140456140041,
0.07824517786502838,
-0.07074116915464401,
0.04573504254221916,
-0.007265528663992882,
0.02180406264960766,
0.08040014654397964,
0.011253643780946732,
-0.005977623164653778,
0.007534130476415157,
0.... | 0.145098 |
with `.git`. Repository details are stored in secrets. To configure a repo, create a secret which contains repository details. Consider using [bitnami-labs/sealed-secrets](https://github.com/bitnami-labs/sealed-secrets) to store an encrypted secret definition as a Kubernetes manifest. Each repository must have a `url` ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.04212748259305954,
-0.03137591853737831,
-0.03709752857685089,
0.00655743945389986,
-0.0730045735836029,
0.010348792187869549,
0.008015094324946404,
0.045538291335105896,
0.09072969108819962,
0.006828610319644213,
0.02488821931183338,
-0.06898821145296097,
0.07921747118234634,
0.0359434... | 0.053269 |
match will take precedence. The order of definition is not important, as opposed to pre v1.4 configuration. The following keys are valid to refer to credential secrets: #### SSH repositories \* `sshPrivateKey` refers to the SSH private key for accessing the repositories #### HTTPS repositories \* `username` and `passwo... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.06652620434761047,
0.037366390228271484,
-0.013300708495080471,
-0.06600113958120346,
-0.04266560822725296,
-0.01452294085174799,
-0.00597386946901679,
-0.006761133670806885,
0.09097569435834885,
-0.0013378770090639591,
0.05037827417254448,
-0.026927674189209938,
0.09151969105005264,
0.... | -0.018356 |
Argo CD (unlike TLS configuration), otherwise the connections to the repository will fail. You can manage the SSH known hosts data in the `argocd-ssh-known-hosts-cm` ConfigMap. This ConfigMap contains a single entry, `ssh\_known\_hosts`, with the public keys of the SSH servers as its value. The value can be filled in f... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
0.01392803993076086,
0.009879094548523426,
-0.11455308645963669,
0.06349281966686249,
-0.05890781432390213,
-0.04828386381268501,
0.03282284364104271,
-0.09120737016201019,
0.047316357493400574,
0.15268993377685547,
0.016347454860806465,
-0.011636178940534592,
0.0814361646771431,
-0.036791... | 0.037069 |
restricted using the `namespaces` list. \* `project` - optional string to designate this as a project-scoped cluster. \* `config` - JSON representation of the following data structure: ```yaml # Basic authentication settings username: string password: string # Bearer authentication settings bearerToken: string # IAM au... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.016331491991877556,
0.022167639806866646,
-0.017575999721884727,
-0.01636764593422413,
-0.05274656414985657,
0.04999525099992752,
-0.0038681989535689354,
0.016832992434501648,
0.057099584490060806,
0.046411916613578796,
-0.02538263611495495,
-0.10385911911725998,
0.020490845665335655,
0... | 0.137775 |
policy suitable for this need. Ensure that the Argo CD cluster has an [IAM OIDC provider configured](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html) or [Pod Identity agent running](https://docs.aws.amazon.com/eks/latest/userguide/pod-id-agent-setup.html) \*\*for IRSA:\*\* ``... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.03747277706861496,
0.035771340131759644,
-0.05643593519926071,
0.03337816521525383,
0.0013243741123005748,
-0.0027862347196787596,
0.06413979828357697,
-0.058239199221134186,
0.02222451940178871,
0.09958283603191376,
0.05342651531100273,
-0.04180166870355606,
-0.009019818156957626,
-0.0... | 0.145329 |
assumed by the `ARGO\_CD\_MANAGEMENT\_IAM\_ROLE\_NAME` role looks like this: \*\*for IRSA:\*\* ```json { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam:::role/" }, "Action": "sts:AssumeRole" } ] } ``` \*\*for Pod Identity:\*\* ```json { "Version": "2012-10-17", "Statemen... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.012455863878130913,
0.06774206459522247,
-0.03389114886522293,
0.041890863329172134,
0.014343657530844212,
-0.02164824865758419,
0.08837155252695084,
-0.057948581874370575,
0.0015193819999694824,
0.057528056204319,
0.06080580875277519,
-0.05302216112613678,
-0.013773184269666672,
0.0480... | 0.15648 |
} } ``` This example assumes that the role being attached to the credentials that have been supplied, if this is not the case the role can be appended to the `args` section like so: ```yaml ... "args": ["aws", "--cluster-name", "my-eks-cluster", "--role-arn", "arn:aws:iam:::role/"], ... ``` This construct can be used i... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.06389133632183075,
0.043095242232084274,
-0.07765333354473114,
0.041768547147512436,
-0.0298448596149683,
0.005016466602683067,
0.08918479084968567,
-0.0192093588411808,
0.042642369866371155,
0.05260379984974861,
0.02173715829849243,
-0.03789975121617317,
0.07750500738620758,
-0.0131706... | 0.159421 |
to the environment variables above, argocd-k8s-auth accepts two extra environment variables to set the AAD environment, and to set the AAD server application ID. The AAD server application ID will default to 6dae42f8-4368-4678-94ff-3960e28e3630 if not specified. See [here](https://github.com/azure/kubelogin#exec-plugin... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
0.004684622399508953,
-0.008774888701736927,
-0.07348780333995819,
-0.023955579847097397,
-0.11690277606248856,
0.0034220709931105375,
0.06855015456676483,
-0.07967899739742279,
0.07945533096790314,
0.1515527218580246,
-0.0009635246824473143,
-0.05571993440389633,
0.020760564133524895,
0.0... | 0.079444 |
and `tlsClientCertKey` can be specified as desired. Helm Chart Repository: ```yaml apiVersion: v1 kind: Secret metadata: name: argo-helm namespace: argocd labels: argocd.argoproj.io/secret-type: repository stringData: name: argo url: https://argoproj.github.io/argo-helm type: helm username: my-username password: my-pas... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.038409896194934845,
0.05314752459526062,
-0.03714683651924133,
-0.01673794351518154,
-0.011517818085849285,
-0.06232575327157974,
0.005673212930560112,
-0.01632656902074814,
0.06611307710409164,
0.038348447531461716,
0.011294031515717506,
-0.053271591663360596,
0.03457579016685486,
-0.0... | -0.021091 |
the feature and controller will continue to monitor all resources. Users who are comfortable with an increase in kube api-server calls can opt for `strict` option while users who are concerned with higher api calls and are willing to compromise on the accuracy can opt for the `normal` option. Notes: \* When set to use ... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/declarative-setup.md | master | argo-cd | [
-0.009457817301154137,
0.003953323233872652,
-0.1493072509765625,
0.007527303881943226,
-0.011232249438762665,
0.0017406544648110867,
0.09058786928653717,
-0.019318806007504463,
-0.008532990701496601,
0.025439748540520668,
0.037494998425245285,
-0.05859962850809097,
-0.011218678206205368,
... | 0.209691 |
# Config Management Plugins Argo CD's "native" config management tools are Helm, Jsonnet, and Kustomize. If you want to use a different config management tool, or if Argo CD's native tool support does not include a feature you need, you might need to turn to a Config Management Plugin (CMP). The Argo CD "repo server" c... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.02029692381620407,
-0.044572215527296066,
-0.03261873126029968,
-0.012739810161292553,
-0.04456464201211929,
-0.033793020993471146,
0.06221546232700348,
-0.01259294617921114,
-0.03289678692817688,
0.08795329928398132,
0.027942772954702377,
-0.034893784672021866,
-0.049846962094306946,
0... | 0.166175 |
directory) glob patterns. glob: "\*\*/Chart.yaml" # The find command runs in the repository's root directory. To match, it must exit with status code 0 \_and\_ # produce non-empty output to standard out. command: [sh, -c, find . -name env.yaml] # The parameters config describes what parameters the UI should display for... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.08386661112308502,
-0.0003844322054646909,
-0.0152781642973423,
0.0387655571103096,
0.01701573096215725,
-0.01807706244289875,
0.0477568618953228,
0.041532743722200394,
0.033601827919483185,
-0.01754259504377842,
0.07287921756505966,
-0.02548402175307274,
0.029943525791168213,
0.0061447... | 0.09907 |
only follows kubernetes-style spec conventions. The `generate` command must print a valid Kubernetes YAML or JSON object stream to stdout. Both `init` and `generate` commands are executed inside the application source directory. The `discover.fileName` is used as [glob](https://pkg.go.dev/path/filepath#Glob) pattern to... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.07602176070213318,
0.01809803582727909,
-0.013319948688149452,
0.020345648750662804,
-0.0006510224775411189,
0.00431050593033433,
0.00007994893530849367,
-0.020159799605607986,
0.01975305937230587,
0.06169460341334343,
0.0911780595779419,
-0.05772271379828453,
-0.06514974683523178,
0.00... | 0.117223 |
This prevents users from directly setting potentially-sensitive environment variables. 4. Parameters in the Application spec: apiVersion: argoproj.io/v1alpha1 kind: Application spec: source: plugin: parameters: - name: values-files array: [values-dev.yaml] - name: helm-parameters map: image.tag: v1.2.3 The parameters a... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
0.009920363314449787,
0.049240246415138245,
-0.04170004650950432,
0.0162555780261755,
0.03662658855319023,
-0.016522007063031197,
0.028605373576283455,
0.04109102860093117,
-0.02467401511967182,
0.031152458861470222,
0.019445454701781273,
-0.031170861795544624,
-0.04004831239581108,
0.0457... | 0.087497 |
If a CMP command fails to gracefully exit on `ARGOCD\_EXEC\_TIMEOUT`, it will be forcefully killed after an additional timeout of `ARGOCD\_EXEC\_FATAL\_TIMEOUT`. ## Debugging a CMP If you are actively developing a sidecar-installed CMP, keep a few things in mind: 1. If you are mounting plugin.yaml from a ConfigMap, you... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
0.016198549419641495,
0.01162643451243639,
0.00838978961110115,
0.02310025319457054,
0.04604514315724373,
-0.05133388936519623,
-0.03940565139055252,
0.00938271451741457,
-0.052743956446647644,
0.06844178587198257,
0.11031319946050644,
0.002633767668157816,
-0.04510638117790222,
-0.0268392... | 0.069335 |
ConfigMap entry into a config file First, copy the plugin's configuration into its own YAML file. Take for example the following ConfigMap entry: ```yaml data: configManagementPlugins: | - name: pluginName init: # Optional command to initialize application source directory command: ["sample command"] args: ["sample arg... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.04284024238586426,
-0.04701869934797287,
-0.037099841982126236,
0.03170761466026306,
-0.018614286556839943,
-0.005657500121742487,
0.03913770243525505,
0.003809182206168771,
-0.012147190049290657,
0.07136524468660355,
0.037088435143232346,
-0.07921378314495087,
-0.01704704388976097,
-0.... | 0.124148 |
files mode By default, config management plugin receives source repository files with reset file mode. This is done for security reasons. If you want to preserve original file mode, you can set `preserveFileMode` to `true` in the plugin spec: > [!WARNING] > Make sure you trust the plugin you are using. If you set `pres... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/config-management-plugins.md | master | argo-cd | [
-0.0925079733133316,
-0.05592474341392517,
-0.0584590919315815,
0.06465063244104385,
0.026742177084088326,
-0.037066422402858734,
0.07130119949579239,
-0.0057813627645373344,
0.004026744980365038,
0.06918056309223175,
0.05932701751589775,
0.05879499390721321,
-0.013593641109764576,
-0.0021... | 0.097544 |
# Git Configuration ## System Configuration Argo CD uses the Git installation from its base image (Ubuntu), which includes a standard system configuration file located at `/etc/gitconfig`. This file is minimal, just defining filters necessary for Git LFS functionality. You can customize Git's system configuration by mo... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/git_configuration.md | master | argo-cd | [
0.0015988359227776527,
-0.08761071413755417,
0.0031310529448091984,
0.0233160350471735,
0.03504610061645508,
-0.07888877391815186,
0.055139366537332535,
0.013229157775640488,
-0.024249276146292686,
0.07028815150260925,
0.037682872265577316,
0.04413807764649391,
-0.02229379676282406,
-0.002... | 0.071458 |
# Metrics Argo CD exposes different sets of Prometheus metrics per server. ## Application Controller Metrics Metrics about applications. Scraped at the `argocd-metrics:8082/metrics` endpoint. | Metric | Type | Description | | ------------------------------------------------- | :-------: | ------------------------------... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/metrics.md | master | argo-cd | [
-0.01434520073235035,
-0.033417779952287674,
-0.1306128054857254,
-0.001258153235539794,
-0.07882332056760788,
-0.09337541460990906,
0.02284395508468151,
0.014273015782237053,
-0.0007099167560227215,
0.013515637256205082,
-0.002411563415080309,
-0.07292257994413376,
-0.036504171788692474,
... | 0.158705 |
apps | Group name of a Kubernetes resource being monitored. | | host | example.com | Hostname of the Kubernetes API to which the request was made. | | hostname | argocd-application-controller-0 | Hostname of the Argo CD component that initiated the request to Redis. | | initiator | argocd-server | Name of the Argo CD c... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/metrics.md | master | argo-cd | [
-0.025390371680259705,
-0.024242931976914406,
-0.10700982809066772,
-0.0024144132621586323,
-0.034507010132074356,
-0.05428299680352211,
0.06662292778491974,
-0.02150052599608898,
0.08303830772638321,
0.08030673116445541,
-0.0003862191515509039,
-0.04690426588058472,
-0.004907801281660795,
... | 0.245556 |
- ExcludedResourceWarning ``` ## Application Set Controller metrics The Application Set controller exposes the following metrics for application sets. | Metric | Type | Description | | ------------------------------------------------- | :-------: | -----------------------------------------------------------------------... | https://github.com/argoproj/argo-cd/blob/master//docs/operator-manual/metrics.md | master | argo-cd | [
0.0005947704776190221,
-0.02293200045824051,
-0.08057655394077301,
-0.030799625441432,
-0.0470808744430542,
0.033854689449071884,
0.10990255326032639,
0.03511456027626991,
0.03527500480413437,
-0.03428009897470474,
-0.004855197388678789,
-0.08047207444906235,
0.060419730842113495,
-0.08264... | 0.064712 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.