build: remove filebeat from the TeamCity agents #61087
Draft
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
|
This change is |
Before: we were using an ELK stack instance for monitoring TeamCity logs. Why: we aren't using the ELK stack for monitoring any more. Now: The packer configuration has been updated so filebeat is no longer installed. Release justification: non-production code change Release note: None
jlinder
force-pushed
the
jhl/remove-filebeat-from-tc-agents
branch
from
ddc4ce3
to
02188ee
Compare
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.
Before: we were using an ELK stack instance for monitoring TeamCity logs.
Why: we aren't using the ELK stack for monitoring any more.
Now: The packer configuration has been updated so filebeat is no longer
installed.
Release justification: non-production code change
Release note: None