AvantGuard - DNSFilterInstall

Overview

This node operation, Traffic Reports Total Threats Users, retrieves aggregated traffic threat data related to users from a security or network monitoring service. It is designed to generate reports summarizing total threats detected per user over a specified time range and filtered by various criteria such as agent types, applications, networks, and more.

Typical use cases include:

• Security analysts wanting to monitor the number of threats associated with different users in their organization.
• Network administrators generating periodic reports on threat activity to identify high-risk users or devices.
• Automated workflows that trigger alerts or further investigation based on threat counts per user.

For example, you could configure this node to fetch all blocked traffic threats for specific user IDs within the last 7 days, grouped by individual users, helping prioritize incident response efforts.

Properties

Output

The node outputs JSON data representing the aggregated traffic threat report according to the specified filters. The structure typically includes:

• Summary statistics of total threats per user or grouped entities.
• Time-bucketed counts if bucket size is specified.
• Breakdown by threat type (allowed, blocked, all).
• Grouping by user ID if enabled.

If binary data output is supported, it would represent downloadable report files or raw data exports, but this is not indicated in the provided code.

Dependencies

• Requires an API key credential for authenticating with the external traffic reporting service.
• The node uses a base URL endpoint (https://api.dnsfilter.com) for making requests.
• Proper configuration of authentication credentials in n8n is necessary.
• The node depends on the external service's API availability and correct parameter formatting.

Troubleshooting

• Invalid Date Format: If the from or to date parameters are incorrectly formatted, the API may reject the request or return default ranges. Ensure dates follow the ISO 8601 format (e.g., YYYY-MM-DDThh:mm:ssZ).
• Empty Results: Using overly restrictive filters (e.g., specific user IDs or agent types) might result in no data returned. Try broadening filters to verify connectivity.
• Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key credential is correctly set up in n8n.
• API Rate Limits: Excessive requests may be throttled by the external service. Implement retry logic or reduce request frequency if needed.
• Incorrect Parameter Names: All additional query parameters must match expected names exactly (e.g., agent_ids, bucket_size). Typos will cause the API to ignore them or error out.

Links and References

• ISO 8601 Date Format
• Documentation for the external traffic reporting API (not provided here, consult your service provider)
• n8n documentation on HTTP Request Node for understanding query parameter usage and authentication setup