This message was deleted.
# supports
Slackbot
04/01/2022, 3:26 PMThis message was deleted.
k
Kumaran Ilangovan
04/01/2022, 3:49 PMHi #C01HWQ1R0BC, @Ankit Nayan
When logged in to my minikube - seems the url itself is invalid. I can curl the alertmanager url - but not with relative path /api/v1/routes/
In screenshot - I have curl within my minikube - and seems baseurl for alertmanager was fine - but not with api/v1/routes
a
Ankit Nayan
04/01/2022, 5:15 PM
@User do we have the latest helm release ready? Kumaran might be facing issues due to that.
k
Kumaran Ilangovan
04/04/2022, 12:08 PMHi @User - whether Helm is released. If not please let me know, whether any other helm changes than signoz version, from earlier helm release.
p
Prashant Shahi
04/04/2022, 12:20 PMHey @User! New chart will be out by the EOD with latest SigNoz version.
🙌 1
Prashant Shahi
04/04/2022, 6:47 PM@User we have released new charts:
Copy code
NAME CHART VERSION APP VERSION
signoz/signoz 0.0.11 0.7.4
signoz/clickhouse 16.0.3 21.12.3.32k
Kumaran Ilangovan
04/05/2022, 5:03 AMHi @User - should we install clickhouse thru new chart? Or does signoz/signoz has clickhouse as well.
p
Prashant Shahi
04/05/2022, 5:07 AMTo upgrade, you can refer to here:
https://signoz.io/docs/operate/kubernetes/#upgrade
🙌 1
k
Kumaran Ilangovan
04/05/2022, 5:12 AMHi @User - after upgrade - alertmanager is moving into CrashLoopBackOff.
Also, the error in Alertmanager is,
level=info ts=2022-04-05T050817.784Z caller=main.go:236 msg="Starting Alertmanager" version="(version=0.23.0, branch=pull-1, revision=bb7c380db5cbbf8ae0efb87e1006c328e989fcea)"
level=info ts=2022-04-05T050817.784Z caller=main.go:237 build_context="(go=go1.17.7, user=ec2-user@ip-172-31-17-99.us-east-2.compute.internal, date=20220329-052731)"
level=info ts=2022-04-05T050817.784Z caller=cluster.go:184 component=cluster msg="setting advertise address explicitly" addr=172.17.0.7 port=9094
level=info ts=2022-04-05T050817.785Z caller=cluster.go:679 component=cluster msg="Waiting for gossip to settle..." interval=2s
level=info ts=2022-04-05T050817.986Z caller=coordinator.go:141 component=configuration msg="Loading a new configuration"
level=error ts=2022-04-05T050817.986Z caller=coordinator.go:148 component=configuration msg="*configuration update failed*" config="global:\n resolve_timeout: 5m\n http_config:\n follow_redirects: true\n smtp_from: alertmanager@signoz.io\n smtp_hello: localhost\n smtp_smarthost: localhost:25\n smtp_require_tls: true\n pagerduty_url: https://events.pagerduty.com/v2/enqueue\n opsgenie_api_url: https://api.opsgenie.com/\n wechat_api_url: https://qyapi.weixin.qq.com/cgi-bin/\n victorops_api_url: https://alert.victorops.com/integrations/generic/20131114/alert/\nroute:\n receiver: default-receiver\n continue: false\n group_wait: 30s\n group_interval: 5m\n repeat_interval: 4h\nreceivers:\n- name: default-receiver\n email_configs:\n - send_resolved: false\n to: default@email.com\n from: alertmanager@example.org\n html: '{{ template \"email.default.html\" . }}'\ntemplates: []\n" err="received an error from query service while fetching config: error in http get: Get \"localhost:8080/api/v1/channels\": unsupported protocol scheme \"localhost\""
level=info ts=2022-04-05T050817.987Z caller=cluster.go:688 component=cluster msg="gossip not settled but continuing anyway" polls=0 elapsed=201.144383ms
Please let me know, if any additional config to be done?
p
Prashant Shahi
04/05/2022, 5:15 AMAlertmanager used to be another chart, it's now integrated with signoz.
Prashant Shahi
04/05/2022, 5:17 AMyou would have to remove all previous alertmanager components and retry the upgrade steps.
k
Kumaran Ilangovan
04/05/2022, 5:23 AMsure, let me try and update
Kumaran Ilangovan
04/05/2022, 5:47 AMThanks @User - able to create webhook now. Will keep posted on webhook integration as well. Thanks again!
🎉 1
11 Views