-
Notifications
You must be signed in to change notification settings - Fork 888
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
add semantic conventions for heroku #3075
Conversation
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
I just noticed, shouldn't these new conventions be inside the cloud provider's folder? |
I don’t know. Please tell me where this should go. Thanks! |
I'm not sure as well, but I'd think Heroku is a cloud provider, so would make sense to be in that folder? Not sure if the others think the same. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
specification/resource/semantic_conventions/cloud_provider/heroku.md
Outdated
Show resolved
Hide resolved
/label -stale |
specification/resource/semantic_conventions/cloud_provider/heroku.md
Outdated
Show resolved
Hide resolved
…oku.md Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
specification/resource/semantic_conventions/cloud_provider/heroku.md
Outdated
Show resolved
Hide resolved
specification/resource/semantic_conventions/cloud_provider/heroku.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
Fixes #3032
Changes
Adds a list of resource attributes characterizing a Heroku dyno environment, taken after https://devcenter.heroku.com/articles/dyno-metadata