Quite often, when there is a network disruption, nxlog (which is controlled
and started by graylog-collector) stops sending data.
We can detect this through Graylog Stream alerts.
Restarting nxlog on the remote nodes fixes the issues.
We achieve this by making a Collector configuration change, specifically
nxlog snippet part, we just add or remove a comment and save.
This triggers the collector to restart nxlog which resolves the issue.
We'd like to know if there is a simple API that can trigger similar effect.
I assume we can do this:
GET /plugins/org.graylog.plugins.collector/configurations,
extract the specific configuration id
call
GET /plugins/org.graylog.plugins.collector/configurations/{id}
with the above id and extract snipet and snipet_id
make changes to the snippet and call
PUT
/plugins/org.graylog.plugins.collector/configurations/{id}/snippets/{snippet_id}
Just wondering if there was an easier way to trigger collector restart.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/b601274e-be03-4c14-b11b-3f2f1b646463%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
