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
In our case the traces were arriving the service but with broken start times. Therefore the traces were not displayed in the Graph.
Environment details
Ruby version: 3.3.5
Gem name and version: google-cloud-trace 0.44.0
Rails version: >= v7.1.4
Steps to reproduce
Update to Rails >= v7.1.4
Code example
# example
Full backtrace
Traces are arriving the service but with broken start times so that the traces are not displayed in the Graph. However some traces can be found by directly searching with the trace id. That way i could see the broken start times.
The text was updated successfully, but these errors were encountered:
The google-cloud-trace gem's instrumentation features are not currently actively maintained. I recommend using OpenTelemetry instead for trace instrumentation.
@dazuma thanks for your answer. So basically i would need to implement the complete rails instrumentation part? I think the fix is really easy by just adding another condition to check for rails version >=7.1.4. Any chance to get this implemented or can i provide a PR to add it?
https://github.com/googleapis/google-cloud-ruby/blob/main/google-cloud-trace/lib/google/cloud/trace/notifications.rb#L121 This patch is not valid anymore for Rails version >= v7.1.4
See https://github.com/rails/rails/blob/v7.1.4/activesupport/lib/active_support/notifications/instrumenter.rb#L123
In our case the traces were arriving the service but with broken start times. Therefore the traces were not displayed in the Graph.
Environment details
Steps to reproduce
Update to Rails >= v7.1.4
Code example
# example
Full backtrace
Traces are arriving the service but with broken start times so that the traces are not displayed in the Graph. However some traces can be found by directly searching with the trace id. That way i could see the broken start times.
The text was updated successfully, but these errors were encountered: