Coralogix allows you to monitor Prometheus events through webhooks. Using Alertmanager, you can track the state of instances and machines, monitor their memory, disk usage and more. Using alerts and visualizations you can gain insight into the status of these Alerts. This can help with root cause and impact analysis as well as in correlating resources with issues.
Coralogix came up with an easy solution to allow you to collect Prometheus alarms. The steps below are going to walk you through how to do so.
Promtool check rules /path to your rules.yml file.
4. Configure your alertmanager to trigger an alert once any of the rules in your rules.yml file has been satisfied.
5. Open alertmanager.yml usually it is located under /etc/alertmanger/alertmanager.yml, the path depends on your installation.
5. Add the following to the file.
route: receiver: Coralogix receivers: - name: Coralogix webhook_configs: - url: Coralogix-url send_resolved: true
|Can be any name you like but just to differentiate between your receivers put something meaningful||The same as your receiver||https://integrations.Cluster URL/v1/prometheus/v1/events/<token>|
If you’d like to specify the application name and subsystemname you can add them right after the token in the payload URL like the below example.
Cluster URL is a variable. Please match this part with a row entry within the table. Copy the table row entry located under the column that matches the top-level domain of your Coralogix account (.com, .in, etc.). Replace the variable part of the URL with this entry.
|Cluster URL||Team URL|
Please make sure to use amtool to check the alert manager config and make sure it passes. Your alert manager will not start if this config is not correct.
If the config passes you will get a success message with details about what you have configured in your alertmanger.yml.
Example of the log you would see in Coralogix UI.