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.

Sign up for GitHub

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

Jump to bottom

Have consistent naming for Google Cloud services #1485

Closed
rakyll opened this issue Mar 1, 2021 · 0 comments · Fixed by #1496
Closed

Have consistent naming for Google Cloud services #1485

rakyll opened this issue Mar 1, 2021 · 0 comments · Fixed by #1496
Labels
area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory

Comments

@rakyll
Copy link
Contributor

rakyll commented Mar 1, 2021

The cloud semantic conventions specify a number of Google Cloud services https://github.com/open-telemetry/opentelemetry-specification/blob/main/semantic_conventions/resource/cloud.yaml#L74 but they are not consistently named.

For example, 'gcp_gke' uses a short name for the service whereas 'gcp_compute_engine' and 'gcp_cloud_functions' uses the long name. Either use short names everywhere or switch to the long names for all.

cc @jsuereth
@rakyll rakyll added the spec:miscellaneous For issues that don't match any other spec label label Mar 1, 2021
@arminru arminru added area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory and removed spec:miscellaneous For issues that don't match any other spec label labels Mar 1, 2021
@rakyll rakyll mentioned this issue Mar 3, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:semantic-conventions Related to semantic conventions spec:resource Related to the specification/resource directory
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Have consistent naming for Google Cloud services
2 participants
@rakyll @arminru