Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FluentD not sending application logs to open telemetry collector #1423

Open
saritatewari4 opened this issue Mar 31, 2023 · 3 comments
Open

Comments

@saritatewari4
Copy link

Hello, I am trying to send all application logs of each pods to open telemetry collector . What configuration I have to use for that.

Currently I am using this:
<match *.*> @type forward <server> host <OTEL_HOST> port <OTEL_PORT> </server> </match>

This configuration is forwarding fluentD pods logs to open telemetry, but I need to send application logs running on EKS, which are forwarded to cloud watch too.

I am using fluentd-kubernetes-daemonset:v1.7.3-debian-cloudwatch-1.0 this image currently.

@Hronom
Copy link

Hronom commented Jun 6, 2023

@saritatewari4 for me this works:

Stock config from here https://artifacthub.io/packages/helm/fluent/fluentd

Modified 04_outputs.conf section:

      <label @OUTPUT>
        <match **>
          @type forward
          send_timeout 60s
          recover_wait 10s
          hard_timeout 60s
    
          <server>
            name opentelemetry-collector
            host opentelemetry-collector.opentelemetry.svc.cluster.local
            port 8006
            weight 100
          </server>
        </match>
      </label>

Then using helm chart opentelemetry-collector https://artifacthub.io/packages/helm/opentelemetry-helm/opentelemetry-collector

I put this in values.yaml:

  ports:
    fluentforward:
      enabled: true
      containerPort: 8006
      servicePort: 8006
      hostPort: 8006
      protocol: TCP

and

  config:
    receivers:
      jaeger: null
      fluentforward:
        endpoint: ${env:MY_POD_IP}:8006

Hope it get you some inspiration

@github-actions
Copy link

github-actions bot commented Sep 4, 2023

This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days

@github-actions github-actions bot added the stale label Sep 4, 2023
@ashie ashie removed the stale label Sep 27, 2023
Copy link

This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants