feat(otel): propose browser behavioral analytics semantic conventions
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation, observability
Research direction
Start by reviewing #140 for the OTLP exporter mapping and #141 for the demo's community validation. Use those results to draft the OTEP and submit it to the opentelemetry-specification repository; done means the proposal has been submitted and iterated based on SIG feedback.
Written by the indexing model from the issue text.
Description
Summary
Propose OTel semantic conventions for browser behavioral analytics to the OpenTelemetry specification.
Proposed Conventions
| Attribute | Type | Description |
|---|---|---|
browser.dom.target |
string | CSS selector of interaction target |
browser.dom.path |
string[] | DOM path from target to root |
browser.event.type |
string | DOM event type (click, keydown, etc.) |
browser.session.id |
string | Behavioral session identifier |
browser.viewport.width |
int | Viewport width in pixels |
browser.viewport.height |
int | Viewport height in pixels |
browser.pointer.x |
double | Pointer X coordinate |
browser.pointer.y |
double | Pointer Y coordinate |
Process
- Validate mapping via Flagon's OTLP exporter (#140)
- Draft OTEP (OpenTelemetry Enhancement Proposal)
- Submit to opentelemetry-specification repo
- Iterate based on SIG feedback
Depends On
- #140 (OTLP exporter — proves mapping works in practice)
- Community validation via demo (#141)
- Dominant language
- Jupyter Notebook
- Stars
- 30
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from apache/flagon
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
process
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement experimental
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
enhancement Userale
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
enhancement Userale
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·