AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node operation, Traffic Reports Total Requests Agents, retrieves aggregated traffic report data focused on total requests grouped by user agents. It is designed to provide detailed insights into network traffic patterns, filtered and segmented by various criteria such as agent IDs, types, applications, networks, and time ranges.

Typical use cases include:

  • Monitoring network usage by different user agents over a specified period.
  • Analyzing allowed versus blocked traffic requests for security auditing.
  • Generating reports segmented by specific agents or groups of agents.
  • Filtering traffic data by organizational units, networks, or device MAC addresses.

For example, a network administrator could use this node to generate a daily report showing the number of requests made by each user agent type within their organization, helping identify unusual activity or optimize resource allocation.

Properties

Name Meaning
Additional Query Parameters Optional filters and 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 start datetime in UTC (format YYYY-MM-DDThh:mm:ss or with Z).
- Mac Addresses: Comma-separated list of MAC addresses without colons.
- Msp Id: Numeric MSP ID.
- Nat Ips: Comma-separated list of NAT IPs (valid integers 101 to 106).
- 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 for private LAN IPs.
- Security Report: Boolean to filter 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 end datetime in UTC.
- Type: Report type filter (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 applied filters. The structure typically includes:

  • Aggregated counts of total requests per agent or grouped entities.
  • Time-bucketed data according to the selected bucket size (e.g., 15 minutes or 1 day).
  • Breakdown by request type (allowed, blocked, or all).
  • Details about the agents involved if grouping by individual agents is enabled.

If binary data output is supported, it would represent downloadable report files or raw data exports, but this is not indicated explicitly here.

Dependencies

  • Requires an API key credential for authenticating with the external traffic reporting service.
  • The node sends HTTP requests to a predefined base URL endpoint (not shown explicitly in the snippet but implied by the use of routing and query parameters).
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Invalid Date Format: If the from or to date strings are not in the expected ISO format, the report may default to current UTC minus one day or current UTC respectively, potentially causing unexpected data ranges.
  • Empty or Incorrect Filters: Providing invalid or empty comma-separated lists (e.g., malformed agent IDs) might result in no data returned or errors from the API.
  • API Authentication Errors: Missing or incorrect API keys will cause authentication failures.
  • Unsupported Bucket Size: Using unsupported values for bucket_size may lead to errors or default behavior.
  • Network Issues: Connectivity problems to the external API endpoint can cause request failures.

To resolve these issues:

  • Ensure date formats conform to ISO 8601 standards.
  • Validate all filter inputs before execution.
  • Confirm API credentials are correctly set up in n8n.
  • Use only supported options for enumerated properties like bucket_size, source, and type.

Links and References

  • No direct links provided in the source code.
  • For more information, consult the documentation of the external traffic reporting API used by this node (likely provided by the service vendor).
  • Refer to n8n documentation on how to configure API credentials and use HTTP request nodes for similar integrations.

Discussion