Skip to content
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

Show friendlier error in am start when scrape target is not yet up #90

Open
brettimus opened this issue Jul 14, 2023 · 1 comment
Open

Comments

@brettimus
Copy link
Contributor

when you am start :1337 but port 1337 has no /metrics route, then you get a warning log in the console. it'd be nice to say something like "target not yet up, but prometheus will still try to scrape it" (don't use that exact copy pls)

image
@hatchan
Copy link
Contributor

hatchan commented Jul 14, 2023

This is running in verbose mode, when running in "normal" mode it is more clean though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants