Such requests could be offloaded to community if ZBXNEXT-2651 was implemented.

First version of acceptance criteria with suggested design is attached. ACC Prometheus integration.pdf

Apparently, it's not a MS Word document...

Yep. Can you provide a pdf instead?

Weird. I can only open file from the PC, not from mobile phone. Re-uploaded as PDF.

Item prototype example uses {#KEY} as item key. LLD macros are supported in item key parameters, not in item key itself.

Very good work, I hope to test soon to understand if is easy to start to monitoring application like "OpenShift".
Another topic on Kubernetes cluster could be, how i could automatically create PODS on Zabbix using the Prometheus exporters data? Host Prototypes? Have you some ideas?

Hi Dev Team,
this new feature is still planned for Zabbix 4.2?
Thanks

dimitri.bellini, yes

Very good, we need a customer case to setup
Do you think we could start to monitoring Openshift/Kubernetes with the actual feature sets?

Released in:

• pre-4.2.0rc1 r91109

API documentation updated:

• https://www.zabbix.com/documentation/4.2/manual/api/changes_4.0_-_4.2
• https://www.zabbix.com/documentation/4.2/manual/api/reference/item/object
• https://www.zabbix.com/documentation/4.2/manual/api/reference/item/get
• https://www.zabbix.com/documentation/4.2/manual/api/reference/itemprototype/object
• https://www.zabbix.com/documentation/4.2/manual/api/reference/itemprototype/get
• https://www.zabbix.com/documentation/4.2/manual/api/reference/discoveryrule/object
• https://www.zabbix.com/documentation/4.2/manual/api/reference/discoveryrule/get

dimitri.bellini Did you manage to try to automatically create pods?

@Kirill Dudka at the moment i could not test it, i'm waiting the Zabbix Documentation

Is there interest in the Zabbix community in forming a working-group to create a comprehensive Kubernetes monitoring Template that has feature parity with Prometheus? The ability to auto-discover pods, containers, etc. Would be great to build a robust solution, share it with the community, and possibly maintain it as a group to support future versions.

I’m able to provide compute resources for running a development environment for us to perform testing and provide a space for collaboration.  If anyone is interested, please message me privately ([email protected]).

cc: vzhuravlev

Hi Zabbix Team,
i tried the new feature on Zabbix 4.2.0 but i'm very confusing, i have tested with a simple exporter (https://github.com/nlamirault/speedtest_exporter). From that exporter i could receive the below metrics:

# HELP go_gc_duration_seconds A summary of the GC invocation durations.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 5.233e-05
go_gc_duration_seconds{quantile="0.25"} 6.3163e-05
go_gc_duration_seconds{quantile="0.5"} 7.107000000000001e-05
go_gc_duration_seconds{quantile="0.75"} 7.271e-05
go_gc_duration_seconds{quantile="1"} 8.303000000000001e-05
go_gc_duration_seconds_sum 0.000624217
go_gc_duration_seconds_count 9
# HELP go_goroutines Number of goroutines that currently exist.
# TYPE go_goroutines gauge
go_goroutines 24
# HELP go_memstats_alloc_bytes Number of bytes allocated and still in use.
# TYPE go_memstats_alloc_bytes gauge
go_memstats_alloc_bytes 3.370152e+06
# HELP go_memstats_alloc_bytes_total Total number of bytes allocated, even if freed.
# TYPE go_memstats_alloc_bytes_total counter
go_memstats_alloc_bytes_total 3.2114744e+07
# HELP go_memstats_buck_hash_sys_bytes Number of bytes used by the profiling bucket hash table.
# TYPE go_memstats_buck_hash_sys_bytes gauge
go_memstats_buck_hash_sys_bytes 1.448797e+06
# HELP go_memstats_frees_total Total number of frees.
# TYPE go_memstats_frees_total counter
go_memstats_frees_total 334739

I have created an HTTP Check Item with a Prometheus step, below the detail:

• Parameters: go_gc_duration_seconds_count

every time i will test it i sow an error that say "", check the screenshot.

What i'm wrong?

Thanks very much!

When sending mutliline input data frontend terminates lines with CR LF (\r\n) while promeheus protocol expects only LF (\n).

Created ZBX-15933. Note that only the testing is affected. Data obtained from prometheus agents should be parsed without errors, but of course it's hard to setup it without testing.

Ok we have found the trick
I think is very useful to find a "fix" for the testing feature.
Thank you!

Updated documentation:

• What's new
• Prometheus checks
• Discovery using Prometheus data