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

Dynamic selection of log_group_name and log_stream_name in aws cloudwatch logs exporter #14554

Closed
mathiaz opened this issue Sep 27, 2022 · 4 comments
Labels

Comments

@mathiaz
Copy link

mathiaz commented Sep 27, 2022

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

We are running the opentelemetry collector to send logs from our edge systems to a central opentelemetry gateway service. From the gateway we'd like to write logs to cloudwatch logs in different log groups and streams based on log resources.

Describe the solution you'd like

We'd like to be able to set the log_group_name and log_stream_name dynamically based on fields from the log event:

  awscloudwatchlogs:
    log_group_name: "{log_file_name}"
    log_stream_name: "{resource.hostname}"

Describe alternatives you've considered

No response

Additional context

No response

@mathiaz mathiaz added enhancement New feature or request needs triage New item requiring triage labels Sep 27, 2022
@evan-bradley evan-bradley added priority:p2 Medium exporter/awscloudwatchlogs awscloudwatchlogs exporter and removed needs triage New item requiring triage labels Sep 27, 2022
@github-actions
Copy link
Contributor

Pinging code owners: @boostchicken. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions
Copy link
Contributor

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 Nov 28, 2022
@github-actions
Copy link
Contributor

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 May 26, 2023
@sorobon
Copy link

sorobon commented Jan 23, 2024

I'm interested :)

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