Skip to content

Suppress devsandbox server side telemetry #837

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

Closed
kim-tsao opened this issue May 3, 2022 · 0 comments
Closed

Suppress devsandbox server side telemetry #837

kim-tsao opened this issue May 3, 2022 · 0 comments
Assignees
Labels
area/telemetry telemetry related issues kind/bug Something isn't working

Comments

@kim-tsao
Copy link
Contributor

kim-tsao commented May 3, 2022

/kind bug

Which area this bug is related to?

/area telemetry

What versions of software are you using?

N/A

Bug Summary

Describe the bug:

We are collecting a lot of vague data. Events like list devfile are coming from devsandbox. Earlier attempts to filter these events out only considered the client id but it seems like the way these events are set up, it's the id that is set to the openshift-console identfier not the client-property which is still set to the old devfile-registry value.

To Reproduce:

Login to our segment and woopra account to see the data

Expected behavior

Need to filter out to reduce the noise in our data

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable.

segment event payloads look like this:

client.Track(&analytics.Track{
  UserId: "openshift-console",
  Event: "list devfile",
  Properties: map[string]interface{}{
    "client": "devfile-registry",
    "registry": "devfile-community-registry",
    "type": "sample",
  },
})

This is causing spikes in our telemetry data

Additional context

Any workaround?

Suggestion on how to fix the bug

@openshift-ci openshift-ci bot added the kind/bug Something isn't working label May 3, 2022
@kim-tsao kim-tsao self-assigned this May 3, 2022
@kim-tsao kim-tsao added the area/telemetry telemetry related issues label May 3, 2022
@kim-tsao kim-tsao closed this as completed May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/telemetry telemetry related issues kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant