AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

The "Traffic Reports Total Threats" operation in the Traffic Reports resource provides aggregated threat data related to network traffic. This node is useful for security analysts and network administrators who want to monitor and analyze total threats detected over a specified time range, filtered by various criteria such as agents, applications, networks, or organizations.

Typical use cases include:

  • Generating reports on blocked or allowed traffic threats within an organization.
  • Monitoring specific user agents or devices for suspicious activity.
  • Analyzing threat trends over custom time intervals with flexible bucket sizes.
  • Filtering threat data by network segments or collections for targeted insights.

For example, a security team could use this node to retrieve all blocked threats from the last 7 days grouped by individual networks, helping them identify which network segments are most affected.

Properties

Name Meaning
Additional Query Parameters Optional filters and parameters to customize the report query. Includes:
- Agent Ids: Comma separated list of user agent UUIDs (default all)
- Agent Types: Comma separated list of user agent types (default all)
- Application Ids: Comma separated list of application IDs (default all)
- Bucket Size: Desired bucket size for aggregation; options: auto, 15min, 1day (default auto). Auto selects 15min if range < 24h, else 1day.
- Collection Ids: Comma separated list of collection IDs (default all)
- From: Report start datetime in UTC (format YYYY-MM-DDThh:mm:ss or with Z), defaults to current UTC minus 1 day or if format invalid
- Mac Addresses: Comma separated MAC addresses without colons or filter values (default all)
- Network Ids: Comma separated list of network IDs (default all)
- Organization Ids: Comma separated list of organization IDs (default user org ID)
- Private Ip: Private LAN IP filter
- Private Ip From: Lower limit of private LAN IP range
- Private Ip To: Upper limit of private LAN IP range
- Show Individual Networks: Boolean to group results by network id (default true)
- Source: Traffic source filter; options: all, networks, agents, proxies (default all)
- To: Report end datetime in UTC (format YYYY-MM-DDThh:mm:ss or with Z), defaults to current UTC or if format invalid
- Type: Type of report; options: all, allowed, blocked (default all)
- User Ids: Comma separated list of local user IDs (default all)

Output

The node outputs JSON data containing the aggregated total threats report based on the applied filters and time range. The structure typically includes counts or metrics of threats grouped by the selected bucket size and optionally by network if enabled.

If binary data output is supported, it would represent downloadable report files or raw data exports, but this is not indicated in the provided information.

Dependencies

  • Requires an API key credential for authenticating with the external traffic reporting service.
  • The node sends HTTP requests to the service's API endpoint with query parameters constructed from the input properties.
  • 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 8601 format, the node may default to preset dates or fail. Ensure correct formatting like YYYY-MM-DDThh:mm:ssZ.
  • Empty Results: Applying overly restrictive filters (e.g., very specific agent IDs or network IDs) might result in no data returned. Try broadening filters.
  • Authentication Errors: Missing or incorrect API key credentials will cause authorization failures. Verify that the API key is correctly set up in n8n.
  • API Rate Limits: Frequent or large queries might hit rate limits imposed by the external service. Implement retry logic or reduce query frequency.
  • Boolean Property Misuse: The show_individual_networks property defaults to true; setting it incorrectly might change grouping behavior unexpectedly.

Links and References

  • No direct links provided in the source code. For more details, consult the official documentation of the traffic reporting API or the service provider’s developer portal.

Discussion