Hello Yolanda
Where is the document about accepted parameter to set after “includedRegistries”
Thanks for help
Envoyé à partir de l'app mail mobile
sur 14/08/2023 le 17:38, Yolanda Davis écrivit:
Hi Aaron,
Great to hear it's something you can use! You are correct in that it should expose everything that the PrometheusReportingTask does. It also has the ability to limit the metrics exposed on the endpoint, however it is different from how the reporting task can limit metrics. So for example let's say you only want to make JVM or NIFi specific metrics available, you can pass that as a parameter value to only include the registries for those metrics (e.g. https://localhost:8443/nifi-api/flow/metrics/prometheus?includedRegistries=JVM). There are other filtering mechanisms, but you can also just limit what Prometheus scrapes using its own scrape configurations.
One thing also to be mindful of is the amount of metrics you are collecting and your storage constraints in Prometheus. Depending on the size of your flow there could be lots of metrics produced for components. The amount of space needed for these metrics are driven not just by the name and value pair but also the labels associated with it; so you may want to consider how to configure your scrape to grab only what is necessary, at intervals that best matches your query needs.
Again, I hope this is helpful!
Hi Yolanda,
That is SUPER helpful to know. This looks like a great starting point.
It looks like this is equivalent to reporting task for all components. Is that correct? I'll have to see if I can get Prometheus to scrape it with a secure endpoint.
Thanks for the starting pointer!
-Aaron
Hi Aaron,
Just wanted to provide some additional info that hopefully will be useful. NiFi also has a dedicated prometheus endpoint that can be scraped directly, without needing to set up a specific task. That endpoint can be found (in a local host example) under https://localhost:8443/nifi-api/flow/metrics/prometheus. From here you can see the metrics NiFi makes available and prometheus can be configured to scrape depending on the security settings you have in place. Again hope this helps, and good luck!
-yolanda
This list is perfectly fine.
All of our metrics are available via push, pull, and prometheus so it can def be done. It would be great to see what you end up with.
Thanks
Hi,
Not sure if this belongs on the dev or user mailing list but figured would start with user.
I wanted to see if there is a way to create the same graphs available in the status displays using grafana? I'm assuming I would need to use a prometheus reporting task but wanted to know if all the metrics are reported to generate same graphs.
I want to be able to graph nifi performance metrics at the same time as my kubernetes cluster metrics so I can understand how they relate and what resources are impacting any slow down in performance of NiFi.
If anyone has already attempted this, wouls love to get any pointers for implementing.
Thanks.
--
--
|
