Prometheus Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
=Configuration Operations= | =Configuration Operations= | ||
==Configure a Target== | ==Configure a Target== | ||
Examples: | |||
{{Internal|Prometheus_Pushgateway#Configure_Pushgateway_as_a_Prometheus_Target|Configure Pushgateway as a Target}} | {{Internal|Prometheus_Pushgateway#Configure_Pushgateway_as_a_Prometheus_Target|Configure Pushgateway as a Target}} | ||
=Configuring Prometheus with Prometheus Operator= | =Configuring Prometheus with Prometheus Operator= | ||
{{Internal|Configuring Prometheus with Prometheus Operator|Configuring Prometheus with Prometheus Operator}} | {{Internal|Configuring Prometheus with Prometheus Operator|Configuring Prometheus with Prometheus Operator}} | ||
Latest revision as of 21:44, 14 October 2020
External
Internal
Overview
Prometheus is configured in a prometheus.yaml configuration file. The "global" block controls the server's global configuration. The "rule_files" block specifies the location of any rules to load. The "scrape_configs" controls the targets.
global:
scrape_interval: 15s
evaluation_interval: 15s
rule_files:
# - "first.rules"
# - "second.rules"
scrape_configs:
- job_name: prometheus
static_configs:
- targets: ['localhost:9090']
scrape_configs
Configuration Operations
Configure a Target
Examples: