mosescha1972 opened a new issue, #38429:
URL: https://github.com/apache/superset/issues/38429
### Bug description
Description:
When an Alert is triggered in Superset, the webhook payload contains an
incorrect url value.
Raw body received by the webhook:
{
"name": "test8: Table",
"header": {
"notification_format": "TEXT",
"notification_type": "Alert",
"notification_source": "chart",
"chart_id": 73,
"dashboard_id": null
},
"text": null,
"description": null,
"url":
"http://:8888/explore/?form_data=%7B%22slice_id%22:+73%7D&force=true"
}
Webhook log:
172.18.0.1 - - [05/Mar/2026 06:29:00] "POST /superset-proxy HTTP/1.1" 200
Issue:
The url field in the webhook payload is incorrect:
It uses port 8888
It contains a form_data parameter
The hostname is empty (http://:8888)
However, the actual chart URL in the browser is:
http://:8088/explore/?form_data_key=0oYdXaJNOrc&slice_id=73
Differences:
Port mismatch (8888 vs 8088)
form_data vs form_data_key
Missing hostname in the generated URL
Expected behavior:
The url field in the Alert webhook payload should match the actual
accessible chart URL, including:
Correct hostname
Correct port (e.g., 8088)
Proper query parameters (e.g., form_data_key and slice_id)
Environment:
Superset master branch (December 25 build)
Alert triggered from chart (slice_id=73)
Webhook target: Mattermost proxy endpoint
Please investigate how the chart URL is constructed in the Alert execution
flow and ensure it uses the correct external base URL configuration.
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to
my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]