List Datasets

List the datasets an integration instance exposes, most-recently-seen first.

A dataset is one queryable unit of the integration — an index pattern for Elasticsearch/OpenSearch, an application for AppDynamics, a table for ServiceNow. Each entry carries when we last saw it and whether data has arrived for it recently.

Paginated because the count is unbounded in practice: the largest instance in production owns over 100,000 datasets. Use total_count for an "N indexes" label rather than the length of datasets.

search filters server-side on a case-insensitive substring of the dataset's stored key, narrowing total_count alongside the page. It does not match the rendered display_name, which is derived from the stored details and has no column to filter on; the two coincide for most integrations but not AppDynamics, whose key holds an application id while the row displays the application name.

dataset_term narrows to the rows carrying one source-system noun and narrows total_count too. It takes a key from this integration type's dataset_terms (see the integration catalog), which is also what each row reports as dataset_term_key — never the displayed wording, so the filter survives a rewording. log_group returns just the CloudWatch Logs half of an instance that also holds metric namespaces. A valid key belonging to another integration type selects nothing, and that empty page is the honest answer rather than an error. Both filters compose.

Permissions: users with integration-setup permission on the owning org.

Returns HTTP 404 if the instance does not exist in the resolved organization, and HTTP 503 (DATASET_AVAILABILITY_UNAVAILABLE) if the label-value store cannot be reached — availability is unknowable then, and reporting every dataset as not_available would be a false statement about the customer's data rather than about our own reachability.