Yes, you can do it.
I don't know if it is documented, but, here's how you can do it:
First query the set of "custom reports" you have in your org:
GET ${mgmtserver}/v1/organizations/${ORG}/reports
From that you will get a list of mappings from name to id. The friendly human-readable name of the custom report, to the ID, which is a uuid. Suppose you want to download the data for the custom report with ID da94c72e-e028-43cc-b4ea-ba241e703a69 . You first must get the details for the report:
GET ${mgmtserver}/v1/organizations/${ORG}/reports/${reportid} The result of that is something like this:
{
"chartType" : "column",
"comments" : [ ],
"createdAt" : 1574475520000,
"createdBy" : "dchiesa@google.com",
"dimensions" : [ "apiproxy" ],
"displayName" : "testReport3",
"environment" : "prod",
"lastModifiedAt" : 1574475520000,
"lastModifiedBy" : "dchiesa@google.com",
"lastViewedAt" : 1574475520000,
"metrics" : [ {
"function" : "avg",
"name" : "target_response_time"
}, {
"function" : "avg",
"name" : "total_response_time"
} ],
"name" : "da94c72e-e028-43cc-b4ea-ba241e703a69",
"organization" : "gaccelerate3",
"properties" : [ {
"property" : "__ui__",
"value" : [ {
"name" : "description"
}, {
"name" : "accuracy"
} ]
} ],
"sortbyCols" : [ ],
"tags" : [ ],
"timeUnit" : "hour"
}
Then you must submit an async query for that report . To do so you must map the metrics and dimensions into a new payload, and supply the time range The result is a POST, like this:
POST ${mgmtserver}/v1/organizations/${ORG}/environments/${ENV}/queries \
-H content-type:application/json \
-d '
{
"metrics": [
{
"function": "avg",
"name": "target_response_time"
},
{
"function": "avg",
"name": "total_response_time"
},
{
"function": "sum",
"name": "message_count"
}
],
"dimensions": [
"apiproxy"
],
"timeRange": {
"start": "2020-02-03 22:12:00",
"end": "2020-02-03 23:12:00"
},
"name": "testReport3",
"outputFormat": "csv",
"reportDefinitionId": "da94c72e-e028-43cc-b4ea-ba241e703a69",
"groupByTimeUnit": "minute"
}'
That kicks off an "Asynchronous query". The response from that is a payload that tells you where to look. It's like this:
{
"self" : "/organizations/ORG/environments/ENV/queries/QUERYID",
"state" : "enqueued",
"created" : "2020-02-03T23:23:55Z"
}
Then, just poll that query to get the results:
GET ${mgmtserver}/v1//organizations/ORG/environments/ENV/queries/QUERYIDEventually you will see a payload that tells you the report is ready:
{
"self" : "/organizations/ORG/environments/ENV/queries/QUERYID",
"state" : "completed",
"result" : {
"self" : "/organizations/ORG/environments/ENV/queries/QUERYID/result",
"expires" : "2020-02-10T23:24:09Z"
},
"resultFileSize" : "0.08 KB",
"resultRows" : "0",
"executionTime" : "6 seconds",
"created" : "2020-02-03T23:23:55Z",
"updated" : "2020-02-03T23:24:09Z"
}
And then finally just retrieve the "result.self" URL, and you will get a ZIP containing .... uh.... a gzip... which contains.... a file which contains a set of JSON records. You will need to unpack and parse that yourself.
Keep in mind this would count against your entitled allotment of async reports for a given month/quarter, etc.
LinkedIn
Twitter
