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
File import service initially appears to Prometheus to be in an unknown state. This is because no metrics are available to be scraped until after a file has been imported.
To Reproduce
Deploy speckle on kubernetes with prometheus metrics enabled
Port-forward prometheus and view the prometheus targets http://localhost:9090/targets?search=
See that all targets except fileimport are in an up state, and fileimport is in an unknown state.
Expected behavior
Fileimport service should be shown as up by prometheus as soon as it is reporting to kubernetes it is ready.
Additional context
Proposed Solution (if any)
File import service should produce some metrics on startup, even if these are zero values.
The text was updated successfully, but these errors were encountered:
This may not be the bug I originally thought it was. I may have just been too early in looking at Prometheus and not allowed enough time for it to scrape all the services - will try to recreate this to verify the behaviour.
What package are you referring to?
File import service
Describe the bug
File import service initially appears to Prometheus to be in an unknown state. This is because no metrics are available to be scraped until after a file has been imported.
To Reproduce
http://localhost:9090/targets?search=
up
state, and fileimport is in an unknown state.Expected behavior
Fileimport service should be shown as
up
by prometheus as soon as it is reporting to kubernetes it is ready.Additional context
Proposed Solution (if any)
File import service should produce some metrics on startup, even if these are zero values.
The text was updated successfully, but these errors were encountered: