AvantGuard - DNSFilterInstall

Overview

The "Traffic Reports Qps" operation under the "Traffic Reports" resource is designed to retrieve detailed traffic query-per-second (QPS) reports from a network monitoring or security service. This node allows users to specify various filters and parameters to customize the traffic data they want to analyze, such as filtering by user agents, applications, networks, IP ranges, and time intervals.

This node is beneficial in scenarios where network administrators or security analysts need to monitor traffic patterns, detect anomalies, or generate usage statistics over specific periods. For example, it can be used to:

• Analyze traffic volume trends for different user agents or applications.
• Monitor allowed versus blocked traffic types.
• Generate threat-related reports by toggling security report options.
• Group results by individual networks for granular insights.

Properties

Output

The node outputs JSON data representing the traffic QPS report according to the specified filters and parameters. The structure typically includes aggregated traffic metrics grouped by the chosen bucket size and filtered by the selected criteria. The output may contain fields such as timestamps, counts of allowed or blocked traffic, threat indicators if enabled, and grouping by networks or other entities.

If binary data were involved (e.g., files or images), it would be summarized accordingly, but this node primarily returns structured JSON data.

Dependencies

• Requires an API key credential for authenticating requests to the underlying traffic reporting service.
• The node sends HTTP requests to a predefined base URL endpoint (not explicitly shown in the provided code but implied by the use of query parameters).
• Proper configuration of the API authentication token or key within n8n credentials is necessary.

Troubleshooting

• Invalid Date Format: If the from or to date parameters are not in the correct ISO format (YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ), the node may default to fallback dates or return errors. Ensure date strings are correctly formatted.
• Empty or Incorrect Filters: Providing invalid or empty comma-separated lists (e.g., malformed UUIDs or IPs) might result in no data returned or errors. Validate input values before execution.
• API Authentication Errors: Missing or incorrect API keys will cause authentication failures. Verify that the API key credential is properly set up in n8n.
• Unsupported Bucket Size: Using unsupported bucket sizes outside the allowed options (auto, 1min, 15min, 1day) may lead to errors or unexpected aggregation behavior.
• Network or Permission Issues: Network connectivity problems or insufficient permissions on the API side can cause request failures.

Links and References

• Refer to the official API documentation of the traffic reporting service for detailed descriptions of query parameters and response formats.
• n8n documentation on creating and using API key credentials.
• General best practices for date/time formatting in ISO 8601 standard.