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

Contributing Geo fields from ECS #2835

Closed
wants to merge 1 commit into from

Conversation

AlexanderWert
Copy link
Member

Fixes open-telemetry/semantic-conventions#1033

Changes

Adds geo namespace from the Elastic Common Schema to the resource attributes to allow filtering and grouping of observability data by geo location.

Related OTEP: open-telemetry/oteps#199

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Sep 26, 2022

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: AlexanderWert / name: Alexander Wert (b0fbc25)

| `NA` | North America |
| `OC` | Oceania |
| `SA` | South America |
<!-- endsemconv -->
Copy link
Contributor

@scheler scheler Sep 26, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. For mobile devices, the geo attributes will be changing as the user moves around and they cannot be updated on the Resource currently. This PR will have to wait until Ephemeral Resource Attributes oteps#208 is resolved or there's another mechanism introduced that allows changing attributes on a Resource.
  2. For apps running in data centers, I believe the customers will have to run a Geo mapping service to map the IP to the geo coordinates. If for some reason this service is unavailable, there should be a way to pass the original source IP in the Resource so that the telemetry backends can use that for the geo mapping. Can you include support for that in this PR or add a reference to it if it's already there?

@reyang reyang requested review from jsuereth and reyang September 27, 2022 18:40
@github-actions
Copy link

github-actions bot commented Oct 6, 2022

This PR was marked stale due to lack of activity. It will be closed in 7 days.

@github-actions github-actions bot added the Stale label Oct 6, 2022
@github-actions
Copy link

Closed as inactive. Feel free to reopen if this PR is still being worked on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Geo fields from Elastic Common Schema
2 participants