DumbMonit
IntegrationsNetwork and firewalls
Monitor Aruba Central with DumbMonit
BetaThe Wi-Fi access points, switches and gateways of an HPE Aruba Networking Central account through its cloud API: devices offline, active critical alerts, devices in poor health, and the number of connected clients.
DocumentationOfficial website: Aruba Central
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
The Wi-Fi access points, switches and gateways of an HPE Aruba Networking Central account, read through Central's cloud API: devices that went offline, active critical alerts, devices in poor health, and the number of connected clients. DumbMonit reads the new Central API (the one served from the *.api.central.arubanetworks.com gateways), once a minute. The recommended credential is a personal API client created in HPE GreenLake: DumbMonit exchanges its ID and secret for a two-hour access token (https://sso.common.cloud.hpe.com/as/token.oauth2, client_credentials) and keeps it until it expires. An access token pasted by hand works too, but DumbMonit cannot renew it: it stops working after…
Typical use. Beta. Aruba access points, switches and gateways through the cloud API: devices offline, critical alerts, device health, clients
Examples
- Aruba access points
- Aruba CX switches
- Aruba gateways
How it connects
What you need
- API clientRecommended: DumbMonit exchanges the client for an access token and renews it by itself.
- Access tokenWorks for a test, but expires after two hours and DumbMonit cannot renew it.
Network ports to open
443/TCPCentral API (HTTPS, the base URL of your region)443/TCPHPE GreenLake sign-in (HTTPS, sso.common.cloud.hpe.com)
Setup steps: Create a personal API client for DumbMonit
Sign in to HPE GreenLake (common.cloud.hpe.com) and open Manage Workspace → Personal API clients.
Click Create personal API client, name it as follows and choose your Central instance as the service.
dumbmonitCopy the client ID and the client secret: the secret is shown once, and HPE keeps no copy.
In Central, open the API gateway page (Menu → API Gateway → REST API) and note the base URL of your region.
In DumbMonit, enter that base URL as the address (for example us1.api.central.arubanetworks.com) and paste the client ID and the client secret.
Heads-up. Beta: written from HPE's published API reference, not yet tested on a real Central account. It reads the new Central API with Central credentials; credentials scoped to the GreenLake platform and classic Central are not supported.