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.

Sign up for GitHub

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

Jump to bottom

Allow user to specify their own Prometheus instance #2

Open
mies opened this issue Jun 5, 2023 · 2 comments
Open

Allow user to specify their own Prometheus instance #2

mies opened this issue Jun 5, 2023 · 2 comments
Assignees
@hatchan
Labels
enhancement New feature or request

Comments

@mies
Copy link
Member

mies commented Jun 5, 2023

It would be nice if am detects if a Prometheus instance is already running (for instance via quickmetrics/docker) and won't download/run a local binary.

An alternative would be to run am with a --no-prometheus option that assumes that the user is already running, or connecting to a different Prometheus instance.
@mies mies added the enhancement New feature or request label Jun 5, 2023
@hatchan
Copy link
Contributor

hatchan commented Jun 6, 2023

Yeah think we can combine this with being able to point am to any existing Prometheus. So was thinking about something like --prometheus=127.0.0.1:9090

@hatchan hatchan changed the title ability to detect already running Prometheus and/or be able to specify not running Prometheus Allow user to specify their own Prometheus instance Jun 7, 2023
@mies
Copy link
Member Author

mies commented Jun 29, 2023

current idea is to have an explore subcommand, that just shows the UI with a custom prometheus instance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hatchan hatchan

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mies @hatchan