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

Semantic convention for location attributes #1228

Open
ssidhu-apm opened this issue Mar 9, 2022 · 1 comment
Open

Semantic convention for location attributes #1228

ssidhu-apm opened this issue Mar 9, 2022 · 1 comment
Assignees
Labels
area:new enhancement New feature or request

Comments

@ssidhu-apm
Copy link

What are you trying to achieve?

  • Latitude and Longitude can be identified from or assigned to a device, which is useful to capture in the telemetry context.
  • Backends can typically capture this lat/long and do a reverse geo IP lookup.

What did you expect to see?

  • A convention along the lines of location.lat, location.lon (other location attributes could be added in the future).
  • Agreement on a standard to follow for the lat / long values; such as wgs84

Additional context.

Add any other context about the problem here. If you followed an existing documentation, please share the link to it.

@arminru arminru added the enhancement New feature or request label Mar 9, 2022
@ssidhu-apm
Copy link
Author

Thanks @arminru - can we also add "area:client" tag here? (I do not seem to have the appropriate rights)

@lmolkova lmolkova transferred this issue from open-telemetry/opentelemetry-specification Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:new enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants