Skip to content

Log js client side errors in our server side logs #39

Closed
@vprithvi

Description

We don't track errors in the UI, and rely on users to contact us when things break.

Adding such logging would allow for better discovery of js errors.

Activity

yurishkuro

yurishkuro commented on Jul 11, 2017

@yurishkuro
Member

+1. I assume there are existing solutions for that though, rather than us building something custom.

vprithvi

vprithvi commented on Jul 11, 2017

@vprithvi
ContributorAuthor

Yes, tools like Sentry, Usersnap, etc allow for this.
Ideally, we'd add an extension point that people can plug some solutions into.

yurishkuro

yurishkuro commented on Aug 10, 2017

@yurishkuro
Member

Google Analytics may support that

tiffon

tiffon commented on Oct 30, 2017

@tiffon
Member
ghost assigned on Feb 12, 2018
ghost removed on Feb 12, 2018
ghost removed on Feb 27, 2018
Dieterbe

Dieterbe commented on May 3, 2018

@Dieterbe

do i understand this right that people who have deployed jaeger in their environment will automatically have their jaegers send errors to a GA account owned by the jaeger team?
is there any chance confidential information might leak? e.g. from data in logs or spans. this is a bit concerning to me.
can GA be made opt-in ? (off by default?)

yurishkuro

yurishkuro commented on May 3, 2018

@yurishkuro
Member

it is opt-in, there is no default GA app id in the code.

Dieterbe

Dieterbe commented on May 3, 2018

@Dieterbe

Great thanks Yuri .

1 remaining item

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Log js client side errors in our server side logs · Issue #39 · jaegertracing/jaeger-ui