AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, Traffic Reports Total Requests, retrieves aggregated traffic report data focusing on total requests within a specified time range and various filtering criteria. It is useful for network administrators or security analysts who want to monitor traffic patterns, analyze allowed versus blocked requests, or generate threat reports based on user agents, networks, applications, and other parameters.

Practical examples include:

  • Generating daily summaries of total web requests filtered by specific user agents or applications.
  • Monitoring blocked versus allowed traffic over the last week to identify potential security threats.
  • Creating detailed reports grouped by individual networks or organizations to understand traffic distribution.

Properties

Name Meaning
Additional Query Parameters A collection of optional filters and settings that refine the traffic report query. These include:
- Agent Ids Comma-separated list of user agent UUIDs to filter by; defaults to all if empty.
- Agent Types Comma-separated list of user agent types; defaults to all.
- Application Ids Comma-separated list of application IDs; defaults to all.
- Bucket Size Desired bucket size for aggregation. Possible values: auto, 15min, 1day. Defaults to auto which selects 15 minutes buckets for ranges under 24 hours, and 1 day buckets for longer ranges.
- Collection Ids Comma-separated list of collection IDs; defaults to all.
- From UTC lower limit datetime for the report in format YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ. Defaults to current UTC datetime minus 1 day or ignored if format unrecognized.
- Mac Addresses Comma-separated list of MAC addresses (without colons) or filter values; defaults to all.
- Msp Id Numeric MSP (Managed Service Provider) ID; defaults to 0.
- Nat Ips Comma-separated list of NAT IPs (valid integers from 101 to 106); defaults to all.
- Network Ids Comma-separated list of network IDs; defaults to all.
- Organization Ids Comma-separated list of organization IDs; defaults to the user's organization ID.
- Private Ip Specific private LAN IP address to filter by.
- Private Ip From Lower limit of private LAN IP range.
- Private Ip To Upper limit of private LAN IP range.
- Security Report Boolean flag indicating whether to return only threat reports (true), non-threats (false), or both if not set. Defaults to true.
- Show Individual Networks Boolean flag to group the report results by network ID. Defaults to true.
- Source Traffic source filter with options: all, networks, agents, proxies. Defaults to all.
- To UTC upper limit datetime for the report in format YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ. Defaults to current UTC datetime or ignored if format unrecognized.
- Type Type of report to retrieve with options: all, allowed, blocked. Defaults to all.
- User Ids Comma-separated list of local user IDs; defaults to all.

Output

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

  • Time-bucketed counts of total requests.
  • Breakdown by request type (allowed, blocked).
  • Grouping by network, user agent, or other dimensions if requested.
  • Threat-related information if the security report flag is enabled.

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

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter service.
  • The node sends HTTP requests to the DNSFilter API endpoint at https://api.dnsfilter.com.
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Invalid Date Format: If the from or to date properties are not in the expected ISO 8601 format, the API may ignore them or default to preset ranges. Ensure dates follow YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ.
  • Empty or Incorrect Filters: Providing invalid IDs or malformed comma-separated lists can result in no data returned or errors. Validate input formats carefully.
  • API Authentication Errors: Missing or incorrect API keys will cause authentication failures. Verify the API key credential is correctly configured.
  • Large Data Sets: Requesting very large date ranges or many filters simultaneously might lead to timeouts or partial data. Use appropriate bucket sizes and narrower filters when possible.

Links and References

Discussion