Closed mdb closed 9 months ago
Thank you, @mdb, for highlighting this issue to us. Rest assured, we will investigate it thoroughly. 👍
Thank you, @mdb, for highlighting this issue to us. Rest assured, we will investigate it thoroughly. 👍
@ParthaI I hope you don't mind; I took a stab at a fix over in https://github.com/turbot/steampipe-plugin-datadog/pull/48.
Because datadog_monitor does not perform paginated requests when calling the Datadog API /api/v1/monitor endpoint, the request can often fail for organizations with a large volume of monitors.
For example...
Using following
query.sql
:...results in an HTTP 504 from the Datadog API when the targeted organization has a large volume of monitors, which renders
datadog_monitor
unusable:Describe the solution you'd like
I believe the HTTP 504 could be avoided if the
steampipe-plugin-datadog
issued the request(s) with apage_size
query parameter, and fetched the monitors in smaller batches via distinct, per-page HTTP requests.