AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, Traffic Reports Top Organizations Requests, retrieves traffic report data focused on the top organizations making requests within a specified time range. It is useful for network administrators or analysts who want to monitor and analyze traffic patterns by organization, identify heavy users, or detect unusual activity in their network environment.

Typical use cases include:

  • Generating reports of top organizations accessing network resources over a custom date/time range.
  • Monitoring traffic trends with configurable bucket sizes (e.g., 15 minutes or daily aggregation).
  • Paging through large result sets to handle extensive traffic data efficiently.

Properties

Name Meaning
Additional Query Parameters Optional parameters to customize the traffic report query:
- Bucket Size: Aggregation interval for data buckets; options are auto, 15min, or 1day. Defaults to auto which adjusts based on date range.
- From: UTC start datetime for the report in ISO format (e.g., YYYY-MM-DDThh:mm:ssZ). Defaults to current UTC minus 1 day if not set or invalid.
- Msp Id: Numeric ID of the Managed Service Provider (MSP). Default is 0.
- Organization Id: Numeric ID of the organization to report on. Defaults to the user’s organization ID.
- Page: JSON object specifying pagination details like page number (default 1) and page size (default 10, max 100).
- To: UTC end datetime for the report in ISO format. Defaults to current UTC datetime if not set or invalid.

Output

The node outputs JSON data containing the traffic report results for the top organizations' requests. The structure typically includes aggregated request counts grouped by organization and time buckets according to the specified bucket size. This allows downstream nodes or workflows to process, visualize, or store detailed traffic analytics.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the external traffic reporting service.
  • The node uses HTTP requests to communicate with the service's REST API endpoint.
  • Proper timezone handling and date formatting are necessary for the from and to parameters.
  • Pagination support requires correct JSON formatting for the page parameter.

Troubleshooting

  • Invalid Date Format Errors: If the from or to dates are not in the expected ISO format, the API may reject the request or default to fallback values. Ensure dates follow YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ.
  • Empty or Missing Data: If no data is returned, verify that the date range and organization IDs are correct and that there is traffic data available for those parameters.
  • Pagination Issues: Incorrectly formatted page JSON or out-of-range page numbers can cause errors or empty responses. Validate JSON syntax and ensure page numbers are positive integers.
  • API Authentication Failures: Confirm that the API key credential is correctly configured and has sufficient permissions.
  • Bucket Size Misconfiguration: Using unsupported bucket sizes may lead to unexpected aggregation results. Use only auto, 15min, or 1day.

Links and References

  • ISO 8601 Date and Time Format
  • Documentation for the external traffic reporting API (not provided here, but recommended to consult for detailed parameter usage and response schema)

Discussion