AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node operation, User Agent Bulk Deletes Counts, is designed to retrieve counts of user agents eligible for bulk deletion based on various filtering criteria. It is useful in scenarios where an organization needs to manage and clean up large numbers of user agents (such as devices or clients) by identifying those that meet specific states, statuses, tags, or network affiliations before performing bulk delete actions.

Practical examples include:

  • Counting all user agents currently offline and tagged with a certain label to decide if they should be removed.
  • Filtering user agents by their agent state (e.g., protected or uninstalled) to assess how many fall into each category.
  • Searching user agents by hostname or friendly name keywords to find candidates for cleanup.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the count query. These include:
- Agent State: Filter by agent protection state (protected, unprotected, bypassed, uninstalled).
- Name Search: Search term for client names.
- Network Ids: JSON array of network IDs to limit scope.
- Organization Id: Numeric ID of the organization.
- Search: Keyword(s) to search user agents by hostname or friendly name.
- State: Filter by online/offline status.
- Status: Filter by user agent status such as active, disabled, or uninstalled.
- Tags: JSON array of tags to filter user agents.
- Traffic Received Last 15 Mins: Boolean to filter agents that have received traffic recently.
- Type: User agent type, either proxy or agents.

Output

The output contains a JSON object representing the count of user agents matching the specified filters. The exact structure is not detailed in the provided code, but typically it would include fields such as:

  • count: Number of user agents matching the criteria.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external service managing user agents.
  • The node uses HTTP requests to communicate with the backend API endpoint that provides user agent bulk delete counts.
  • No additional environment variables or configurations are explicitly required beyond standard API credential setup.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid filter values (e.g., malformed JSON for network IDs or tags) may result in request errors.
    • Network connectivity issues can prevent successful API calls.
  • Error Messages:

    • Authentication errors typically indicate invalid or expired API keys; reconfigure credentials accordingly.
    • Validation errors on query parameters suggest checking the format and allowed values for filters.
    • Timeout or connection errors require verifying network access and API availability.

Links and References

  • No direct links were provided in the source code.
  • For more information, consult the API documentation of the user agent management system integrated with this node.

Discussion