open-telemetry / open-telemetry/semantic-conventions
Add specification for ASN/Autonomous System Number
@ajimenez1503 is already working on this.
Since Sep 14, 2026.
- Dominant language
- Jinja
- Stars
- 651
- Forks
- 394
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 38
Description
Area(s)
area:network
Is your change request related to a problem? Please describe.
Including the ASN in OpenTelemetry tracing data is helpful when trying to analyze where an attack is coming from. Often attackers use multiple IPs that come from the same ASN. Also, it can be helpful for diagnosing if an issue is specific to one network, or many networks.
Describe the solution you'd like
Add a standard attribute for specifying an ASN, and possibly the ASN name. E.g.
network.as.number
network.as.organization.name
(Borrowing heavily from https://www.elastic.co/guide/en/ecs/current/ecs-as.html).
Describe alternatives you've considered
I can just add this myself, but it seems like a common use.
Additional context
Perhaps this should be available for many different parts of the schema that deal with IP addresses, e.g. client.as.number, destination.as.number.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.