New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Instrumentation Base] Improve install failure messages #1055
Comments
In the meantime, Is there any way to work out why installs fail? I'm using
I was mainly trying to get Update: Oh, we need to bump to Rails 5.2 at minimum (looks like that's already being worked on in our app so I'll wait a bit). source |
@NickLarsenNZ unfortunately we don't yet have better logging in this area yet. And, even more unfortunately, the minimum supported Rails version is now Rails 6 (since Rails 5 went EOL last summer): open-telemetry/opentelemetry-ruby-contrib#307 |
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
I am using Roda, and have this error: |
👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
Follow up form this discussion #1050, there is value in improve the quality of the failure to install messages. We could increase the detail to identify which specific checks failed to provide a better set of bread crumbs for users to follow in the event they have instrumentation failing to install.
The text was updated successfully, but these errors were encountered: