AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node operation, "Traffic Reports Total Domains," retrieves aggregated traffic report data focused on domain usage. It is designed to query and summarize total domains seen in network traffic within specified parameters such as time range, user agents, categories, networks, and more. This node is useful for network administrators or security analysts who want to monitor domain access patterns, detect anomalies, or generate reports on allowed or blocked domains over a period.

Practical examples include:

  • Generating daily summaries of all domains accessed across an organization’s networks.
  • Filtering domain traffic reports by specific user agents or device types.
  • Producing threat-related reports by toggling the security report option.
  • Grouping results by individual networks to analyze domain usage per subnet.

Properties

Name Meaning
Additional Query Parameters Optional filters and settings to customize the traffic report query. Includes:
- Agent Ids: Comma-separated list of user agent UUIDs (default all).
- Agent Types: Comma-separated list of user agent types.
- Application Ids: Comma-separated list of application IDs.
- Bucket Size: Aggregation bucket size; options are auto, 15min, 1day. Defaults to auto which adjusts based on date range.
- Category Ids: Comma-separated list of category IDs.
- Collection Ids: Comma-separated list of collection IDs.
- Domain: Filter domains starting with this value.
- From: UTC start datetime for report (format YYYY-MM-DDThh:mm:ss or with Z). Defaults to current UTC minus 1 day.
- Mac Addresses: Comma-separated 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: Specific private LAN IP.
- Private Ip From/To: Range for private LAN IP.
- Security Report: Boolean to filter threats only (true), non-threats only (false), or both if empty.
- Show Individual Networks: Boolean to group results by network ID.
- Source: Traffic source filter with options: All, Networks, Agents, Proxies.
- To: UTC end datetime for report. Defaults to current UTC.
- Type: Report type filter with options: All, Allowed, Blocked.
- User Ids: Comma-separated list of user IDs.

Output

The node outputs JSON data representing the aggregated traffic report for total domains matching the query parameters. The structure typically includes domain names along with associated metrics such as counts, timestamps, and possibly categorization or threat indicators depending on the filters applied.

If binary data output is supported (not explicitly shown here), it would represent downloadable report files or raw data exports related to the traffic reports.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard DNSFilter service.
  • The node communicates with the DNSFilter API endpoint at https://api.dnsfilter.com.
  • Proper configuration of the API authentication credential in n8n is necessary.
  • The node depends on the external @avantguardllc/n8n-openapi-node package for building request properties from the OpenAPI specification.

Troubleshooting

  • Invalid Date Format: If the from or to date parameters are not in the correct ISO format, the API may default to fallback dates or return errors. Ensure dates follow YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up in n8n.
  • Empty Results: Overly restrictive filters (e.g., very narrow date ranges or specific IDs) might yield no data. Try broadening filters or removing some parameters.
  • Network Issues: Connectivity problems to the DNSFilter API endpoint can cause request failures. Check network access and proxy settings if applicable.
  • Boolean Parameter Confusion: For security_report and show_individual_networks, ensure boolean values are correctly set; otherwise, unexpected filtering behavior may occur.

Links and References

Discussion