This repository has been archived by the owner on Jun 30, 2020. It is now read-only.
Add ability for kubernetes pods to exclude themselves and suggest parser #19
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.
The fluentbit kubernetes
[FILTER]
block has two options which we will find useful - presumably other clients will as well. The first isK8S-Logging.Exclude
. It allows developers to exclude certain pods from logging by applying a pod annotationfluentbit.io/exclude: "true"
. This gives the ability to exclude apps that have overly-chatty or sensitive logs they don't wish to send to New Relic (currently a soft blocker for us).The next option,
K8S-Logging.Parser
, allows developers to designate a fluentbit parser for their specific app.Source:
https://github.com/fluent/fluent-bit-docs/blob/master/filter/kubernetes.md