[issue-63] integration with logstash output plugin #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Lida He <[email protected]>
Signed-off-by: Lida He <[email protected]>
|
@hldnova due to issues we had in previous releases merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Lida He [email protected]
This PR addresses the issue #63. The example demonstrates the following pipleline
The Flink application reads apache access logs from a Pravega stream and once every 2 seconds counts the number of 500 responses in the last 30 seconds, and generates alert when the counts of 500 responses exceed 6. For more details, see https://github.com/hldnova/pravega-samples/tree/issue-63/flink-connector-examples/doc/high-count-alerter.
This is a replacement for #64.