Monitoring InterSystems IRIS Using REST API

Metric Descriptions

The metrics are returned in a text-based format, described in the Exposition Formats page of the Prometheus documentation (https://prometheus.io/docs/instrumenting/exposition_formats/Opens in a new tab). Each metric is listed on a single line with only one space, which separates the name from the value.

InterSystems IRIS metrics are listed in the table below. Metric names with a label appear here with line breaks to improve readability.

Interoperability Metrics

In addition to the metrics described in the previous section, an InterSystems IRIS instance can also record metrics about active interoperability productionsOpens in a new tab and include them in the output of the /metrics endpoint. The recording of these interoperability metrics is disabled by default. To enable it, you must perform the following steps for each interoperability production you want to monitor:

1. Open a Terminal session for the InterSystems IRIS instance running the production you want to monitor. If necessary, switch to the namespace associated with the production by executing the following command:

   set $namespace = "[interopNS]"
   

   

   where [interopNS] is the namespace name.

2. In the Terminal, execute the following command to enable the collection of metrics for the active production within the current namespace (SAM refers to System Alerting and MonitoringOpens in a new tab, the InterSystems monitoring solution):

   do ##class(Ens.Util.Statistics).EnableSAMForNamespace()
   

   
   Note:

   If the recording of metrics is enabled for a namespace but the corresponding production is not active, the /metrics endpoint does not return any metrics.

   The Ens.Util.Statistics class provides methods for customizing the output of the /metrics endpoint. For example, invoking the method DisableSAMIncludeHostLabel will provide aggregated metrics for the entire production instead of providing them for each host individually.

   The metrics available after completing this step are described in the Basic Interoperability Metrics table below.

3. If you would like to collect additional metrics about activity volume for a production, you must enable activity monitoring by invoking the class method Ens.Util.Statistics.EnableStatsForProduction in the corresponding namespace using the Terminal. You must also add the Ens.Activity.Operation.Local business operation to the production. This process is detailed in Enabling Activity Monitoring on the Monitoring Activity Volume page.

   The additional metrics available after completing this step are described in the Activity Volume Metrics table below.

4. If you would like to collect additional HTTP transmission metrics for an interoperability web client which uses the EnsLib.HTTP.OutboundAdapter or the EnsLib.SOAP.OutboundAdapter, you must enable the reporting of HTTP metrics for the corresponding business operation by performing the following steps:

   1. Open the Management Portal for the InterSystems IRIS instance containing the web client you want to monitor.

   2. Select Interoperability and choose the namespace containing the web client.

   3. Select Configure > Production to open the Production Configuration page.

   4. Select the operation which uses the HTTP or SOAP outbound adapter.

   5. In the Alerting Control section of the Production Settings > Settings panel, select the Provide Metrics for SAM checkbox.

   6. Select Apply to save your settings.

   The additional metrics available after completing this step are described in the HTTP Metrics table below.

   Note:

   Currently, HTTP transmission metrics are only collected for business operations which invoke actors using the Queue style (not inProc). For more information on the difference between these invocation styles, see Defining a Business Operation Class in Defining Business Operations.

InterSystems IRIS interoperability metrics are listed in the tables below. Metric names with a label appear here with line breaks to improve readability.

Create Application Metrics

To add custom application metrics to those returned by the /metrics endpoint:

1. Create a new class that inherits from %SYS.Monitor.SAM.AbstractOpens in a new tab.

2. Define the PRODUCT parameter as the name of your application. This can be anything except for iris, which is reserved for the InterSystems IRIS metrics.

3. Implement the GetSensors()Opens in a new tab method to define the desired custom metrics, as follows:

   • The method must contain one or more calls to the SetSensor()Opens in a new tab method. This method sets the name and value for an application metric. The values should be integers or floating point numbers to ensure compatibility with Prometheus and InterSystems SAM.

     You can optionally define a label for the metric, though if you do, you must always define a label for that particular metric.

     Note:

     For best practices when choosing metric and label names, see Metric and Label Naming in the Prometheus documentation (https://prometheus.io/docs/practices/naming/Opens in a new tab).

   • The method must return $$$OK if successful.

   Important:

   A slow implementation of GetSensors() can negatively impact system performance. Be sure to test that your implementation of GetSensors() is efficient, and avoid implementations that could time out or hang.

4. Compile the class. An example is shown below:

   /// Example of a custom class for the /metric API
   Class MyMetrics.Example Extends %SYS.Monitor.SAM.Abstract
   {
   
   Parameter PRODUCT = "myapp";
   
   /// Collect metrics from the specified sensors
   Method GetSensors() As %Status
   {
      do ..SetSensor("my_counter",$increment(^MyCounter),"my_label")
      do ..SetSensor("my_gauge",$random(100))
      return $$$OK
   }
   
   }

   

5. Use the AddApplicationClass()Opens in a new tab method of the SYS.Monitor.SAM.ConfigOpens in a new tab class to add the custom class to the /metrics configuration. Pass as arguments the name of the class and the namespace where it is located.

   For example, enter the following in the Terminal from the %SYS namespace:

   %SYS>set status = ##class(SYS.Monitor.SAM.Config).AddApplicationClass("MyMetrics.Example", "USER")
   
   %SYS>w status
   status=1
   

   

6. Ensure that /api/monitor web application has the necessary Application Roles to access the custom metrics. For details on how to edit application roles, see Edit an Application: The Application Roles Tab.

   This step grants /api/monitor access to the data needed for the custom metric. For example, if the custom metric class is located in the USER database (protected by the %DB_USER resource), grant /api/monitor the %DB_USER role.

7. Review the output of the /metrics endpoint by pointing your browser to http://<instance-host>:52773/api/monitor/metrics (where 52773 is the default WebServer port). The metrics you defined should appear after the InterSystems IRIS metrics, such as:

   [...]
   myapp_my_counter{id="my_label") 1
   myapp_my_gauge 92
   

The /metrics endpoint now returns the custom metrics you defined. The InterSystems IRIS metrics include an “iris_” prefix, while your custom metrics use the value of PRODUCT as a prefix.