Closed
Conversation
Member
|
Thanks for this. Do you want to keep it around to update later or want to close it for now? |
Contributor
Author
|
I think I'd keep it open as a reference until we have proper Vector support for at least one operator. |
1 task
This was referenced Oct 25, 2022
Contributor
|
#588 was merged based off of this PR, I'm closing this |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
This is a pretty dirty proof of concept for using Vector to parse and forward product logs into OpenSearch.
Review Checklist
Once the review is done, comment
bors r+(orbors merge) to merge. Further information