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.)?
Our applications currently generates a lot of custom
redis.encode.startandredis.encode.endevents. 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.statementanddb.systemattributes:{ "attributes": [ { "key": "db.statement", "value": "INFO", "matchType": "strict" }, { "key": "db.system", "value": "redis", "matchType": "strict" } ], "percentage": 0 }Also we have tried using
ai.operation.nameattribute:{ "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.)?