AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node operation fetches total domain traffic statistics reports from a traffic reporting service. It is useful for users who want to analyze aggregated traffic data filtered by various criteria such as domain name prefixes, time ranges, and organizational or network identifiers. Practical applications include monitoring network usage trends, auditing domain traffic over specific periods, and generating reports for managed service providers or organizations.

Properties

Name Meaning
Additional Query Parameters Optional filters and parameters to refine the traffic report query. Includes:
- Domain Filter to only search for domains starting with this value (string).
- From UTC lower limit of the report time range in format YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ. Defaults to current UTC datetime minus 1 day if not specified or invalid.
- To UTC upper limit of the report time range in format YYYY-MM-DDThh:mm:ss or YYYY-MM-DDThh:mm:ssZ. Defaults to current UTC datetime if not specified or invalid.
- Msp Id Managed Service Provider ID filter (number).
- Network Ids Comma-separated list of network IDs to filter by; defaults to all networks if empty (string).
- Organization Id Organization ID filter; defaults to the user's organization ID if zero or not provided (number).

Output

The node outputs JSON data containing the total domain traffic statistics matching the query parameters. The exact structure depends on the external API response but typically includes aggregated metrics such as counts, timestamps, domain names, and possibly breakdowns by network or organization. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the traffic reporting service.
  • The base URL for API requests is set to https://api.dnsfilter.com.
  • The node uses standard HTTP headers including Accept: application/json and Content-Type: application/json.
  • No additional environment variables are explicitly required beyond the API authentication credential.

Troubleshooting

  • Common issues:

    • Invalid date formats for the From and To parameters may cause the API to default to preset date ranges or return errors.
    • Providing incorrect or unauthorized MSP, Network, or Organization IDs may result in empty responses or authorization errors.
    • Missing or invalid API credentials will prevent successful API calls.

  • Error messages:

    • Authentication failures typically indicate missing or invalid API keys; ensure the correct credential is configured.
    • Validation errors on query parameters suggest checking the formatting and types of inputs, especially dates and numeric IDs.
    • Network or connectivity errors require verifying internet access and API endpoint availability.

Links and References

Discussion