did you try bot on the OpenShift 3.11?

[Nurlan199206]

I cant run your bot on openshift 3.11

level=info ts=2020-09-23T17:57:13.714667261Z caller=main.go:262 component=webserver msg="starting webserver" addr=0.0.0.0:8080
level=info ts=2020-09-23T17:57:13.714627292Z caller=main.go:220 component=telegram msg="starting alertmanager-bot" version=0.4.2 revision=bda776646e5591ea464ac1e0786e85cdd163b125 buildDate=2020-01-11T17:48:02+0000 goVersion=go1.13.6
level=info ts=2020-09-23T17:57:58.411409884Z caller=retry.go:56 component=telegram msg=retrying duration=235.816935ms err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts
level=info ts=2020-09-23T17:57:58.651358709Z caller=retry.go:56 component=telegram msg=retrying duration=258.261425ms err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts
level=info ts=2020-09-23T17:57:58.917035914Z caller=retry.go:56 component=telegram msg=retrying duration=356.90141ms err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts
level=info ts=2020-09-23T17:57:59.278936149Z caller=retry.go:56 component=telegram msg=retrying duration=476.943296ms err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts
level=info ts=2020-09-23T17:57:59.76566419Z caller=retry.go:56 component=telegram msg=retrying duration=1.03661806s err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts
level=info ts=2020-09-23T17:58:00.80601158Z caller=retry.go:56 component=telegram msg=retrying duration=1.681641161s err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts
level=info ts=2020-09-23T17:58:02.492782776Z caller=retry.go:56 component=telegram msg=retrying duration=2.189617195s err="Get https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts: x509: certificate signed by unknown authority" url=https://alertmanager-main-openshift-monitoring.router.default.svc.cluster.local/api/v1/alerts

[metalmatze]

This seems like a mTLS issue that's unrelated to the alertmanager-Bot. Or are you asking for mTLS support? I happily accept PRs. 😊

[Nurlan199206]

or i can use service path instead url...?

like this? - '--alertmanager.url=alertmanager-main.openshift-monitoring.svc'

[metalmatze]

That won't help. The problem is that you need to trust the certificates of Prometheus.

[Nurlan199206]

ok, i finally configured bot. But i dont receiving notification from events, for example CrashLoopPod etc... i can see only alert events with command /alerts.

[Nurlan199206]

how to start alertmanager-bot as systemd service?

systemd service started, but telegram bot commands not working....

i'm added new service to systemd.

[Unit]
Description=alertmanager-bot

[Service]
ExecStart=/etc/alertmanager-bot/alertmanager-bot --listen.addr="127.0.0.1:8080" --template.paths=/etc/alertmanager-bot/default.tmpl --alertmanager.url=http://127.0.0.1:9093 --log.level=info --store=bolt --bolt.path="/etc/alertmanager-bot/bot.db" --telegram.token=XXXX --telegram.admin=XXXXX
WorkingDirectory=/etc/alertmanager-bot
TimeoutSec=15
Restart=always
User=root
Group=root

[Install]
WantedBy=multi-user.target

[Nurlan199206]

i moved binary file to /usr/bin/ and it is works as simple command, but with systemd no success

[metalmatze]

The logs look like the bot is up and running successfully. It has to be the configuration outside of the bot most liekly.

[Nurlan199206]

finally ran as service.

[Unit]
Description=alertmanager-bot

[Service]
ExecStart=/etc/alertmanager-bot/alertmanager-bot 
WorkingDirectory=/etc/alertmanager-bot/
TimeoutSec=15
Restart=always
User=root
Group=root
Environment=ALERTMANAGER_URL=http://127.0.0.1:9093
Environment=BOLT_PATH=/tmp/bot.db
Environment=LISTEN_ADDR=0.0.0.0:8080
Environment=STORE=bolt
Environment=TELEGRAM_ADMIN=XXXXXXX
Environment=TELEGRAM_TOKEN=XXXXXX
Environment=TEMPLATE_PATHS=/etc/alertmanager-bot/default.tmpl
Environment=http_proxy=myproxy:port
Environment=https_proxy=myproxy:port 

[metalmatze]

@Nurlan199206 Looks good. You probably don't need to run it as root though. Be careful with /tmp/bot.db in production too. This will lose all data once the machine gets restarted. Otherwise looking good.