Skip to content

Latest commit

 

History

History
61 lines (43 loc) · 2.31 KB

INTEGRATING.md

File metadata and controls

61 lines (43 loc) · 2.31 KB

Deployment scenarios

graph LR

subgraph LXD model 1
nrpe --- cos-proxy --- sc1[scrape-config]
end

sc1 --- prometheus

subgraph LXD model 2
zookeeper --- grafana-agent --- sc2[scrape-config]
end

sc2 --- prometheus

subgraph K8s model
prometheus
end


style sc1 stroke-width:4px
style sc2 stroke-width:4px

scrape_configs manipulation

Generally, the prometheus config file (example) has the following form:

Section Provided by
global promethehus
rule_files rules from upstream charms; re-structured by prometheus
alerting alertmanager
tracing (not yet implemented)
scrape_configs upstream charms, prometheus-scrape-config

The scrape_configs section is made up of:

Subsection Provided by
job_name upstream charm (optional); topology-prefixed and deduped (consumer side)
static_configs upstream charm
metrics_path upstream charm
relabel_configs upstream charm (optional); topology-adjusted (consumer side)
scrape_interval upstream charm, prometheus-scrape-config
etc. upstream charm, prometheus-scrape-config

This charm updates some values in the scrape_configs section.

The static_configs section is made up of:

Sub-subsection Provided by
targets upstream charm (star notation expanded on consumer side)
labels upstream charm