AvantGuard - DNSFilterInstall

Overview

This node fetches aggregated traffic threat data related to agents from a security or network monitoring service. It is designed to generate reports summarizing total threats detected by various user agents over a specified time range and filtered by multiple criteria such as agent IDs, types, applications, networks, and more.

Common scenarios where this node is beneficial include:

• Security analysts wanting to monitor threat activity across different user agents in their network.
• Network administrators generating periodic reports on blocked or allowed traffic incidents.
• Incident response teams filtering threat data by specific agents, applications, or organizational units for detailed investigation.

Practical example:

• Generate a report of all blocked threats detected by specific user agents within the last 7 days, grouped by individual agents, to identify which agents are most frequently targeted.

Properties

Output

The node outputs JSON data containing the aggregated traffic threat report based on the applied filters. The structure typically includes:

• Summary statistics of total threats per agent or grouped entities.
• Time-bucketed counts of threats according to the selected bucket size.
• Breakdown by threat type (allowed, blocked, all).
• Details about agents, applications, networks, or other filtered dimensions depending on input parameters.

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

Dependencies

• Requires an API key credential for authenticating requests to the external traffic monitoring or security reporting service.
• The node uses a base URL endpoint https://api.dnsfilter.com indicating dependency on the AvantGuard DNSFilter API or similar service.
• Proper configuration of credentials and network access to the API endpoint is necessary.

Troubleshooting

• Invalid Date Format: If the from or to date parameters are not in the correct ISO format, the API may reject the request or return unexpected results. Ensure dates follow YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ.
• Empty Results: Applying overly restrictive filters (e.g., specific agent IDs or date ranges with no data) can result in empty responses. Try broadening filters to verify connectivity and data availability.
• Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Verify that the API key is correctly configured in n8n credentials.
• Network Issues: Connectivity problems to the API endpoint can cause timeouts or errors. Check network settings and firewall rules.
• Unsupported Bucket Size: Using unsupported values for bucket_size may lead to errors or default fallback behavior. Use only auto, 15min, or 1day.

Links and References

• AvantGuard DNSFilter API Documentation (for detailed API usage and parameter descriptions)
• ISO 8601 Date and Time Format (for correct date formatting)
• n8n Documentation on Creating Custom Nodes