AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation fetches aggregated traffic report data showing the total number of requests broken down by geographic location. It is useful for analyzing network or service usage patterns across different regions, helping identify where most traffic originates or to monitor regional demand.

Common scenarios include:

  • Monitoring web or API traffic distribution by geography.
  • Generating reports for compliance or auditing purposes.
  • Identifying unusual spikes in traffic from specific locations.

For example, a user might request the total number of requests per country over the last day to understand which markets are most active.

Properties

Name Meaning
Limit Limits the size of the response (number of records returned).
Additional Query Parameters Optional parameters to refine the query:
- From UTC lower time limit for the report, format YYYY-MM-DDThh:mm:ss or with trailing Z. Defaults to current UTC minus 1 day if not set or invalid.
- Msp Id Numeric MSP (Managed Service Provider) identifier.
- Organization Ids Comma-separated list of organization IDs to filter the report; defaults to the user's organization ID if empty.
- To UTC upper time limit for the report, format YYYY-MM-DDThh:mm:ss or with trailing Z. Defaults to current UTC if not set or invalid.

Output

The output JSON contains aggregated traffic data grouped by geographic locations. Each item typically includes fields such as location identifiers (e.g., country codes), and the total number of requests originating from those locations within the specified time range.

If binary data were supported, it would represent raw report files or exports, but this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the external traffic reporting service.
  • The node sends HTTP requests to the service's API endpoint, passing query parameters based on input properties.
  • Proper timezone-aware date strings must be provided for accurate filtering.

Troubleshooting

  • Invalid Date Format: If the From or To parameters are incorrectly formatted, the API may default to preset times or return errors. Ensure dates follow the ISO 8601 format (YYYY-MM-DDThh:mm:ss or with Z).
  • Empty or Zero Limit: Setting Limit to zero might result in no data returned or default limits applied by the API. Specify a positive integer to control response size.
  • Authorization Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key is correctly configured in n8n credentials.
  • No Data Returned: If filters are too restrictive (e.g., wrong organization IDs or MSP ID), the response may be empty. Adjust query parameters accordingly.

Links and References

  • Refer to the external traffic reporting service API documentation for detailed parameter descriptions and response schema.
  • ISO 8601 date format specification: https://en.wikipedia.org/wiki/ISO_8601

Discussion