Editing Prometheus
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | [[wikipedia:Prometheus (software)|Prometheus]] is an open-source systems [[monitoring]] and [[alerting]] toolkit <ref>https://prometheus.io/docs/introduction/overview/</ref> released in [[2012]]. Prometheus design is focused to [[collect]] and process metrics, not as an event logging system for | + | [[wikipedia:Prometheus (software)|Prometheus]] is an open-source systems [[monitoring]] and [[alerting]] toolkit<ref>https://prometheus.io/docs/introduction/overview/</ref> released in [[2012]]. Prometheus design is focused to [[collect]] and process metrics, not as an event logging system for logs.<ref>https://prometheus.io/docs/introduction/faq/#how-to-feed-logs-into-prometheus?</ref>. [[Grafana]] is usually used to produce [[dashboards]]. |
* https://prometheus.io/ | * https://prometheus.io/ | ||
== [[Prometheus Installation]]== | == [[Prometheus Installation]]== | ||
| + | * <code>[[brew install]] prometheus</code> | ||
| + | * <code>[[apt install prometheus]]</code> | ||
* http://localhost:9090 | * http://localhost:9090 | ||
| − | |||
[[Kubernetes]] | [[Kubernetes]] | ||
| − | * <code>[[helm repo add prometheus-community https://prometheus-community.github.io/helm-charts | + | * <code>[[helm repo add]] prometheus-community https://prometheus-community.github.io/helm-charts</code> |
* <code>[[helm install myprometheus prometheus-community/prometheus]]</code> | * <code>[[helm install myprometheus prometheus-community/prometheus]]</code> | ||
| Line 13: | Line 14: | ||
* Linux: <code>[[/etc/prometheus/prometheus.yml]]</code> | * Linux: <code>[[/etc/prometheus/prometheus.yml]]</code> | ||
* macOS: <code>[[/usr/local/etc/prometheus.args]]</code> | * macOS: <code>[[/usr/local/etc/prometheus.args]]</code> | ||
| − | |||
== Binaries == | == Binaries == | ||
| Line 19: | Line 19: | ||
* <code>[[promtool]]</code> | * <code>[[promtool]]</code> | ||
* <code>[[tsdb]]</code> | * <code>[[tsdb]]</code> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Configuration == | == Configuration == | ||
| Line 31: | Line 26: | ||
* In the '''global''' settings, define the default interval for scraping metrics. Note that Prometheus will apply these settings to every exporter unless an individual exporter's own settings override the global. | * In the '''global''' settings, define the default interval for scraping metrics. Note that Prometheus will apply these settings to every exporter unless an individual exporter's own settings override the global. | ||
| − | * This ''' | + | * This '''scrape_interval''' value tells Prometheus to collect metrics from its exporters every 15 seconds, which is long enough for most exporters. Now, add Prometheus itself to the list of exporters to scrape from with the following s'''crape_configs''' directive: |
* Prometheus uses the '''job_name''' to label exporters in queries and on graphs, so be sure to pick something descriptive here. And, as Prometheus exports important data about itself that you can use for monitoring performance and debugging, we've overridden the global '''scrape_interval''' directive from 15 seconds to 5 seconds for more frequent updates. Lastly, Prometheus uses the '''static_configs''' and '''targets''' directives to determine where exporters are running. Since this particular exporter is running on the same server as Prometheus itself, we can use localhost instead of an IP address along with the default port, '''[[9090]]'''. | * Prometheus uses the '''job_name''' to label exporters in queries and on graphs, so be sure to pick something descriptive here. And, as Prometheus exports important data about itself that you can use for monitoring performance and debugging, we've overridden the global '''scrape_interval''' directive from 15 seconds to 5 seconds for more frequent updates. Lastly, Prometheus uses the '''static_configs''' and '''targets''' directives to determine where exporters are running. Since this particular exporter is running on the same server as Prometheus itself, we can use localhost instead of an IP address along with the default port, '''[[9090]]'''. | ||
| Line 49: | Line 44: | ||
</pre> | </pre> | ||
| − | == Linux Basic Prometheus Operations == | + | ==Linux Basic Prometheus Operations== |
| − | * '''Start''' Prometheus: :<code> | + | * '''Start''' Prometheus: :<code>sudo systemctl start prometheus</code> |
| − | * '''Reload''' systemd: :<code> | + | * '''Reload''' systemd: :<code>sudo systemctl daemon-reload prometheus</code> |
| − | * '''Verify''' the service's status: :<code>sudo | + | * '''Verify''' the service's status: :<code>sudo systemctl status prometheus</code> |
* Delete all data: | * Delete all data: | ||
| Line 75: | Line 70: | ||
* <code>[[alert:]]</code> | * <code>[[alert:]]</code> | ||
* [[AWS CloudWatch Container Insights]] | * [[AWS CloudWatch Container Insights]] | ||
| − | * [[ | + | * [[Thanos]] |
| + | * [[VictoriaMetrics]] | ||
* [[Kubernetes Metrics Server]] | * [[Kubernetes Metrics Server]] | ||
* [[Fluent Bit]] | * [[Fluent Bit]] | ||
* [[GitLab 12.5]] Automatically close GitLab issues with recovery alerts from [[Prometheus]] | * [[GitLab 12.5]] Automatically close GitLab issues with recovery alerts from [[Prometheus]] | ||
| + | * [[Grafana Mimir]] | ||
* [[Prometheus-node-exporter Debian configuration file]] | * [[Prometheus-node-exporter Debian configuration file]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== See also == | == See also == | ||
| − | |||
* {{Prometheus}} | * {{Prometheus}} | ||
| + | * {{Grafana}} | ||
* {{monitoring software}} | * {{monitoring software}} | ||
* {{TSDB}} | * {{TSDB}} | ||
Advertising:
