AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

The "Traffic Reports Top Networks" operation in the Traffic Reports resource fetches summarized traffic data about the top networks based on various filtering criteria. This node is useful for network administrators and security analysts who want to analyze network traffic patterns, identify top-performing or problematic networks, and generate reports filtered by time range, network attributes, user agents, and other parameters.

Practical examples include:

  • Generating a report of the top networks accessed within the last 24 hours.
  • Filtering traffic reports to only include blocked traffic types or specific user agents.
  • Analyzing traffic from particular organizations or applications to monitor usage or detect anomalies.

Properties

Name Meaning
Additional Query Parameters Optional filters and query parameters that refine the traffic report request. 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 if empty.
  Application Ids Comma separated list of application IDs; defaults to all if empty.
  Collection Ids Comma separated list of collection IDs; defaults to all if empty.
  From UTC lower limit datetime for the report in format YYYY-MM-DDThh:mm:ss or with trailing Z; 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 networks whose name contains this string.
  Nat Ips Comma separated list of NAT IPs (valid integers 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.
  Page JSON object specifying pagination, e.g., page number and size (defaults to page 1, size 10, max 100).
  Private Ip 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 indicating whether to include threat reports (true), exclude them (false), or both if not set. Defaults to true.
  Source Traffic source filter; options are all, networks, agents, or proxies. Defaults to all.
  To UTC upper limit datetime for the report in format YYYY-MM-DDThh:mm:ss or with trailing Z; defaults to current UTC datetime or ignored if format invalid.
  Type Type of report to return; options are all, allowed, or blocked. Defaults to all.
  User Ids Comma separated list of local user IDs; defaults to all if empty.

Output

The node outputs JSON data representing the top networks traffic report according to the specified filters. The structure typically includes aggregated statistics about networks such as network identifiers, names, traffic counts, allowed or blocked status, and possibly threat information depending on the security_report flag.

If binary data were output, it would represent raw report files or attachments, but this node focuses on JSON structured data summarizing traffic metrics.

Dependencies

  • Requires an API key credential for authenticating requests to the external traffic reporting service.
  • The node sends HTTP requests to the service's API endpoint with appropriate query parameters.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid Date Format: If the from or to date strings are not in the expected ISO 8601 format, the API may ignore these filters or return errors. 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 API errors. Validate input formats carefully.
  • Pagination Limits: Requesting pages beyond available data or sizes larger than 100 may cause errors or truncated results. Use sensible pagination settings.
  • Authentication Errors: Missing or invalid API credentials will prevent successful requests. Verify the API key is correctly configured in n8n credentials.
  • Network Connectivity: Ensure the n8n instance has internet access to reach the external API endpoint.

Links and References

  • Refer to the official API documentation of the traffic reporting service for detailed parameter descriptions and response schemas.
  • n8n documentation on creating and configuring API key credentials.
  • General best practices for date/time formatting in APIs (ISO 8601 standard).

Discussion