Skip to content

Commit

Permalink
resolve workflow errors
Browse files Browse the repository at this point in the history
  • Loading branch information
@gunnalahema
gunnalahema committed Oct 28, 2024
1 parent 1304a20 commit 532a027
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Forwarding your Fluent Bit logs to New Relic will give you enhanced <InlinePopov

## Kubernetes installation[#Kubernetes-installation]

New Relic has a [Fluent Bit](https://fluentbit.io/) [output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward your logs to New Relic log management. This plugin is also provided in a standalone Docker image that can be installed in a Kubernetes cluster in the form of a DaemonSet, also known as the Kubernetes plugin.
New Relic has a [Fluent Bit](https://fluentbit.io/) [output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) to forward your logs to New Relic log management. You can install this plugin as a standalone Docker image in a Kubernetes cluster, where it functions as a DaemonSet, also known as the Kubernetes plugin.

You can install it in your cluster using our Helm chart in two ways.

Expand Down Expand Up @@ -53,12 +53,10 @@ Go here for [uninstallation instructions](/docs/kubernetes-pixie/kubernetes-inte

### Using Docker Image

we've published a container with the plugin installed. It serves as a base image to be used by our Kubernetes integration. If you have your own custom kubernetes integration, we recommend you use our [docker image](https://hub.docker.com/r/newrelic/newrelic-fluentbit-output) that comes with the [New Relic’s fluent bit output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) or use the docker image as a base image and layer your own custom configuration files.
we've published a container with the plugin installed , serves as a base image for our Kubernetes integration. If you have your own custom kubernetes integration, we recommend you use our [docker image](https://hub.docker.com/r/newrelic/newrelic-fluentbit-output) that comes with the [New Relic’s fluent bit output plugin](https://github.com/newrelic/newrelic-fluent-bit-output) . Alternatively, you can use the docker image as a base image and layer your own custom configuration files.

Check warning on line 56 in src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx

View workflow job for this annotation

GitHub Actions / vale-linter 

[vale] reported by reviewdog 🐶
[new-relic.ComplexWords] Consider using 'or' instead of 'Alternatively'.

Raw Output:
{"message": "[new-relic.ComplexWords] Consider using 'or' instead of 'Alternatively'.", "location": {"path": "src/content/docs/logs/forward-logs/fluent-bit-plugin-log-forwarding.mdx", "range": {"start": {"line": 56, "column": 382}}}, "severity": "INFO"}

## On-host installation[#On-host-installation]

we've published a container with the plugin installed. It serves as a base image to be used by our Kubernetes integration. We recommend you use this base image and layer your own custom configuration files.

## Install the Fluent Bit plugin [#fluentbit-plugin]

To install the Fluent Bit plugin:
Expand Down

0 comments on commit 532a027

Please sign in to comment.