![]() toplevel_hostgorup: default derived from the targeted hostgroup.submitter_hostgroup: defaults to the targeted hostgroup.submitter_environment: default is retrieved from Puppet.remote_producer: defaults to the folder name.To override the internal labels automatically set by MONIT: To trigger the creation of NoContact alarms: Query_interval is an optional configuration that you can use to set up a different query frequency for your targets than the default one "1m". Labels can be set for two use cases here they are, along with their related labels: monitoring/something/example) you can also specify different labels, if you need so. Here, the is of course the hostgroup you want to probe (e.g. The general structure of this file is the following: ![]() Head into your folder and create a probes.yaml file. Remember that you are only allowed to make changes in your group's folder and to the whitelist.yaml file. Now create a folder using your group's name: that's where you will operate. Whitelist yourself by adding your group's name (if it's missing) and your username under it, in a similar fashion of what is already there. If you've never configured a remote probe before, open the whitelist.yaml file: it's used to prevent accidental changes to other people's probes. First thing to do is to create a branch for your changes. How do I add a new probe?Īll probes are centrally managed in our monit-remote-probes You can either pick a module from a fixed set that we support (you can check it here) or create a custom module which can include more things, such as authentication. That allow to tweak probe settings such as the used protocol, the expected This configuration is carried out through the use of modules, which are templates To then expose the results as metrics to be scraped by Prometheus. The Blackbox exporter executes the configured probes against the remote targets, If you want to read more about the Blackbox exporter, please refer to theĪnd to the GitHub project. Over a variety of protocols: HTTP, HTTPS, TCP, DNS, ICMP. Workflow is based on Prometheus and the Blackbox exporter, probing endpoints This section explains how to setup and execute probes on remote targets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |