ArcGIS server does not report any ServiceActiveInstances report usage

Question

I'm writing scripts to collect usage data from ArcGIS Server in order to generate reports. I used this Esri suport page to develop such scripts. For simplicity, suppose the following json as my REST data to create an usage report: { "reportname": "my_debug_report", "since": "LAST_DAY", "queries": [{ "metrics": ["RequestCount", "ServiceActiveInstances"], "resourceURIs": ["services/MOSAICO/MOSAICO_ORTOFOTO_OESTE_2010.ImageServer"] }] }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I receive then the following data: TimestampRequestCount of services/MOSAICO/MOSAICO_ORTOFOTO_OESTE_2010.ImageServerServiceActiveInstances of services/MOSAICO/MOSAICO_ORTOFOTO_OESTE_2010.ImageServer147731760000015NO SUCH METRIC SUPPORTED: ServiceActiveInstances147731940000019NO SUCH METRIC SUPPORTED: ServiceActiveInstances14773212000000NODATA14773230000000NODATA14773248000000NODATA14773266000000NODATA14773284000000NODATA147733020000042NO SUCH METRIC SUPPORTED: ServiceActiveInstances14773320000000NODATA147733380000036NO SUCH METRIC SUPPORTED: ServiceActiveInstances14773356000000NODATA14773374000000NODATA14773392000000NODATA147734100000032NO SUCH METRIC SUPPORTED: ServiceActiveInstances14773428000000NODATA14773446000000NODATA14773464000000NODATA14773482000000NODATA14773500000000NODATA14773518000000NODATA14773536000000NODATA14773554000000NODATA14773572000000NODATA14773590000000NODATA14773608000000NODATA14773626000000NODATA14773644000000NODATA14773662000000NODATA14773680000000NODATA14773698000000NODATA14773716000000NODATA14773734000000NODATA14773752000000NODATA14773770000000NODATA14773788000000NODATA14773806000000NODATA14773824000000NODATA14773842000000NODATA14773860000000NODATA14773878000000NODATA14773896000000NODATA14773914000000NODATA14773932000000NODATA14773950000000NODATA14773968000000NODATA14773986000000NODATA14774004000000NODATA14774022000000NODATA ---- Updates from 2016/10/26 Using the server manager, I could generate the following report: Despite of the Portuguese stuff, this report is from the same service witch I requested the json at the beginning of this post. In order to learn more about how the web manager do its job, I sniffed the network to capture the json request that generated this manage report and for my surprise I got this json: { "reportname": 1477487802255, "since": "LAST_DAY", "queries": [{ "resourceURIs": ["services/SISGEOPOLIS/LinhaTrecho23.MapServer"], "metrics": ["ServiceRunningInstancesMax"] }], "metadata": { "temp": true, "tempTimer": 1477488074129 } }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ A strange thing here. Please take attention to the metrics array: I don't even know about the ServiceRunningInstancesMax. This official esri doc page was supposed to mention that but it does not. Question 1: since there were service usage, why is ServiceActiveInstances not supported ? Question 2: Where can I find an up to date documentation about admin usage reports which mentions all metrics, including ServiceRunningInstancesMax ?

PlinioSantos · Answer

In my opinion is unacceptable an official help page contains wrong information. And even more unacceptable the ServiceRunningInstancesMax metric result only be correct when collected alone. I have a bunch of reporting scripts that rely in those statistics and I'm astonished to know that it is incorrect. Thant you for point out that.

PS: In fact I noticed that some usage reports of ServiceRunningInstancesMax where returning 2147483647 but so far I was discarding them without look into the other values.

nicogis · Answer

The documentation  seems wrong. The metrics is 'ServiceRunningInstancesMax' and not

'ServiceActiveInstances'

The help link is http://resources.arcgis.com/en/help/arcgis-rest-api/02r3/02r30000027n000000.htm

I noticed another problem: if there is only this metric the result is correct, but if it is with other metrics the result of ServiceRunningInstancesMax is incorrect

I have made a console (c#) that you can schedulate that create excel file from usagereport https://github.com/nicogis/UsageReports/releases