AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, Traffic Reports Total Collections Agents, retrieves aggregated traffic report data grouped by collection agents. It is designed to provide detailed insights into network traffic collected from various agents over a specified time range. This can be useful for network administrators or security analysts who want to monitor traffic patterns, detect anomalies, or generate reports on allowed and blocked traffic.

Typical use cases include:

  • Generating daily or hourly summaries of traffic handled by different agents.
  • Filtering traffic reports by agent types, applications, networks, or organizations.
  • Analyzing security-related traffic by including threat reports.
  • Customizing the granularity of the report with bucket sizes like 15 minutes or 1 day.

For example, a user might request a report showing total collections from all agents in their organization over the last week, grouped by each individual agent, focusing only on blocked traffic sources.

Properties

Name Meaning
Additional Query Parameters Optional parameters to customize the traffic report query. Includes:
- Agent Ids: Comma separated list of user agent UUIDs (defaults to all).
- Agent Types: Comma separated list of user agent types.
- Application Ids: Comma separated list of application IDs.
- Bucket Size: Desired bucket size for aggregation (auto, 15min, 1day).
- Collection Ids: Comma separated list of collection IDs.
- From: Report UTC lower limit datetime (format YYYY-MM-DDThh:mm:ss or with Z).
- Mac Addresses: Comma separated list of MAC addresses without colons.
- Network Ids: Comma separated list of network IDs.
- Organization Ids: Comma separated list of organization IDs (defaults to user's org).
- Private Ip: Private LAN IP.
- Private Ip From/To: Range limits for private LAN IP.
- Security Report: Boolean to include threats report (true/false/both).
- Show Individual Agents: Boolean to group results by agent id.
- Source: Traffic source filter (all, networks, agents, proxies).
- To: Report UTC upper limit datetime.
- Type: Type of report (all, allowed, blocked).
- User Ids: Comma separated list of local user IDs.

Output

The node outputs JSON data representing the aggregated traffic report based on the query parameters. The structure typically includes:

  • Aggregated metrics grouped by agent or collection as requested.
  • Time-bucketed traffic data according to the specified bucket size.
  • Details about allowed, blocked, or all traffic depending on the type filter.
  • If enabled, security threat information related to the traffic.

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

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 fetch traffic reports.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Invalid Date Format: If the from or to date parameters are not in the correct ISO format (YYYY-MM-DDThh:mm:ss), the API may default to current datetime minus one day or current datetime, which could lead to unexpected report ranges. Ensure dates are correctly formatted.
  • Empty Results: If filters such as agent IDs, network IDs, or organization IDs are too restrictive or incorrect, the report may return no data. Verify that the IDs exist and are accessible by your API credentials.
  • Authentication Errors: Missing or invalid API key will cause authentication failures. Confirm that the API key credential is properly configured in n8n.
  • Unsupported Bucket Size: Using unsupported values for bucket_size may cause errors or fallback behavior. Use only auto, 15min, or 1day.
  • Boolean Parameter Issues: For boolean fields like security_report and show_individual_agents, ensure the input is a proper boolean value; otherwise, the API may ignore or misinterpret the parameter.

Links and References


This summary is based solely on static analysis of the provided code and property definitions.

Discussion