-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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/honeycombmarker] Use the service.name
resource attribute to set dataset_slug
#29407
Comments
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
No response
Is your feature request related to a problem? Please describe.
Currently the honeycombmarker exporter allows you to specify exactly 1 dataset per marker. If you want to create a marker in different datasets based on similar conditions you have to keep recreating the marker.
Describe the solution you'd like
Allow the exporter to use
service.name
resource attribute to determine the dataset. With that feature in place a user could create a rule like to following:That rule could then create markers in specific datasets based on the service that produced the log. Without this feature, you'd have to do
Describe alternatives you've considered
No response
Additional context
We need to think about how this config option interacts with
dataset_slug
? If both are set, which takes precedence? Should only 1 be settable at a time?The text was updated successfully, but these errors were encountered: