Skip to content

Suppress devsandbox server side telemetry #837

Closed
@kim-tsao

Description

@kim-tsao

/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

Metadata

Metadata

Assignees

Labels

area/telemetrytelemetry related issueskind/bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions