streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STREAMS-283) Logstash-friendly monitoring
Date Wed, 18 Feb 2015 20:04:11 GMT


ASF GitHub Bot commented on STREAMS-283:

GitHub user robdouglas opened a pull request:

    STREAMS-283 | Ensuring that logic in BroadcastMonitorThread actually cre...

    ...ates a Message Persister

You can merge this pull request into a Git repository by running:

    $ git pull STREAMS-283

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #190
commit ef2b167f28fb9815cbd2e51d4f837ef6f6386bcf
Author: Robert Douglas <>
Date:   2015-02-18T20:02:22Z

    STREAMS-283 | Ensuring that logic in BroadcastMonitorThread actually creates a Message


> Logstash-friendly monitoring
> ----------------------------
>                 Key: STREAMS-283
>                 URL:
>             Project: Streams
>          Issue Type: New Feature
>            Reporter: Steve Blackmon
> streams-monitoring is able to package stream execution statistics and post a JSON to
a dedicated end-point, but seems to have trouble when the server on the other end does not
supply a response.  Since this is how the logstash tcp input works, investigate and implement
a more logstash-friendly MessagePersister - one that does not require any endpoint between
the stream and the logstash collector.

This message was sent by Atlassian JIRA

View raw message