-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread metrics not collected in NFQueue runmode #17
Comments
This should support NFQ with in autofp and workers mode. It also adds very basic support for the ips packet metrics as suricata_ip_blocked_packets_total Closes #17
@rowecharles / @Neurozone - could you check if v0.4.0-rc1 works for you? I've also added the |
Will check tomorrow :) |
@awelzel , I've validated on our setup and confirmed that all the thread metrics are now getting collected including the new IP packet counter metrics. Thanks a lot for the fix and all the work on the project! |
Thanks, I've pushed 0.4.0 now. |
I also confirm that I don't have theses warnings anymore with version 0.4. |
v7.0.1
v0.3.0
After switching Suricata to NFQueue runmode the thread metrics are no longer collected. There are warnings in the logs such as:
The thread metrics are available from Suricata however the thread names have prefix
W-NFQ#
:The exporter expects worker threads to have a prefix
W#
which is not the case when in nfqueue runmode:suricata_exporter/main.go
Line 756 in 998e7d9
The text was updated successfully, but these errors were encountered: