-
Notifications
You must be signed in to change notification settings - Fork 211
chore: move from prom-client to OpenTelemetry metrics #1811
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
chore: move from prom-client to OpenTelemetry metrics #1811
Conversation
|
Skipping CI for Draft Pull Request. |
|
The image is available at: |
2160724 to
5b9e1f9
Compare
5b9e1f9 to
720a38b
Compare
|
The image is available at: |
|
TODO: need to update monitoring-and-logging.md, will go through this set up & update the docs |
563dfb5 to
ad3afca
Compare
|
The image is available at: |
ad3afca to
dfeb858
Compare
|
The image is available at: |
dfeb858 to
bf6ed0c
Compare
|
The image is available at: |
bf6ed0c to
8b33cc4
Compare
Signed-off-by: Jessica He <[email protected]>
8b33cc4 to
217a8d3
Compare
|
|
The image is available at: |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kim-tsao The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Jessica He <[email protected]>


Description
Adopts OpenTelemetry metrics for metrics and move away from using
prom-client.This change adds these new Backstage specific metrics:
catalog.stitching.durationcatalog.stitching.queue.lengthcatalog.stitching.queue.lengthbackend_tasks.task.runs.countbackend_tasks.task.runs.durationHowever, OpenTelemetry doesn’t collect Node.js specific metrics likenodejs_eventloop_lag_seconds.Note: Node.js specific metrics are WIP in this PRThe application metrics will be exposed at
localhost:9464/metricsThe host/process metrics will be exposed at
localhost:9463/metricsWhich issue(s) does this PR fix
Please make sure that the following steps are complete: