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
I have been using the dd.grpc.server.error.statuses system property to configure how gRPC server spans are marked as errored.
In version v1.43.0, this property worked as expected. However, after upgrading to v1.44.1, it no longer seems to take effect.
Is this a bug, or do I need to adjust some configuration values for the new version?
The text was updated successfully, but these errors were encountered:
socar-brownie
changed the title
dd.grpc.server.error.statuses system property not working in v1.44.1 (worked fine in v1.43.0)dd.grpc.server.error.statuses system property not working in v1.44.1 (worked fine in v1.43.0)
Dec 19, 2024
Hello, thanks for having opened This github issue. The changes in behaviour might be due to this PR. In particular that PR fixed a bug concerning manual error flag overrrides in grpc. In fact if the span was manually marked as errored, then the dd.grpc.server.error.statuses rule might have them changed.
The manual setting should always take precedence hence we used error priorities to avoid this from happening.
Are you doing any kind of manual tracing or manually setting error or tags to those grpc spans?
If not you should not be impacted. It would be useful to know more about the spans you're creating and how the code looks like. I can also suggest to reach the helpdesk and open a case asking to escalate that issue.
Thanks
I have been using the
dd.grpc.server.error.statuses
system property to configure how gRPC server spans are marked as errored.In version
v1.43.0
, this property worked as expected. However, after upgrading tov1.44.1
, it no longer seems to take effect.Is this a bug, or do I need to adjust some configuration values for the new version?
The text was updated successfully, but these errors were encountered: