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

Tag/match not working for OpenTelemetry input #7939

Closed
carlosli888 opened this issue Sep 18, 2023 · 3 comments
Closed

Tag/match not working for OpenTelemetry input #7939

carlosli888 opened this issue Sep 18, 2023 · 3 comments

Comments

@carlosli888
Copy link

Bug Report

Describe the bug
If I want to output logs received via OpenTelemetry plugin, I am forced to use * as the Match string. If I use anything else, logs are not sent to the output plugins.

To Reproduce

  • Steps to reproduce the problem:
  1. Start an instance of FluentBit as a server.
[INPUT]
    Name                opentelemetry
    Listen              0.0.0.0
    Port                4319
    Tag                 otel
[OUTPUT]
    Name                stdout
    Match               otel
  1. Use another instance of FluentBit to act as a log generator.
[INPUT]
    Name                dummy 
[OUTPUT]
    Name                opentelemetry
    Match               *
    Host                127.0.0.1
    Port                4319
  1. If we examine the output from the FluentBit acting as a server, nothing is shown. However, if we change the Match string of the Stdout plugin to *, then it works.

Expected behavior
I expect routing to work the same way for all plugins except Forward as described by [https://docs.fluentbit.io/manual/concepts/key-concepts#tag]. Alternatively, if the Match string needs to match the original source, this is clearly documented and it works. Currently, adding the otel tag to the Dummy input makes no difference.

Screenshots
image

Your Environment

  • Version used: 2.1.8
  • Configuration: See reproduction steps above
  • Environment name and version (e.g. Kubernetes? What version?): See OS below
  • Server type and version:
  • Operating System and version: Windows 10
  • Filters and plugins: See reproduction steps above

Additional context
This was first discovered while troubleshooting why logs were not being sent to Loki.

@nokute78
Copy link
Collaborator

nokute78 commented Nov 4, 2023

Tag seems to be composed by uri.
e.g. v1_metrics from /v1/metrics

I sent a patch to create a tag from property tag.
#8134

Copy link
Contributor

github-actions bot commented Feb 3, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Feb 3, 2024
Copy link
Contributor

github-actions bot commented Feb 9, 2024

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2024
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

2 participants