Skip to content

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

@brettimus

Description

@brettimus

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions