elastic/logstash

Sensu codec for RabbitMQ output

Open

#2,124 opened on Nov 24, 2014

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Ruby (3,496 forks)batch import
help wantednew plugin

Repository metrics

Stars
 (14,197 stars)
PR merge metrics
 (Avg merge 4d 19h) (50 merged PRs in 30d)

Description

Originally reported by Brian Preston at https://logstash.jira.com/browse/LOGSTASH-2116

I'm trying to get matching ingested logs to fire a sensu alert. One way I see to do this is have logstash output matching logs into rabbitmq, using the output already written. However the message would need to be formatted into the format sensu uses, which implies a codec.

History: The google group "logstash-users" mentioned a need for this in Nov 2013, but it looks like no one has implemented it yet.

The original thread: https://groups.google.com/forum/#!searchin/logstash-users/sensu/logstash-users/pZkBl7XoTEg/pfCiErPxRI4J

It probably would not need specific codec, if the existing rabbitmq plugin supported customizing the payload.

Contributor guide

Research direction
Examine existing RabbitMQ output plugin and codec structure in Logstash. Understand the Sensu JSON format (check, result). Implement a codec that transforms Logstash events into Sensu compatible JSON and ensure it can be used with the RabbitMQ output.
Tech stack
ruby
Domain
backendapidata
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RubyLogstash pluginsRabbitMQSensu
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50