AnsweredAssumed Answered

ServiceRunningInstancesMax usage report metric

Question asked by khibmaesri-ca-esridist Employee on Aug 28, 2018



I've created a report using ServiceRunningInstancesMax metric -- (note, this particular metric appears to be incorrectly documented @ as ServiceActiveInstances. Attempting to use ServiceActiveInstances fails.


If I use the ServiceRunningInstancesMax metric as the only metric in a report, it works fine. As soon as I add any other metric and that other metric has a value, it'll always return 2147483647. For example, using it with RequestCount: when the RequestCount has any value greater than 0, ie, any usage, the ServiceRunningInstancesMax  because the 2147483647 value. When RequestCount =0, I get back the expect ServiceRunningInstancesMax value.


Example JSON used to create the report:


"temp": false,
"reportname": "MaxInstances",
"title": "MaxInstances",
"since": "LAST_DAY",
"queries": [{
"resourceURIs": ["services/MyService.MapServer"],
"metrics": [
"managerReport": false,
"metadata": "my report"

Example CSV output, incorrect values bolded when RequestCound >0:


TimestampServiceRunningInstancesMax of services/Service.MapServerRequestCount of services/Service.MapServer
08/27/2018 09:00:002147483647 1
08/27/2018 09:30:0040
08/27/2018 10:00:002147483647 2
08/27/2018 10:30:0040
08/27/2018 11:00:002147483647 6