Documentation has missing Information about linking sentry errors in openReplay sessions
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- documentation
Research direction
Open the Sentry integration documentation at the linked page and review section 4, “Attach openreplaySessionURL.” Compare both examples with the requested session URL tag and verify that the finished documentation explains linking from Sentry to the OpenReplay session video as well as the reverse direction.
Written by the indexing model from the issue text.
Description
I have noticed, that the documentation is missing one line in the examples of linking Sentry issues in the openReplay Session, to show the directly in the OpenReplay video:
const tracker = new OpenReplay({
projectKey: window.OPENREPLAY_PROJECT_KEY,
onStart: ({ sessionToken, sessionID }) => {
// This is to link from OpenReplay -> Sentry
Sentry.setTag("openReplaySessionToken", sessionToken);
// This is to link from Sentry -> OpenReplay (requires tracker v3.6.0+)
Sentry.setTag(
"openReplaySessionURL",
tracker.getSessionURL();
);
},
});
Both your examples will create a link from Sentry to OpenReplay.
- Dominant language
- MDX
- Stars
- 16
- Forks
- 23
- Avg merge
- 39m
- Merged PRs (30d)
- 3
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 openreplay/documentation
-
Difficulty 2/5 Half a day Newbie friendliness 68/100
openreplay/documentation#231 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
openreplay/documentation#254 ·
-
Zendesk Integration Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
openreplay/documentation#167 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openreplay/documentation#120 · 1 comment ·
-
Difficulty 2/5 Half a day Newbie friendliness 48/100
openreplay/documentation#65 · 2 reactions ·
All issues in openreplay/documentation
Similar issues
-
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 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100