[Do not merge]Feat(FB monitoring on k8): Updating the log collector lifecycle document with monitoring tiers #20723
Conversation
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
…ifecycle document with monitoring tiers Updated the Log collector management lifecycle document as following: - Modularised the topic - Updated it with the monitoring tier details - Included troubleshooting - Enhanced monitoring details
sujitnewrelic
added
content
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @sujitnewrelic 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
| * [Remote configuration via Fleet Control](#modify-and-deploy-config-via-fleet-control) | ||
|
|
||
| ### Modify configuration in Kubernetes environment [#modify-in-kubernetes-environment] | ||
| If you are not using the New Relic Control solution, you can modify the Fluent Bit configuration directly in your Kubernetes environment. Locate the `values.yaml` file and set the `fluentBitMetrics` field to `advanced`. Then, apply the changes to your Kubernetes cluster using the following command: |
There was a problem hiding this comment.
Change fluentBitMetrics to fluentbit.fluentBitMetrics
| If you are not using the New Relic Control solution, you can modify the Fluent Bit configuration directly in your Kubernetes environment. Locate the `values.yaml` file and set the `fluentBitMetrics` field to `advanced`. Then, apply the changes to your Kubernetes cluster using the following command: | ||
|
|
||
| ```shell | ||
| helm upgrade RELEASE_NAME newrelic/nri-bundle \ |
There was a problem hiding this comment.
I feel this is redundant , not required, we can just put upgrade the helm chart
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.
Updated the Log collector management lifecycle document as following: