AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve traffic reports specifically focusing on "Traffic Reports Qps Active Users." It allows users to query detailed traffic data filtered by various parameters such as agent IDs, application IDs, network IDs, and time ranges. This node is beneficial for network administrators or security analysts who want to monitor DNS traffic patterns, analyze active user queries per second (QPS), and identify potential threats or anomalies in network traffic.

Practical examples include:

  • Monitoring DNS query activity over a specific time period to detect unusual spikes.
  • Filtering traffic reports by specific user agents or applications to understand their behavior.
  • Generating threat reports to identify blocked or allowed traffic sources.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the traffic report query. Includes:
- Agent Ids: Comma-separated list of user agent UUIDs.
- Agent Types: Comma-separated list of user agent types.
- Application Ids: Comma-separated list of application IDs.
- Collection Ids: Comma-separated list of collection IDs.
- From: UTC lower limit datetime for the report.
- Mac Addresses: Comma-separated list of MAC addresses without colons.
- Nat Ips: Comma-separated list of NAT IPs (valid integers 101-106).
- Network Ids: Comma-separated list of network IDs.
- Organization Ids: Comma-separated list of organization IDs.
- Private Ip: Specific private LAN IP.
- Private Ip From: Lower limit of private LAN IP range.
- Private Ip To: Upper limit of private LAN IP range.
- Security Report: Boolean to include threat reports (true/false).
- Source: Traffic source filter; options are All, Agents, Proxies.
- To: UTC upper limit datetime for the report.
- Type: Type of report; options are All, Allowed, Blocked.
- User Ids: Comma-separated list of local user IDs.

Output

The node outputs JSON data representing the traffic report results based on the applied filters. The structure typically includes metrics related to queries per second (QPS) and active users, segmented by the specified parameters. The output can be used directly in workflows for further processing, visualization, or alerting.

If binary data were involved (not indicated here), it would represent raw report files or logs, but this node focuses on JSON responses from the API.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The node uses the base URL https://api.dnsfilter.com for making requests.
  • No additional external dependencies beyond the API access and n8n's HTTP request capabilities.

Troubleshooting

  • Common Issues:

    • Invalid date formats for the from and to parameters may cause the API to default to preset date ranges or return errors.
    • Providing incorrect or malformed comma-separated lists in filters like agent IDs or MAC addresses could result in empty or partial data.
    • Missing or invalid API authentication will lead to authorization errors.

  • Error Messages:

    • Authorization errors indicate issues with the provided API key; ensure the key is valid and has necessary permissions.
    • Validation errors on query parameters suggest incorrect formatting; verify that dates follow ISO 8601 format and lists are properly comma-separated without extra spaces.
    • Network or timeout errors may occur if the API service is unreachable; check network connectivity and API status.

Links and References

Discussion