You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
/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 theid
that is set to theopenshift-console
identfier not theclient-property
which is still set to the olddevfile-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:
This is causing spikes in our telemetry data
Additional context
Any workaround?
Suggestion on how to fix the bug
The text was updated successfully, but these errors were encountered: