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

[Lens] Lens telemetry errors on read-only users #75034

Closed
flash1293 opened this issue Aug 14, 2020 · 1 comment · Fixed by #91104
Closed

[Lens] Lens telemetry errors on read-only users #75034

flash1293 opened this issue Aug 14, 2020 · 1 comment · Fixed by #91104
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@flash1293
Copy link
Contributor

Kibana version: master

Describe the bug: When a user has only read rights, they don't have permissions to write to lens telemetry. As Lens tries to send telemetry events based on a timer, this causes a lot of errors failing with a 500 error code

Steps to reproduce:

  1. Go to demo.elastic.co
  2. Go to Lens
  3. Observe network tab

Context:

The telemetry plugin solves this by "probing" the request once and stopping to attempt requests if forbidden is returned:

if (errorCode === 'SavedObjectsClient/forbidden') {

We could adopt the same strategy and stop trying to push telemetry on certain status codes. Maybe implementing #48352 will fix this bug as well

@flash1293 flash1293 added bug Fixes for quality problems that affect the customer experience Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens labels Aug 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants