Skip to content

A way to suppress redis.encode.start/end custom events #1586

@paveljakov

Description

@paveljakov

Our applications currently generates a lot of custom redis.encode.start and redis.encode.end events. Is there a way to suppress these custom events without disabling redis auto-collected telemetry?

We have tried to use new sampling override functionality, but it didn't work.

We have tried rules using db.statement and db.system attributes:

{
  "attributes": [
	{
	  "key": "db.statement",
	  "value": "INFO",
	  "matchType": "strict"
	},
	{
	  "key": "db.system",
	  "value": "redis",
	  "matchType": "strict"
	}
  ],
  "percentage": 0
}

Also we have tried using ai.operation.name attribute:

{
  "attributes": [
	{
	  "key": "ai.operation.name",
	  "value": "redis.encode.end",
	  "matchType": "strict"
	}
  ],
  "percentage": 0
}

Nothing helped, these events are still being sent to AI.

Also maybe there is a way to get complete list of Span attributes that can be used for sampling overrides (to filter out such dependencies like periodic clustered Quatz job selects, etc.)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions