What is Prometheus custom services for

General
1

… and how is this intended to be used.

I can not find any documentation about this, so any hint on what this is and how it may be used may be helpful.

Thnx in advance.

2

Hallo,
perhaps the videos on youtube will answer your questions.
search for checkmk + prometheus to find some content produced by checkmk.
Ralf

3

hey @KartoffelSalat,
since the initial release of the Prometheus integration, additional features have been added, including an extension of the PromQL functionality. Slightly different to the specification in the documentation you can now specify thresholds for your custom queries.

You can define these thresholds in two different places: in the Prometheus Datasource rule (next to the custom PromQL query) or in the custom Prometheus services (that you asked about). The latter gives you more flexibility as the defined rules are based on a regex pattern, allowing you to address multiple Prometheus services at once. There is also a detailed description when you turn on the inline help within the rule itself.

Hope this helps

1 Like
4

Thank you for your replies.

I’m actually using the prometheus integration to fetch information about our k8s clusters and monitor some Metrics with PromQL.

I was just wondering about the Menu Entry in Service Monitoring Rules/Prometheus Custom Services which offers less setup options then available under VM, Cloud, Container/Proemtheus … took me some time to realize that it addresses the same plugin.

So I just guess the first one is somewhat deprecated?

5

VM, Cloud, Container/Prometheus is what I referred to as Prometheus Datasource rule in my previous answer. You can find the details here in section 2.2. The main purpose is to setup the connection to your Prometheus instance and you can also specify simple thresholds directly next to your PromQL queries.

Service Monitoring Rules/Prometheus Custom Services is what I previously described as " The latter gives you more flexibility as the defined rules are based on a regex pattern, allowing you to address multiple Prometheus services at once". In short, you are only delegating the thresholds setting from the Datasource rule to this rule. This becomes handy when you generate multiple temperature services for example and they all have the same thresholds.

Here are two scenarios which have the same outcome:

(Scenario 1) Datasource Prometheus rule: specify connection details + specify temperature related PromQL queries + specify thresholds for each PromQL query

(Scenario 2)
Datasource Prometheus rule: specify connection details + specify temperature related PromQL queries
Custom Prometheus services rule: specify temperature threshold once targeting all previously specified PromQL queries (from the Datasource rule)

Hope this makes it more clear

1 Like
6

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.