Back to ITRS Internal Only FAQ

Internal documentation only

This page has been marked as draft.

ITRS Analytics (Obcerv) - license generation

Preparation Copied

  1. The ITRS account needs to have access to the Licence Tool.
  1. Check with sales team that Sales Force / Omni records have been updated.
  1. Check with customer to obtain Instance ID used to install ITRS Analytics.

Replicated Portal (optional) Copied

It is useful to check if the user organization has been registered in the Replicated portal (Login link: https://iam.itrsgroup.com/auth/realms/itrsgroup/protocol/saml/clients/replicate). While this step is not necessary for license generation, this is needed to provide downloads of ITRS Analytics packages.

Procedure Copied

  1. Navigate to this site: https://resources.itrsgroup.com/admin/config/itrs_licence_tool/licence_tool

  2. Enter the Customer name and select from the available drop-down options.5143592563613 mceclip0

  3. Click the Show Opportunities button.

  1. Currently there is no need to set the Licence Effective Date option.

  2. Select an appropriate Licence Type (Trial / Production).

  3. Input Instance ID name.5143476550941 mceclip2

  4. Select all the Obcerv related Entitlements check boxes.

  5. Select Download License and provide the generated license file to the user.

  1. Depending on the Licence Type, the date will be displayed with the opportunity, ITRS Analytics (Obcerv) - license generation The Start and End (in yellow box) is for Production licence. The POC Start /POC End is for Trial licence

Licence Installation Copied

Troubleshooting Copied

  1. The license file is in JSON format which can be opened with text editors. It can be difficult to read though as the data is stored on a single line. You may use the “jq” command or appropriate tools to look at the contents. e.g.
cat licence_1751234567.json | jq
  1. The license file is processed by the “licenced” pod as of this writing. From a support bundle, you may scroll through the log or search keywords for hints. e.g.
kubectl get pod -n kotsadm | grep licenced
kubectl logs licenced-7d59d59b96-tpfs5 -n kotsadm | grep instance_id
  1. The licence “entitlements” reported on ITRS Analytics web console may not match exactly with codes in the license generator, since the licence tool includes additional logic. There is currently no official documentation on the mapping logic.

We have reverse engineered the process by creating dummy licenses to obtain below sample output.

License Tool Code License File JSON Output (as of 27 Nov 2025)
OBCERV (featureEntitlement) agents ai alerting audit capacity capacity-planner centralised-config commands dashboard dynamic-thresholds entity-viewer fixmonitor iam ingestion notifications obcerv-app-alerting obcerv-app-capacity-planner obcerv-app-entities obcerv-app-system-overview obcerv-app-webconsole service-analyser signal-forecaster system-overview traces
OBCERV-APP-API-GATEWAY (featureEntitlement) obcerv-app-api-gateway
OBCERV-APP-SIGNAL-FORECASTER (no effect)
OBCERV-SAAS (no effect)
OBCERV-STORAGE-AWSEC2 (resourceEntitlement) obcerv-storage-awsec2
OBCERV-STORAGE-NETPROBE (resourceEntitlement) obcerv-storage-netprobe
OBCERV-STORAGE-OPSVIEWHOST (resourceEntitlement) obcerv-storage-opsviewhost
OBCERV-STORAGE-POD (resourceEntitlement) obcerv-storage-pod

Please check with products or development teams if customer reports the licence does not work as expected. (ITRS Analytics may add more apps in the future, the license generator may be updated to include more tokens although it is the same opportunity.)

["Geneos"] ["FAQ"]

Was this topic helpful?