AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve traffic reports, specifically focusing on total domain requests. It is useful for network administrators and security analysts who want to monitor DNS traffic patterns, identify popular domains, or analyze network usage over a specified time range. For example, it can be used to generate reports on how many times certain domains were requested within an organization or across specific networks.

Properties

Name Meaning
Additional Query Parameters Optional parameters to filter and customize the traffic report query. Includes:
- Domain Filter domains starting with this string.
- From UTC lower limit of the report time range (format: YYYY-MM-DDThh:mm:ss or with 'Z'). Defaults to 1 day ago.
- Msp Id MSP (Managed Service Provider) identifier as a number.
- Network Ids Comma-separated list of network IDs to include in the report. Defaults to all networks if empty.
- Organization Id Organization identifier as a number. Defaults to the user's organization ID if not provided.
- To UTC upper limit of the report time range (format: YYYY-MM-DDThh:mm:ss or with 'Z'). Defaults to current UTC datetime.

Output

The node outputs JSON data containing the total domain request counts based on the applied filters. The structure typically includes domain names and their corresponding request totals within the specified time frame. This output can be used for further processing, visualization, or alerting within n8n workflows.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The node sends HTTP requests to https://api.dnsfilter.com.
  • Proper configuration of the API key credential in n8n is necessary for successful operation.

Troubleshooting

  • Common Issues:
    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect date formats for "From" and "To" parameters may result in default date ranges being used or errors.
    • Providing invalid network or organization IDs might lead to empty or error responses.
  • Error Messages:
    • Authentication errors typically indicate issues with the API key; verify the credential setup.
    • Validation errors on query parameters suggest checking the format and values of input fields.
    • Network connectivity issues should be checked if the node cannot reach the API endpoint.

Links and References

Discussion