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
Heads up @umpox @valerybugakov @5h1rU @pdubroy @taylorsperry - the "team/frontend-platform" label was applied to this issue. |
Heads up @pdubroy - the "team/frontend-platform" label was applied to this issue. |
1 task
17 tasks
12 tasks
26 tasks
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 |
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: