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

docs: clarify API routing (and with --web.external-url) #1918

Merged
merged 1 commit into from
Jun 12, 2019

Conversation

adamdecaf
Copy link
Contributor

I couldn't find a reference for determining API routes on the readme, after some trial and error I found out what worked.

Copy link
Contributor

@stuartnelson3 stuartnelson3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small comment, but that's all. Thanks!

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@adamdecaf
Copy link
Contributor Author

Thanks. I've updated after your suggestions.

README.md Outdated

With the default config, endpoints are accessed under a `/api/v1` or `/api/v2` prefix.
The v2 `/status` endpoint would be `/api/v2/status`. If `--web.route-prefix` is set then API routes are
prefixed with that as well, so `--web.route-prefix=https://int.company.com/alertmanager/` would
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd just be /alertmanager/ for this flag.

Signed-off-by: Adam Shannon <adamkshannon@gmail.com>
@adamdecaf
Copy link
Contributor Author

Fixed and rebased.

@stuartnelson3 stuartnelson3 merged commit d15df87 into prometheus:master Jun 12, 2019
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

Successfully merging this pull request may close these issues.

5 participants