AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node performs bulk updates on user agents with mixed criteria. It allows filtering user agents based on various query parameters such as agent state, name search, network IDs, organization IDs, tags, and more. After filtering, it applies specified updates to the selected user agents in bulk.

Common scenarios where this node is beneficial include:

  • Updating multiple user agents' statuses or configurations at once based on dynamic filters.
  • Managing large fleets of user agents by applying changes only to those matching specific conditions (e.g., only online agents, or agents within certain organizations).
  • Automating maintenance tasks like enabling/disabling agents or changing their states in bulk without manual intervention.

Practical example:

  • An administrator wants to disable all user agents that are currently unprotected and have not received traffic in the last 15 minutes. They can use this node to filter those agents and apply the "disable" update in one operation.

Properties

Name Meaning
Additional Query Parameters Optional filters to narrow down which user agents to target. Includes:
• Agent State: protected, unprotected, bypassed, uninstalled
• Name Search: search term for hostname or friendly name
• Network Ids: list of network IDs
• Organization Ids: list of organization IDs
• Search: keyword(s) for hostname or friendly name
• State: online or offline
• Status: active, disabled, uninstalled
• Tags: list of tags
• Traffic Received Last 15 Mins: boolean filter for recent traffic
• Type: proxy or agents (user agent type)
Additional Body Fields Optional body fields to specify details of the bulk update. Currently supports:
• Ids: JSON array of user agent IDs to explicitly target

Output

The node outputs JSON data representing the result of the bulk update operation. This typically includes information about which user agents were updated and the status of the operation. The exact structure depends on the API response but generally contains success indicators and possibly error details for individual agents if any failed.

If binary data is returned by the API (not indicated here), it would represent raw response content, but this node primarily deals with JSON responses.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard DNSFilter service.
  • The node uses the base URL https://api.dnsfilter.com for its API calls.
  • No other external dependencies are indicated.

Troubleshooting

  • Common issues:
    • Incorrect or missing API authentication token will cause authorization errors.
    • Providing invalid filter values (e.g., malformed JSON arrays for IDs) may lead to request failures.
    • Filtering with no matching user agents will result in no updates applied; verify filter criteria.
  • Error messages:
    • Authorization errors: Check that the API key credential is correctly configured and valid.
    • Validation errors: Ensure JSON inputs (like IDs) are properly formatted.
    • Network errors: Verify internet connectivity and API endpoint availability.

Links and References

Discussion