AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node operation, Traffic Reports Total Applications Agents Stats, retrieves aggregated traffic report statistics related to applications and user agents. It is designed to query detailed traffic data filtered by various parameters such as agent IDs, application categories, network IDs, time ranges, and more. This node is useful for network administrators or security analysts who want to analyze traffic patterns, monitor application usage, or generate threat reports over a specified period.

Practical examples include:

  • Generating a report of all blocked traffic by specific user agents within the last 24 hours.
  • Filtering traffic stats by application categories to understand which types of applications are most used or blocked.
  • Creating security reports focusing on threats detected from certain networks or proxies.

Properties

Name Meaning
Additional Query Parameters A collection of optional filters to refine the traffic report query. These include:
- Agent Ids Comma separated list of user agent UUIDs; defaults to all agents if empty.
- Agent Types Comma separated list of user agent types; defaults to all types if empty.
- Application Category Ids Comma separated list of application category IDs; defaults to all categories if empty.
- Application Ids Comma separated list of application IDs; defaults to all applications if empty.
- Collection Ids Comma separated list of collection IDs; defaults to all collections if empty.
- 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 invalid.
- Mac Addresses Comma separated list of MAC addresses (without colons) or filter values; defaults to all if empty.
- Name Filter user agents whose name contains this string.
- Nat Ips Comma separated list of NAT IPs (valid integers from 101 to 106); defaults to all if empty.
- Network Ids Comma separated list of network IDs; defaults to all if empty.
- Organization Ids Comma separated list of organization IDs; defaults to the user's organization ID if empty.
- Private Ip Specific private LAN IP 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 include only threat reports (true), non-threats (false), or both (if not set). 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 invalid.
- Type Type of report to retrieve: All, Allowed, or Blocked traffic. Defaults to "all".
- User Ids Comma separated list of local user IDs; defaults to all users if empty.

Output

The node outputs JSON data containing aggregated traffic statistics based on the applied filters. The structure typically includes counts and metrics related to total applications and user agents, such as number of allowed or blocked requests, threat detections, and other relevant traffic analytics.

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

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard DNSFilter service.
  • The node uses the base URL https://api.dnsfilter.com to send queries.
  • Proper configuration of the API authentication token in n8n credentials is necessary.
  • The node depends on the external @avantguardllc/n8n-openapi-node package for building request properties and handling OpenAPI specifications.

Troubleshooting

  • Invalid Date Format: If the from or to date parameters are not in the correct ISO 8601 format, the node may default to preset dates or fail to filter correctly. Ensure dates follow YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ.
  • Empty or Incorrect Filters: Providing invalid or empty comma-separated lists (e.g., malformed UUIDs or IDs) might result in no data returned or errors. Validate input formats carefully.
  • Authentication Errors: Missing or incorrect API key credentials will cause authentication failures. Verify that the API key is correctly configured in n8n.
  • Network Issues: Connectivity problems to the API endpoint can cause request timeouts or failures. Check network access and proxy settings if applicable.
  • Permission Denied: Using organization IDs or user IDs outside the authorized scope may lead to permission errors. Confirm that the authenticated user has access rights to requested resources.

Links and References

Discussion