Example query results

Adding Table for SLO's

Adding an SLO table to allow the user to search SLO's in DataDog and query based on various aspects of the SLO, like targets or timeframes. This is my first time committing a table to this plugin, So if anything needs to be changed more than happy to tweak it. I followed what was set up in the DataDog monitor and plan to continue to add a table for SLO history.

select
  name,
  thresholds
from
  datadog_slo
where
  type in ('monitor') and
  thresholds @> '[{"timeframe":"90d"}]'::jsonb
limit 5;

+-----------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| name                                                | thresholds                                                                                                                                                                                                                                      |
+-----------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Datatech_sql_Host_uptime SLO                        | [{"target":99,"target_display":"99.","timeframe":"90d"}]                                                                                                                                                                                        |
| Kafka: Offline Partitions                           | [{"target":99.9,"target_display":"99.9","timeframe":"7d"},{"target":99.9,"target_display":"99.9","timeframe":"30d"},{"target":99.9,"target_display":"99.9","timeframe":"90d"}]                                                                  |
| Retriever: chatNodeJsErrorLogs by minute (Clone)    | [{"target":99.9,"target_display":"99.9","timeframe":"90d","warning":99.95,"warning_display":"99.95"}]                                                                                                                                           |
| Kafka SLI: Produce request latency                  | [{"target":95,"target_display":"95.","timeframe":"7d","warning":98,"warning_display":"98."},{"target":95,"target_display":"95.","timeframe":"30d","warning":98,"warning_display":"98."},{"target":95,"target_display":"95.","timeframe":"90d"}] |
| Kafka SLI: Consume request latency                  | [{"target":95,"target_display":"95.","timeframe":"7d","warning":98,"warning_display":"98."},{"target":95,"target_display":"95.","timeframe":"30d","warning":98,"warning_display":"98."},{"target":95,"target_display":"95.","timeframe":"90d"}] |
+-----------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Hi there, First thank you for this nice plugin!

Here a suggestion to add a table: to get the list of hosts (infrastructure_hosts)

Have a nice day,

References https://docs.datadoghq.com/developers/guide/query-the-infrastructure-list-via-the-api/

Tables added

+------------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| table                              | description                                                                                                             |
+------------------------------------+-------------------------------------------------------------------------------------------------------------------------+
| datadog_host                       | A host is any piece of infrastructure that runs an instance of the Datadog Agent such as a bare metal instance or a VM. |
+------------------------------------+-------------------------------------------------------------------------------------------------------------------------+

Closes: #19

This is my first steampipe contribution so I expect I might have overlooked some things but I've tried to adhere to the style of the existing tables where possible.

There are a few things worth pointing out:

• While I've tried to wire up pagination properly, my workplace doesn't actually have enough hosts to properly test that it actually works (the page limit is 1000+)
• I don't really understand the specifics of hydration when it comes to the absence of something. The Datadog hosts API will apparently serve results for any host that is live within the last 3 hours by default. Presumably if you were to open Steampipe, close it then open it again in a week, Steampipe would still retain older hosts rather than magically setting up to false. If Steampipe removes an entry from the table upon trying to rehydrate it and getting a 404, then this isn't such a big deal but either way, it kind of makes the up field redundant if it is always set to true
• While I tried to craft some more "Advanced" queries, I'm not that great with SQL so some queries can probably be rewritten to be less complex
• I haven't mapped host_name, which is available in the hosts API, as it appears to contain the exact same data as name based on the description.

Anyway, I didn't worry too much about the edge cases since they can be ironed out over time I'm sure.

You can do quite a lot of fun queries by making use of jsonb which I've heard about for a few years now but I've never actually seen it in action before now.

References Add table to get details of metrics in realtime

https://github.com/DataDog/datadog-api-client-go/blob/master/api/v2/datadog/docs/MetricsApi.md#metricsapi https://github.com/DataDog/datadog-api-client-go/blob/master/api/v1/datadog/docs/MetricsApi.md#metricsapi

References Add table to get details of metrics in realtime

https://github.com/DataDog/datadog-api-client-go/blob/master/api/v2/datadog/docs/MetricsApi.md#metricsapi https://github.com/DataDog/datadog-api-client-go/blob/master/api/v1/datadog/docs/MetricsApi.md#metricsapi

