timeRange absolute 400 Bad Request

Retired Member — Wed, 02 Sep 2020 18:12:13 GMT

Hi,

Am trying to fetch alerts based upon an absolute timerange to ensure I don't continuously run into timeouts with my queries (want to get all open alerts for long running accounts that customers never looked at or that simply have way too many misconfigured resources). Whenever I execute the call I however keep running into 400 Bad Request statuses, and seem to be blind for my mistake. The call I'm trying to execute is the following:

curl -X POST \ '<a href="https://api2.redlock.io/v2/alert?alert.status=open&detailed=true" target="_blank">https://api2.redlock.io/v2/alert?alert.status=open&detailed=true</a>' \ -H 'Content-Type: application/json' \ -H 'Host: api2.redlock.io' \ -H 'x-redlock-auth: my-very-special-secret-auth-key' \ -d '{ "timeRange": { "type": "absolute", "value": { "startTime": 1572244614366, "endTime": 1569649014366 } } }'

When attempting it with a GET request to the below URL (of course with the x-redlock-auth header set) it also returns a 400 Bad Request. When using relative time of 1 month it just works as expected.

<a href="https://api2.redlock.io/v2/alert?alert.status=open&timeType=absolute&startTime=1572244614366&endTime=1569649014366&detailed=true" target="_blank">https://api2.redlock.io/v2/alert?alert.status=open&timeType=absolute&startTime=1572244614366&endTime=1569649014366&detailed=true</a>

Regards

Re: timeRange absolute 400 Bad Request

ebeuerlein — Mon, 28 Oct 2019 19:30:17 GMT

Your start time is Oct 28th and your end time is Sept 28th. Have you tried flipping the values to see if it still results in a 400?

Re: timeRange absolute 400 Bad Request

Retired Member — Tue, 29 Oct 2019 07:12:13 GMT

Thanks @ebeuerlein! Did I mention I seemed to be blind for my own mistake?

topic timeRange absolute 400 Bad Request in Prisma Cloud Discussions

timeRange absolute 400 Bad Request

Re: timeRange absolute 400 Bad Request

Re: timeRange absolute 400 Bad Request