Graylog2 / Graylog2/graylog2-server
AMQP Input, log Properties and Headers from Raw AMQP Message
- Dominant language
- Java
- Stars
- 8.1k
- Forks
- 1.1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 217
Description
Some of the AMQP brokers log their events and traces in exchanges (e.g. Rabbitmq amq.rabbitmq.event).
These kind of messages are useful for auditing brokers and we would like to consume them with graylog input.
Consumed AMQP Messages come with empty body and useful information is stored in AMQP Headers and Properties.
## Expected Behavior
- AMQP input should accept empty messages (optional).
- AMQP input should parse headers into message (optional).
## Current Behavior
- AMQP input reject empty messages.
- AMQP input can't process message incoming AMQP Headers or Properties.
## Possible Solution
- implement optional acceptance for empty messages.
- implement logging of message Headers and Properties.
## Context
As a company we would like to log these kind of AMQP messages from broker without any kind of middle man between AMQP broker and Graylog.
Contributor guide
Assessment
This issue has not been assessed yet.