AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter
Join our community

Actions277

Overview

This node operation, Traffic Reports Qps Active Organizations, retrieves traffic report data focused on active organizations and their query-per-second (QPS) metrics. It is designed to fetch detailed traffic analytics filtered by various parameters such as agent IDs, application IDs, network IDs, time ranges, and more.

Typical use cases include:

  • Monitoring network traffic activity across multiple organizations.
  • Analyzing traffic patterns for security or performance insights.
  • Filtering traffic reports by specific agents, applications, or IP ranges.
  • Generating threat or security-related reports based on traffic data.

For example, a network administrator could use this node to pull traffic reports limited to certain user agents and within a specific date range to identify unusual spikes or blocked traffic events.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine 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.
- Collection Ids: Comma separated list of collection IDs.
- From: UTC lower limit 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.
- Msp Id: Numeric MSP ID.
- Nat Ips: Comma separated NAT IPs (valid integers 101 to 106).
- Network Ids: Comma separated network IDs.
- Organization Ids: Comma separated organization IDs, defaults to user's org ID.
- Private Ip: Private LAN IP.
- Private Ip From/To: Range limits for private LAN IP.
- Security Report: Boolean to filter threats report; true/false or both if empty.
- Source: Traffic source filter; options are All, Agents, Proxies.
- To: UTC upper limit datetime for report, defaults to current UTC.
- Type: Report type filter; All, Allowed, Blocked.
- User Ids: Comma separated local user IDs.

Output

The node outputs JSON data representing the traffic reports matching the specified filters. The structure typically includes details about active organizations, their traffic query rates, and associated metadata depending on the applied filters.

If binary data were involved (not indicated here), it would represent raw report files or logs, but this node focuses on structured JSON responses.

Dependencies

  • Requires an API key credential for authenticating requests to the external traffic reporting service.
  • The node uses a base URL endpoint https://api.dnsfilter.com for making HTTP requests.
  • Proper configuration of credentials in n8n is necessary to authorize API calls.

Troubleshooting

  • Common Issues:

    • Invalid date formats for from or to parameters may cause the API to default to fallback dates or return errors.
    • Providing incorrect or malformed comma-separated lists can lead to empty or partial results.
    • Missing or invalid API authentication will result in authorization errors.

  • Error Messages:

    • Unauthorized or 401 errors indicate missing or invalid API credentials.
    • 400 Bad Request errors often relate to invalid query parameter values or formats.
    • Empty responses might mean no data matches the given filters; try broadening the query.

  • Resolutions:

    • Ensure date/time strings follow the required ISO format.
    • Validate all comma-separated lists for correct syntax.
    • Confirm that the API key credential is correctly set up and has sufficient permissions.

Links and References

Discussion