![]() I wanted to be able to keep all the sites we monitored in two files without having to modify the prometheus.yml every time I needed to add or remove a site which could require a reload of Prometheus. We host a bunch of small WordPress and other custom built websites (along with a couple very large sites) that we use the Blackbox exporter to monitor the response code and SSL Certificate status. The amount of visibility into our infrastructure it has provided that we didn’t have before has been invaluable. This is disabled by default as an optimization, but since processes can choose to change their names, this may result in a process falling into the wrong group if we happen to see it for the first time before it's assumed its proper name.In the past year I moved our teams entire infrastructure monitoring from Nagios/collectd to Prometheus. recheck On each scrape the process names are re-evaluated.procnames Comma separated list of process names to monitor.It allows assigning a name to a process based on a combination of the process name and command line namemapping Comma-separated list of alternating name,regexp values.debug Print debug information to the log.custom_options Use for your configuration if defined properties are not satisfying your needs.Alternately specific process names and groups may be specified using the proc_names and name_mapping properties The example below monitors all processes on the system. config_path Optional config file for configuring which processes to monitor.children If a proc is tracked, track with it any children that aren't part of their own group (default: true).Monitor resource usage of processes or process groups. web_listen_address Address to listen on for web interface and telemetry.instance_name name of PostgreSQL exporter instance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |