Aruba Central Next Gen icon

Aruba Central Next Gen

Consume Aruba Central Next Gen API
Join our community

Actions82

Overview

This node interacts with the Aruba Central Next Gen API to retrieve an overview of site health information. Specifically, for the Site Health resource and the List Sites with Health Overview operation, it fetches a paginated list of sites along with their health status summaries.

Typical use cases include:

  • Monitoring multiple network sites' health status in a centralized manner.
  • Automating alerts or reports based on site health metrics.
  • Integrating site health data into dashboards or other IT management tools.

For example, a network administrator could use this node to regularly pull health overviews of all managed sites, filter or analyze them, and trigger notifications if any site shows degraded health.

Properties

Name Meaning
Debug Mode Whether to enable detailed debug logs for troubleshooting.
Domain API domain to interact with. Options:
- Monitoring: Monitor devices, clients, and sites
- Configuration: Configure devices, groups, and profiles
Limit Number of sites to return per request (maximum 100).
Offset Number of sites to skip before starting to collect the result set.

Note: The Limit and Offset properties are only applicable when the Domain is set to "Monitoring" and the Resource is "Site Health" with the Operation "List Sites with Health Overview".

Output

The node outputs JSON data representing an array of site health overview objects. Each object typically contains summarized health metrics and status indicators for a single site, such as overall health score, number of devices, alerts, or other relevant health parameters.

If binary data were involved (not indicated here), it would represent files or media related to site health, but this node focuses on JSON structured data.

Dependencies

  • Requires an API key credential for authenticating with the Aruba Central Next Gen API.
  • The node depends on the "Monitoring" domain of the Aruba Central API to fetch site health data.
  • No additional external services beyond Aruba Central API are required.
  • Proper configuration of the API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting more than 100 sites in one call (limit > 100) will be rejected by the API.
    • Using an invalid offset may result in empty responses.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • "Unknown error in node execution": Generic catch-all error; check detailed debug logs if enabled.
    • Authentication errors: Verify that the API key or OAuth token is valid and has sufficient permissions.
    • Rate limiting or quota exceeded errors: Reduce request frequency or contact Aruba support.

Enabling Debug Mode helps capture detailed logs to diagnose issues.

Links and References

Discussion