Prometheus does not respect scheme config for the alertmanger.

[liquidgecka]

Using the following config:

alerting:
  alertmanagers:
    - scheme: https
    - basic_auth:
        username: "user"
        password: "pass"
    - static_configs:
      - targets: ["alertmanager.example.com"]

I see the following logs:

Jun 11 16:03:13 prometheus.aws-us-west-2 prometheus[1782]: level=error ts=2018-06-11T16:03:13.619243596Z caller=notifier.go:473 component=notifier alertmanager=http://alertmanager.example.com/api/v1/alerts count=0 msg="Error sending alert" err="bad response status 400 Bad Request"

Note that https is not respected when generating the alertmanager URL. This is on prometheus 2.3.0 (as well as 2.2.1) running on Ubuntu 16.04 LTS Linux 4.4.0-1031-aws x86_64

[krasi-georgiev]

Thanks for your report. It looks as if this is actually a question about usage and not development.

no crash, no panic = support question 😉

To make support question, and all replies, easier to find, I suggest you move this to our user mailing list.

If you haven't looked already you might find your answer in the official docs and examples or by searching in the users or devs groups.
The #prometheus IRC channel is also a great place to mix up with the community and ask questions (don't be afraid to answers few while waiting).

If you think this is not purely a support question, feel free to comment in here or in the dev mailing list.

Once your questions have been answered, please add a link to the solution to help other Prometheans in trouble reaching this from a search 👍

[liquidgecka]

Deoh! Your absolutely right! I looked at that like 5 times before finally seeing the white space difference.. =/

[krasi-georgiev]

no problem.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.