I want to know , where does the generatorURL and externalURL points to when we get payload for alert generated in SigNoz? { "receiver":"w1", "status":"firing", "alerts":[ { "status":"firing", "labels":{ "alertname":"DiskRunningFull", "dev":"sda3", "instance":"example3", "severity":"critical" }, "annotations":{ "info":"The disk sda3 is running full", "summary":"please check the instance example1" }, "startsAt":"2022-04-25T143519.490146+05:30", "endsAt":"0001-01-01T000000Z", "generatorURL":"", "fingerprint":"ad592b0afcbe2e79" } ], "groupLabels":{ "alertname":"DiskRunningFull" }, "commonLabels":{ "alertname":"DiskRunningFull", "dev":"sda3", "instance":"example3", "severity":"critical" }, "commonAnnotations":{ "info":"The disk sda3 is running full", "summary":"please check the instance example1" }, "externalURL":"http://Apples-MacBook-Pro-3.local:9093", "version":"4", "groupKey":"{}/{}:{alertname=\"DiskRunningFull\"}", "truncatedAlerts":0 }

Hey @Shashank Gupta! I believe

externalURL

is the address of alertmanager that is used internally. I don't think the frontend implementation for plotting graph using

generatorURL

via alerts is done. @Amol Umbark should have more insights on it.

Hi @Prashant Shahi Do we get any URL in the payload that navigates us to the AlertRule which was triggered.

we don't have anything specific yet as all alerts are currently showed in a common place

/alerts

@Shashank Gupta you could try setting the url as a label in the rule definition and use the label down through webhook message. it is hacky but might work for immediate resolution. in future versions we can address this use case. please feel free to create an issue

@Amol Umbark Thanks Amol. Can u please tell me about the externalURL parameter?

externalURL is set to alert manager host:port, may not work for you if you don’t expose the alert manager ports to public