Hello, there is some kind of misunderstanding regarding the Alerts API. The documentation says that there is the "extraProperties" field must be included in the response:
"extraProperties": {
"backend": false,
"browser": "Firefox 113.0",
"browser.name": "Firefox",
"bundler": "parcel@2.10.3",
"environment": "production"
},
...
What I actually see:
curl --request GET \
--url 'https://api.atlassian.com/jsm/ops/api/{cloudId}/v1/alerts?&query=detailsPair:(cluster!:production)&from=1749729674000&to=1749816177000
--user 'me:token' \
--header 'Accept: application/json'
{
"values": [
{
"id": "XXXXX",
"tinyId": "16154",
"createdAt": "2025-06-13T12:00:49.789Z",
"updatedAt": "2025-06-13T12:10:49.463Z",
"message": "[Prometheus]: NodeCPUHighUsage [info] prometheus — High CPU usage.",
"entity": "",
"source": "/alertmanager...",
"status": "closed",
"alias": "d3df7763768dca848174830d930bfd6fb1d661f276d362641c9f66b52aeb20f2",
"tags": [],
"acknowledged": false,
"count": 1,
"owner": "",
"snoozed": false,
"lastOccuredAt": "2025-06-13T12:00:49.789Z",
"integrationType": "Prometheus",
"integrationName": "SRE-prometheus",
"priority": "P4",
"responders": [
{
"id": "xxx",
"type": "team"
}
],
"actions": [],
"seen": true
},
...
The field extraProperties is included only if I query the alert by its ID, using the Get Alert API.
I've also come across this issue, but for some reason, it was closed without any explanations.
If I have, let's say, 100 alerts and I want to make a digest of non-critical alerts, I would have to make 100 separate API calls to get the information about each alert. Why is there a discrepancy between the documentation and the actual API? :(
Thanks.
Hi @Artem Miroshnychenko -- Welcome to the Atlassian Community!
You may want to ask this question in the Developer Community also:
https://community.developer.atlassian.com/
Kind regards,
Bill
Thanks for the suggestion, I'll do that now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.