The api_url of the configuration file has currently no effect. The way to change the server has documented on the datadog-api-client-go is to set the site property, see https://github.com/DataDog/datadog-api-client-go#changing-server

I thought it would be easier to rename the current configuration property from api_url to server has multiple values are possible (datadoghq.com us3.datadoghq.com us5.datadoghq.com datadoghq.eu ddog-gov.com).

Example query results

Time: 8.975788ms
+-----------------------+--------------------------------------+
| name                  | id                                   |
+-----------------------+--------------------------------------+
| Subhajit Kumar Mondal | 0f550528-30e1-11ec-9255-da7ad0900002 |
| turbot-router-events  | f0717bea-30b4-405a-9c8f-34f0b3d28804 |
| <null>                | 252dcb01-30e1-11ec-9255-da7ad0900002 |
| <null>                | 130f3218-38b8-11ec-9b20-da7ad0900002 |
| Lalit Bhardwaj        | 45c9984e-30a0-11ec-9224-da7ad0900002 |
+-----------------------+--------------------------------------+
> select name, id from datadog_eu.datadog_user

Time: 1.031153257s
+----------------+--------------------------------------+
| name           | id                                   |
+----------------+--------------------------------------+
| Lalit Bhardwaj | 26506476-4765-11ec-9a52-da7ad0900005 |
+----------------+--------------------------------------+

Connection config

connection "datadog" {
  plugin  = "datadog"
  api_key = "reacted"
  app_key = "reacted"
}

connection "datadog_eu" {
  plugin  = "datadog"
  api_key = "reacted"
  app_key = "reacted"
  api_url = "https://api.datadoghq.eu/"
}

Describe the bug

> select name, id from datadog_eu.datadog_user
Error: rpc error: code = Internal desc = hydrate function listUsers failed with panic runtime error: invalid memory address or nil pointer dereference
> select name, id from datadog.datadog_user

Time: 7.954036ms
+-----------------------+--------------------------------------+
| name                  | id                                   |
+-----------------------+--------------------------------------+
| <null>                | 130f3218-38b8-11ec-9b20-da7ad0900002 |
| <null>                | 252dcb01-30e1-11ec-9255-da7ad0900002 |
| turbot-router-events  | f0717bea-30b4-405a-9c8f-34f0b3d28804 |
| Lalit Bhardwaj        | 45c9984e-30a0-11ec-9224-da7ad0900002 |
| Subhajit Kumar Mondal | 0f550528-30e1-11ec-9255-da7ad0900002 |
+-----------------------+--------------------------------------+

Steampipe version (steampipe -v) Example: v0.9.0

Plugin version (steampipe plugin list) Example: v0.0.1

To reproduce setup connection config

connection "datadog_eu" {
  plugin  = "datadog"
  api_key = "reacted"
  app_key = "reacted"
  api_url = "https://api.datadoghq.eu/"
}

Tables Added

+------------------------------------+-------------------------------------------------------------------------------------------------------------------+
| table                              | description                                                                                                       |
+------------------------------------+-------------------------------------------------------------------------------------------------------------------+
| datadog_dashboard                  | A dashboard is Datadog’s tool for visually tracking, analyzing, and displaying key performance metrics.           |
| datadog_integration_aws            | Datadog AWS integration resource.                                                                                 |
| datadog_log_event                  | Datadog log events are records of notable changes in your environments.                                           |
| datadog_logs_metric                | Log-based metrics are a cost-efficient way to summarize log data from the entire ingest stream.                   |
| datadog_monitor                    | A monitor provides alerts and notifications if a specific metric is above or below a certain threshold.           |
| datadog_permission                 | Permissions provide the base level of access for roles.                                                           |
| datadog_role                       | Roles categorize users and define what account permissions those users have.                                      |
| datadog_security_monitoring_rule   | Security monitoring rules define conditional logic that is applied to all ingested logs and cloud configurations. |
| datadog_security_monitoring_signal | Signals are threats detected based on a security monitoring rule.                                                 |
| datadog_user                       | A user belongs to an organization and can be assigned roles.                                                      |
+------------------------------------+-------------------------------------------------------------------------------------------------------------------+

Integration test logs

Add passing integration test logs here

Example query results

Add example SQL query results here (please include the input queries as well)

output.txt v