Meraki API details missing

Romen
Comes here often

Meraki API details missing

I am sharing the API details and missing info (highlighted in red) in the response.

We are getting null value for few details and Alert Created Date and Time is missing from below API response.

API: https://api.meraki.com/api/v1/networks/N_577023702256877336/health/alerts

Header: X-Cisco-Meraki-API-Key: <API Key>

Method:
GET

Getting null value:
1. "id": "",
2. "severity": null,

Missing Details 
1. Alert Created Date and Time
2. Alert Type

Please see the below response we are getting currently.
[
    {
        "id": "",
        "category": "Connectivity",
        "type": "Unreachable device",
        "severity": null,
        "scope": {
            "devices": [
                {
                    "url": "https://n25.meraki.com/Coriant-Wireless/n/F_RWLaz/manage/nodes/new_list/149624921699120",
                    "name": "MR2",
                    "productType": "wireless",
                    "tags": [
                        "1stfloorAP",
                        "HOTSPOT",
                        "recently-added"
                    ],
                    "serial": "Q2FD-S5SX-MXRU",
                    "mac": "88:15:44:4e:b3:30"
                }
            ],
            "applications": [],
            "peers": []
        },
        "schemaVersion": "network-alert-api"
    }
]

7 Replies 7
GreenMan
Meraki Employee
Meraki Employee

You're trying to get health alerts for a device that's never connected into the Dashboard  ("unreachable device")...   what you're receiving would, I think, be expected behaviour.

My analogy would be:   you're asking a dad man how he's feeling...  😀

Romen
Comes here often

We can see the ID and severity inside Meraki dashboard for that alert, but when we are trying to pull the alert through API, we are getting NULL value for ID & severity. 

Is there any configuration changes needed?

GreenMan
Meraki Employee
Meraki Employee

But how can you expect to get health information from a device that's not connected to the Meraki Dashboard?    Health relates to how the device is performing once it's connected - if it's not connected you won't get any health information

GreenMan
Meraki Employee
Meraki Employee

Just to be (hopefully) a bit clearer - the 'Health' referred to here is the health of the connectivity of client devices that connect through the Meraki devices being queried - it does not refer to the health of the Meraki device itself.

Romen
Comes here often

We have added devices as you mentioned and now getting the "Severity" but we are still not getting Alert ID & alert created date & time. Please refer the below response.

{

        "id": "",

        "category": "Connectivity",

        "type": "Unreachable device",

        "severity": "critical",

        "scope": {

            "devices": [

                {

                    "url": "https://n25.meraki.com/SVIC_HQ1-applian/n/He-pMcz/manage/nodes/new_spare_status",

                    "name": "MX250-SEC",

                    "productType": "appliance",

                    "tags": [],

                    "serial": "Q2SW-V95K-TAAF",

                    "mac": "08:f1:b3:58:55:9a"

                }

            ],

            "applications": [],

            "peers": []

        },

        "schemaVersion": "network-alert-api"

    }

Romen
Comes here often

@GreenMan : Request your input...

GreenMan
Meraki Employee
Meraki Employee

I'm really not clear what you're trying to achieve here - and I'm no expert in the script, but you appear to be trying to get status info from an MX on its warm spare 'brother' (New_spare_status) - but that MX has no warm spare (Unreachable device).   Please bear in mind this forum is not a substitute for Meraki Support.  you should probably contact them for any further assistance.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.