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

Added mobile carrier info related semantic conventions to span spec #1669

Closed
wants to merge 3 commits into from

Conversation

bryce-b
Copy link
Member

@bryce-b bryce-b commented May 4, 2021

Fixes #
Adds semantic conventions defining mobile carrier data defined in #1647

Changes

  • adds net.host.carrier.*
  • adds net.host.connection_type

Related issues #
#1647 : Add semantic convention for describing network connectivity conditions

Comment on lines +45 to +48
| `net.host.carrier.name` | string | Name of the mobile carrier. | `sprint` | No |
| `net.host.carrier.mcc` | string | [Mobile country code](https://en.wikipedia.org/wiki/Mobile_country_code) | `310` | No |
| `net.host.carrier.mnc` | string | [Mobile network code](https://en.wikipedia.org/wiki/Mobile_country_code) | `001` | No |
| `net.host.carrier.icc` | string | [ISO country code (two character)](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) | `DE` | No |
Copy link
Contributor

Choose a reason for hiding this comment

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

These are not "general network connection attributes", but are very specific to mobile clients.

Copy link
Member

Choose a reason for hiding this comment

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

I think the "general" in the title is more about "low-level networking" as opposed to "protocol-specific attributes".

In any case, I think if we make them span attributes (which seems to be the best currently available option) then putting them under net.host is sensible.

Also net.host.connection_type would make sense for other clients as well.

Copy link
Member Author

Choose a reason for hiding this comment

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

@iNikem do you think these should be placed in a different semantic convention document, specifically for mobile?

Copy link
Member

@Oberon00 Oberon00 left a comment

Choose a reason for hiding this comment

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

Semantic conventions are mostly edited in the YAML sources from which the markdown is then generated. See https://github.com/open-telemetry/opentelemetry-specification/tree/main/semantic_conventions

@arminru arminru added area:semantic-conventions Related to semantic conventions spec:trace Related to the specification/trace directory labels May 6, 2021
@github-actions
Copy link

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 May 14, 2021
@carlosalberto
Copy link
Contributor

Hey @bryce-b

Want to iterate over the comments? I'd like to see this up to date and hopefully merged ;)

@github-actions github-actions bot removed the Stale label May 21, 2021
@carlosalberto
Copy link
Contributor

Ping @bryce-b

@jmacd
Copy link
Contributor

jmacd commented Jun 1, 2021

Please re-open if you would like to resume this work.

@jmacd jmacd closed this Jun 1, 2021
@bryce-b bryce-b mentioned this pull request Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:semantic-conventions Related to semantic conventions spec:trace Related to the specification/trace directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants