Hello Chris,
in our current development branch we have implemented modular alarm callbacks.
This means it is possible to define a chain of actions which are being taken
when an alert is generated. One of those predefined pluggable modules is an
HTTP callback which calls a certain URL and
Hello,
I'm having troubles to set a working regex to match something like this :
GET /some/path USERAGENT
If I try :
match regular expression
and :
GET /some/path
the rule matches my test message but it's not specific enough
if I try :
GET /some/path USERAGENT
the rule does not work
Hi Stephen,
I do hop I'll get you right.
Take a look at nxlog, you can send with it in a CSV format, and give names
to your fields to.
See: http://nxlog.org/nxlog-docs/en/nxlog-reference-manual.html#xm_xml
*Example 6.12. Parsing a CSV file and sending it to Graylog2 in GELF*
On Thursday,
Looks like nxlog will suit my purpose just fine.
Thanks for the help!
On Friday, June 6, 2014 6:06:02 AM UTC-4, Arie wrote:
Hi Stephen,
I do hop I'll get you right.
Take a look at nxlog, you can send with it in a CSV format, and give names
to your fields to.
See:
Hi Daniel,
I've published an equal post about this issue and after no answer, I've
find it out by myself:
1- edit your graylog2.conf and modify both rest_listen_uri and
rest_transport_uri to
http://IP_address_of_your_Graylog2_server:12900/ instead of
http://127.0.0.1:12900; (ex:
