Conversation
a9c761d to
452041f
Compare
4e2c839 to
9f8e4f8
Compare
452041f to
5f2a11d
Compare
This will auto-hook into Rails and other libraries to produce traces. No explicit trace spans are created yet, only automatic instrumentation. The only explicit configuration is to avoid tracing the /up endpoint used for health checks. This prevents a large number of unhelpful traces from being created. All other configuration is provided through environment variables, specified in `forms-deploy`. We also disable logging for Rake tasks to avoid cluttering output when running tasks like database migrations. Finally, OpenTelemetry is only enabled if the `ENABLE_OTEL` environment variable is set to "true". This allows us to control whether tracing is active without changing the code. Again, this is configured in `forms-deploy` when deploying to different environments.
5f2a11d to
319e15c
Compare
| @@ -0,0 +1,117 @@ | |||
| class TelemetryService | |||
There was a problem hiding this comment.
Could we use the Rails.event framework? It's pretty new, so we might still have to roll-our-own, but it would at least be consistent with the future direction and maybe in future it would be supported out of the box by OpenTelemetry.
9f8e4f8 to
5bf4484
Compare
5bf4484 to
c5d6900
Compare
|
|
🎉 A review copy of this PR has been deployed! It is made of up two components Important Not all of the functionality of forms-runner is present in review apps. You should use the full dev environment to test the functionality which is disabled here. It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready For the sign in details and more information, see the review apps wiki page. |
319e15c to
c7e5c58
Compare



What problem does this pull request solve?
Add custom spans and metadata to traces
Things to consider when reviewing