Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toggle to remove errors from traces sent to Engine Servers #1613

Closed
evans opened this issue Sep 4, 2018 · 1 comment · Fixed by #1615
Closed

Toggle to remove errors from traces sent to Engine Servers #1613

evans opened this issue Sep 4, 2018 · 1 comment · Fixed by #1615
Labels
⛲️ feature New addition or enhancement to existing solutions

Comments

@evans
Copy link
Contributor

evans commented Sep 4, 2018

We need the ability to prevent error messages and locations from being sent to the Engine Servers.

This is a feature in the engine proxy, so I would consider the lack of toggle to be a regression.

The documentation for reportErrorFunction doesn't quite seem clear due to the overloading of error, representing reported errors in traces and those that occur when sending a trace to the engine backend.

@ghost ghost added the ⛲️ feature New addition or enhancement to existing solutions label Sep 4, 2018
@daniman
Copy link
Member

daniman commented Sep 4, 2018

Please update this article in the Engine docs when disabling error reporting becomes available: https://www.apollographql.com/docs/engine/data-privacy.html.

martijnwalraven pushed a commit that referenced this issue Sep 5, 2018
Fixes #1613.

We always send traces that includes an error node if the trace has an
error. In the case that sending errors is disabled, we replace the
message and remove the location.

Note that the Engine proxy strips all error information from the traces
with noErrorTraces set. To get errors to show up in the ui, the proxy
sends error counts inside of the aggregated stats reports. To get
similar behavior inside of the apollo server metrics reporting, we
always send a trace and mask out the PII.
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
⛲️ feature New addition or enhancement to existing solutions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants