Detect external services using semconv attributes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
A lot of times the user of an external service does not have control over whether the service generates server spans, but those would still count as a service in the system. This causes the service graph to not contain any external services that are called in the lifetime of a trace.
This can be solved by looking for client spans with standard semconv attributes (most notably service.peer.name). A more comprehensive list can be found here. It would also be useful to extract out common semconv attributes into materialized columns for performance.
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.
Research direction
Start by locating the service-graph processing and trace span storage paths, then review the linked semconv attribute list, especially service.peer.name. Done means client spans with recognized external-service attributes appear in the service graph and common attributes are available as materialized columns for performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, typescript
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100