prometheus
HTTP request to JIRA API: unexpected status code 404:
I updated to the 0.29.0-rc.1 version
My alertmanager.yml looks like this:
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net/rest/api/2/'
api_type: 'cloud'
and I get this error in the logs
time=2025-10-15T11:22:38.145Z level=ERROR source=dispatch.go:363 msg="Notify for alerts failed" component=dispatcher num_alerts=1 err="jira/jira[0]: notify retry canceled due to unrecoverable error after 1 attempts: failed to lo
ok up existing issues: HTTP request to JIRA API: unexpected status code 404: <!DOCTYPE html>\n<html lang=\"en\">\n <head>\n <meta charset=\"utf-8\">\n <meta name=\"description\" content=\"\">\n <meta name
=\"viewport\" content=\"width=device-width, initial-scale=1\">\n <title>Atlassian Cloud Notifications - Page Unavailable</title>\n <link rel=\"stylesheet\" href=\"/_edge/resources/aui-prototyping.css\">\n </head
>\n <body>\n <div id=\"page\">\n <section id=\"content\" role=\"main\" class=\"aui-page-notification aui-page-size-medium\">\n <div id=\"notifications\" class=\"aui-page-panel\">\n
<div class=\"aui-page-header-inner\">\n <section class=\"aui-page-panel-content\">\n <h1>Page unavailable</h1>\n <div class=\"aui-page-notifica
tion-description\">\n Your Atlassian Cloud site is currently unavailable.\n <br/><br/>\n Please check <a href=\"https://status.atlassia
n.com\">Atlassian Status</a> for known problems.\n <br />\n If there are no known problems and your page hasn't appeared again in 5-10 minutes then please contact our
support team.\n </div>\n <br>\n <p>\n <a href=\"https://status.atlassian.com\" class=\"aui-button aui-button-primar
y\">\n Atlassian Status\n </a>\n \n <a href=\"https://support.atlassian.com\" class=\"aui-butt
on\">\n Contact Support\n </a>\n </p>\n <br>\n <p style=\"color:#B3B3B3; font:nor
mal 12px/18px Helvetica, Arial;\">Request ID: xxxxxxxxxxxxxxxxxxxxx</p>\n </section>\n </div>\n </div>\n </section>\n <footer id=\"footer\
">\n <section class=\"footer-body\">\n <ul>\n <li><a href=\"https://status.atlassian.com\">Atlassian Status</a></li>\n <li><a href=\"https://conflue
nce.atlassian.com/display/cloud/What's+New\">Release Summary</a></li>\n <li><a href=\"https://confluence.atlassian.com/display/Cloud/Atlassian+Cloud+Documentation\">Documentation</a></li>\n
<li><a href=\"https://answers.atlassian.com\">Answers</a></li>\n </ul>\n <div id=\"footer-logo\"><a href=\"https://www.atlassian.com/\" target=\"_blank\">Atlassian</a></div>\n
</section>\n </footer>\n </div>\n </body>\n</html>"
The atlassian instance is perfectly working
I even tried this curl and the response was correct
curl -u "[email protected]:apitoken" \
-X POST \
-H "Content-Type: application/json" \
-d '{"jql": "project=PROJECT", "maxResults": 1, "fields": ["status"]}' \
"https://company.atlassian.net/rest/api/3/search/jql"
I also tried to activate debug mode but i don't get the url where the alertmanager is pointing.
I tried changing the alertmanager.yml to:
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net/rest/api/3/'
api_type: 'cloud'
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net/rest/api/3/'
api_type: 'auto'
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net'
api_type: 'cloud'
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net'
api_type: 'auto'
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net/rest/api/2/'
- name: 'jira'
jira_configs:
api_url: 'https://company.atlassian.net/rest/api/2/'
api_type: 'auto'
but I got the same issue
@alex-deploys i'm sorry but i cannot replicate your error. I'm using this testing setup with docker compose:
docker-compose.yml
version: '3.8'
services:
alertmanager:
image: prom/alertmanager:v0.29.0-rc.1 # Using a stable, recent version
container_name: alertmanager
# Map the local configuration file into the container
volumes:
- ./alertmanager.yaml:/etc/alertmanager/alertmanager.yaml
# Expose the web UI port (default is 9093)
ports:
- "9093:9093"
# Ensure Alertmanager uses the configuration file we mounted
command:
- '--config.file=/etc/alertmanager/alertmanager.yaml'
- '--web.listen-address=:9093'
- '--log.level=debug'
restart: unless-stopped
alertmanager.yaml
route:
receiver: "null"
routes:
- receiver: 'default-receiver'
matchers:
- alertname!=""
continue: false
repeat_interval: 3m
# Receivers define where alerts are sent.
receivers:
- name: "null"
- name: 'default-receiver'
jira_configs:
- api_url: 'https://company.atlassian.net/rest/api/2/'
api_type: 'cloud'
project: ""
issue_type: "Alert"
fields:
customfield_10264:
value: "OE"
customfield_10237:
value: "missing"
http_config:
basic_auth:
username: "[email protected]"
password: ""
could you post your complete config?
This definitely looks like an ephemeral issue to me:
Your Atlassian Cloud site is currently unavailable.
Please check https://status.atlassian.com for known problems.
If there are no known problems and your page hasn't appeared again in 5-10 minutes then please contact our support team.
Atlassian does list some issues on 2025-10-15:
Resolved - Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira.
although the timestamp do not match exactly time=2025-10-15T11:22:38.145Z.
This does not appear to be an Alertmanager issue, I think it should be closed.
Hi @alex-deploys ,
closing this issue, since it seems to have resolved by itself.
Kind regards, Solomon Jacobs