-
Notifications
You must be signed in to change notification settings - Fork 85
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
Support for OpenTelemetry #221
Comments
philippeckelintive
added a commit
to philippeckelintive/backstage-charts
that referenced
this issue
Oct 23, 2024
philippeckelintive
added a commit
to philippeckelintive/backstage-charts
that referenced
this issue
Oct 23, 2024
4 tasks
philippeckelintive
added a commit
to philippeckelintive/backstage-charts
that referenced
this issue
Oct 23, 2024
fixes backstage#221 Signed-off-by: Philipp Eckel <philipp.eckel@intive.com>
philippeckelintive
added a commit
to philippeckelintive/backstage-charts
that referenced
this issue
Oct 24, 2024
fixes backstage#221 Signed-off-by: Philipp Eckel <philipp.eckel@intive.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The now recommended Backstage solution for reporting metrics and traces is to use OpenTelemetry. However, this works by running by exporting metrics in a different port than the one used by the Backstage installation.
I'm trying to make the helm chart work with OpenTelemetry but I think the missing part is to open the port in the container, which is not configurable.
Does someone, by any luck, succeeded making OpenTelemetry work with the helm chart?
The text was updated successfully, but these errors were encountered: