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

[exporter/loki] Set a default user agent #27207

Closed
jpkrohling opened this issue Sep 26, 2023 · 6 comments
Closed

[exporter/loki] Set a default user agent #27207

jpkrohling opened this issue Sep 26, 2023 · 6 comments
Assignees
Labels

Comments

@jpkrohling
Copy link
Member

Component(s)

exporter/loki

Is your feature request related to a problem? Please describe.

The Loki team at Grafana Labs was trying to identify the source of an anomaly on their backend and found out that it was related to how a specific tenant uses the Collector. It would have had been easier to identify this if we had a specific user-agent for requests going out from the Collector.

Therefore, this request is to set a specific user-agent for outgoing requests from the Loki exporter.

Describe the solution you'd like

The Loki exporter could set the user-agent on the HTTP client it uses to make the remote call.

Describe alternatives you've considered

No response

Additional context

No response

@jpkrohling jpkrohling added enhancement New feature or request needs triage New item requiring triage and removed needs triage New item requiring triage labels Sep 26, 2023
@jpkrohling
Copy link
Member Author

@mar4uk, would you be interested in implementing this?

@crobert-1 crobert-1 added the exporter/loki Loki Exporter label Sep 26, 2023
@github-actions
Copy link
Contributor

Pinging code owners for exporter/loki: @gramidt @gouthamve @jpkrohling @mar4uk. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@antonjim-te
Copy link

This issue can be also beneficial to solve it in the OTLP HTTP exporter open-telemetry/opentelemetry-collector#8560
Thanks

Copy link
Contributor

github-actions bot commented Dec 4, 2023

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Dec 4, 2023
@jpkrohling jpkrohling removed the Stale label Dec 5, 2023
@jpkrohling jpkrohling self-assigned this Dec 5, 2023
Copy link
Contributor

github-actions bot commented Feb 5, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

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

github-actions bot commented Apr 6, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants