AvantGuard - DNSFilterInstall

Overview

This node operation, Traffic Reports Total Applications Stats, retrieves aggregated statistics about application traffic from a traffic reporting service. It is designed to provide detailed insights into network traffic related to various applications, filtered by multiple criteria such as agent types, application categories, time ranges, and more.

Typical use cases include:

• Network administrators analyzing total application usage over a specific period.
• Security teams monitoring allowed versus blocked application traffic.
• MSPs or organizations generating reports on application traffic filtered by user agents, networks, or proxies.

For example, you could use this node to get the total number of times certain applications were accessed within the last day, filtered by specific user agents or network IDs.

Properties

Output

The node outputs JSON data containing the aggregated traffic statistics for applications based on the specified filters. The exact structure depends on the API response but typically includes counts or metrics summarizing application traffic totals, possibly segmented by application, time, or other dimensions.

If binary data output is supported, it would represent raw report files or exports, but this operation primarily returns JSON summary data.

Dependencies

• Requires an API key credential for authenticating requests to the traffic reporting service.
• The node uses HTTP requests to the service's REST API endpoint at https://api.dnsfilter.com (as inferred from bundled code).
• Proper configuration of credentials in n8n is necessary to authorize API calls.

Troubleshooting

• Invalid Date Format: If the from or to date parameters are not in the expected ISO 8601 format (YYYY-MM-DDThh:mm:ss or with trailing Z), the API may default to current datetime minus one day or current datetime, potentially causing unexpected results.
• Empty or Incorrect Filters: Providing invalid IDs or malformed comma-separated lists can result in no data returned or errors.
• Authentication Errors: Missing or incorrect API key credentials will cause authorization failures.
• Network Issues: Connectivity problems to the API endpoint will prevent data retrieval.
• Permission Denied: Using organization or MSP IDs that the authenticated user does not have access to may cause permission errors.

To resolve these issues:

• Ensure date strings are correctly formatted.
• Validate all filter inputs before execution.
• Confirm API credentials are set up and valid.
• Check network connectivity.
• Verify user permissions for requested resources.

Links and References

• ISO 8601 Date Format
• Documentation for the traffic reporting API (not provided here; consult your service provider)
• n8n documentation on using API key credentials and HTTP request nodes