AvantGuard - DNSFilterInstall

Overview

This node operation fetches aggregated traffic report statistics related to total applications and organizations. It is designed to query detailed traffic data filtered by various parameters such as agents, applications, networks, organizations, and time ranges. This is useful for network administrators or security analysts who want to analyze application usage and organizational traffic patterns over a specified period.

Practical examples include:

• Generating reports on how many applications are used across different organizations.
• Filtering traffic data by specific user agents or network IDs to identify usage trends.
• Monitoring allowed versus blocked traffic types within an organization.
• Creating threat/security reports based on traffic sources and categories.

Properties

Output

The node outputs JSON data containing aggregated statistics about total applications and organizations traffic reports. The structure typically includes counts and metrics grouped by the applied filters, such as application usage totals, organization-specific traffic stats, and possibly threat-related information if requested.

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

Dependencies

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

Troubleshooting

• Common Issues:

  • Invalid date/time format for "From" or "To" parameters may cause the API to reject the request or return default date ranges.
  • Providing invalid or non-existent IDs (agent, application, organization) will result in empty or partial data.
  • Missing or incorrect API authentication credentials will lead to authorization errors.
  • Overly broad queries without filters might result in large datasets causing performance issues or timeouts.

• Error Messages:

  • Authorization errors indicating invalid or missing API keys: Ensure the API key credential is correctly set up in n8n.
  • Validation errors for query parameters: Check that date formats and ID lists conform to expected formats.
  • Network or timeout errors: Verify network connectivity and API service status.

Links and References

• DNSFilter API Documentation (hypothetical link for reference)
• n8n documentation on HTTP Request Node for understanding API calls
• General best practices for Date and Time Formatting