Skip to content

Microsite: group landing page examples under an Example Queries heading #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeffreyaven merged 1 commit into from
Sep 17, 2026
Merged

Microsite: group landing page examples under an Example Queries heading #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions provider-dev/docgen/provider-data/headerContent2.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,11 @@ The provider merges the Datadog v1 and v2 REST APIs into 18 services (`monitorin

List operations with cursor pagination (`page[cursor]`) are traversed automatically; a SQL `LIMIT` is pushed to the API's page size parameter. Query parameters such as `filter[query]`, `filter[from]` or `tags` are used directly as `WHERE` predicates.

## Monitors
## Example Queries

Try the following queries using `stackql shell`, or run them from a script or CI pipeline with `stackql exec`.

### Monitors

Every monitor with its state - the first query most teams run:

Expand All @@ -83,7 +87,7 @@ FROM datadog.monitoring.monitor_search_results
WHERE query = 'type:metric status:alert';
```

## Users, roles and keys
### Users, roles and keys

User audit with status and login method:

Expand Down Expand Up @@ -120,7 +124,7 @@ FROM datadog.organization.api_keys
ORDER BY created_at;
```

## Dashboards and SLOs
### Dashboards and SLOs

```sql
SELECT id, title, layout_type, author_handle, modified_at
Expand All @@ -130,7 +134,7 @@ SELECT id, name, type, json_extract(thresholds, '$[0].target') AS target
FROM datadog.service_management.slos;
```

## Infrastructure
### Infrastructure

Hosts reporting to Datadog, with their apps and mute state:

Expand All @@ -150,7 +154,7 @@ FROM datadog.metrics.active_metrics
WHERE "from" = strftime('%s', 'now') - 3600;
```

## Logs, audit and usage
### Logs, audit and usage

Log indexes and their retention:

Expand Down Expand Up @@ -179,7 +183,7 @@ FROM datadog.organization.usage_summary
WHERE start_month = '2026-08';
```

## Provision, mutate and tear down
### Provision, mutate and tear down

Mutations use the same SQL grammar. A v1 resource (monitor) takes its fields as columns; a v2 resource (role, API key, downtime) takes the JSON:API `data` document. A monitor end to end:

Expand Down
16 changes: 10 additions & 6 deletions website/docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,11 @@ The provider merges the Datadog v1 and v2 REST APIs into 18 services (`monitorin

List operations with cursor pagination (`page[cursor]`) are traversed automatically; a SQL `LIMIT` is pushed to the API's page size parameter. Query parameters such as `filter[query]`, `filter[from]` or `tags` are used directly as `WHERE` predicates.

## Monitors
## Example Queries

Try the following queries using `stackql shell`, or run them from a script or CI pipeline with `stackql exec`.

### Monitors

Every monitor with its state - the first query most teams run:

Expand All @@ -110,7 +114,7 @@ FROM datadog.monitoring.monitor_search_results
WHERE query = 'type:metric status:alert';
```

## Users, roles and keys
### Users, roles and keys

User audit with status and login method:

Expand Down Expand Up @@ -147,7 +151,7 @@ FROM datadog.organization.api_keys
ORDER BY created_at;
```

## Dashboards and SLOs
### Dashboards and SLOs

```sql
SELECT id, title, layout_type, author_handle, modified_at
Expand All @@ -157,7 +161,7 @@ SELECT id, name, type, json_extract(thresholds, '$[0].target') AS target
FROM datadog.service_management.slos;
```

## Infrastructure
### Infrastructure

Hosts reporting to Datadog, with their apps and mute state:

Expand All @@ -177,7 +181,7 @@ FROM datadog.metrics.active_metrics
WHERE "from" = strftime('%s', 'now') - 3600;
```

## Logs, audit and usage
### Logs, audit and usage

Log indexes and their retention:

Expand Down Expand Up @@ -206,7 +210,7 @@ FROM datadog.organization.usage_summary
WHERE start_month = '2026-08';
```

## Provision, mutate and tear down
### Provision, mutate and tear down

Mutations use the same SQL grammar. A v1 resource (monitor) takes its fields as columns; a v2 resource (role, API key, downtime) takes the JSON:API `data` document. A monitor end to end:

Expand Down
Loading