AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node operation retrieves asset governance data from the Datalake Inventory Governance service via a web API. It allows users to query and filter assets based on a wide range of criteria such as cloud provider details, asset status, tags, regions, risk factors, and more. This is useful for inventory management, compliance checks, and governance reporting in cloud environments. For example, a user can fetch all assets in a specific cloud provider organization unit with active coverage, or count assets matching certain risk factors.

Properties

Name Meaning
Additional Query Parameters A collection of optional filters and query parameters to refine the asset search. These include filters like cloud provider organization unit, region exclusions, asset status, tags, risk factors, sorting options, pagination controls (limit, skip, cursor), and flags like countOnly or skipCount to control the response size and content.

Output

JSON

  • items - An array of asset governance objects matching the query filters.
  • totalCount - The total number of matching assets, present if countOnly is false and skipCount is false.
  • cursor - Cursor string for pagination to fetch the next set of results if more than 1000 items exist.

Dependencies

  • Requires an API key credential for authentication to the Datalake Inventory Governance web API.
  • Depends on the base URL of the API endpoint configured in credentials.

Troubleshooting

  • If the node returns authentication errors, verify that the API key credential is correctly configured and has necessary permissions.
  • If no results are returned, check the query parameters for correctness and ensure they match existing asset data.
  • Using countOnly=true will return only the count; ensure this is intended to avoid confusion about missing asset details.
  • Pagination parameters like limit, skip, and cursor must be used correctly to iterate over large result sets.
  • Invalid filter values or malformed JSON in collection fields may cause API errors; validate inputs before execution.

Discussion