This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Improve client error tracking of the Sourcegraph application: Tracking issue #26570
Closed
16 of 28 tasks
Labels
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
sentry
tracking
Comments
valerybugakov
added
tracking
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
sentry
labels
Oct 25, 2021
Heads up @umpox @valerybugakov @5h1rU @pdubroy @taylorsperry - the "team/frontend-platform" label was applied to this issue. |
valerybugakov
removed
the
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
label
Oct 25, 2021
pdubroy
added
the
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
label
Nov 15, 2021
Heads up @pdubroy - the "team/frontend-platform" label was applied to this issue. |
valerybugakov
added
tracking
and removed
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
tracking
labels
Nov 16, 2021
bobheadxi
added
dx
Issues and PRs related to developer experience concerns
observability
and removed
dx
Issues and PRs related to developer experience concerns
observability
labels
Dec 1, 2021
1 task
taylorsperry
added
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
and removed
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
labels
Mar 28, 2022
taylorsperry
changed the title
Sentry resurrection: Tracking issue
Improve runtime error monitoring with Sentry: Tracking issue
Mar 28, 2022
taylorsperry
added
the
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
label
Mar 28, 2022
taylorsperry
changed the title
Improve runtime error monitoring with Sentry: Tracking issue
Sentry resurrection: Tracking issue
Mar 28, 2022
taylorsperry
changed the title
Sentry resurrection: Tracking issue
Improve runtime error monitoring with Sentry: Tracking issue
Mar 28, 2022
taylorsperry
removed
the
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
label
Mar 28, 2022
taylorsperry
changed the title
Improve runtime error monitoring with Sentry: Tracking issue
Improve frontend runtime error monitoring with Sentry: Tracking issue
Mar 30, 2022
17 tasks
valerybugakov
changed the title
Improve frontend runtime error monitoring with Sentry: Tracking issue
Improve client observability: Tracking issue
Apr 5, 2022
taylorsperry
changed the title
Improve client observability: Tracking issue
Improve client-side observability on Sourcegraph Cloud: Tracking issue
Apr 6, 2022
taylorsperry
changed the title
Improve client-side observability on Sourcegraph Cloud: Tracking issue
Improve client-side observability of the Sourcegraph application: Tracking issue
May 27, 2022
12 tasks
26 tasks
taylorsperry
added
the
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
label
Jun 29, 2022
Heads up @taylorsperry @jasongornall - the "team/frontend-platform" label was applied to this issue. |
We are sunsetting all usage of Datadog https://github.com/sourcegraph/sourcegraph/issues/27386 |
valerybugakov
changed the title
Improve client-side observability of the Sourcegraph application: Tracking issue
Improve client error tracking of the Sourcegraph application: Tracking issue
Jul 22, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
frontend-platform
Issues related to our frontend platform, owned collectively by our frontend crew.
sentry
tracking
Problem to solve
Today, we lack processes around client-side error monitoring, error reporting, and prioritizing and fixing runtime errors. Consequently, it can be difficult for Sourcegraph engineers to see, understand, and fix problems in the Sourcegraph application, which has a negative impact on engineering teams' effectiveness and, ultimately, on our customers. For the observability of on-prem instances, distributed traces, and other more advanced observability efforts, we'll follow the lead of the DevX team.
Measure of success
Solution summary
What we're not doing right now:
src debug
can do today in regard to traces, and see if it can be used to export client log events as wellArtifacts:
What specific customers are we iterating on the problem and solution with?
Internal Sourcegraph developers
Impact on use cases
Delivery plan
Tracked issues
@unassigned
Completed
@plibither8: 3.00d
Completed
@valerybugakov
Completed
The text was updated successfully, but these errors were encountered: