Monitoring of REST service connections and threads by using profile tables

You can monitor the connections and threads of HTTP REST service requests by setting special registers and global variables in the profiles.

Db2 system profile monitoring can use the following filtering criteria to monitor Db2 RESTful services requests:

• IP address or domain name, in the LOCATION column.
• Product identifier, in the PRDID column. The current PRDID value used for Db2 native REST services is:
  • 'HTP01010' for non-secure HTTP URL connections
  • 'HTS01010' for HTTPS/secure connections.
• Role and authorization identifier, in both ROLE and AUTHID columns.
• Role, in the ROLE column only.
• Authorization identifier, in the AUTHID column only.
• Collection identifier and package name (Service name), in both COLLID and PKGNAME columns.
• Collection identifier, in the COLLID column only.
• Package name (Service name), in the PKGNAME column only.
• Client application name, in the CLIENT_APPLNAME column.
• Client user identifier, in the CLIENT_USERID column.
• Client workstation name, in the CLIENT_WRKSTNNAME column.

Other criteria combinations are not accepted.

System monitor profile exception queuing is not supported for Db2 native REST requests. If a system monitor profile EXCEPTION level threshold is met for an incoming Db2 native REST request, the REST request will be rejected.