Skip to main content
Version: 2025.02

SAP IDM Monitor

Monitoring of SAP Identity Management dispatchers, job logs, provisioning queue, packages, identities

General

ExecutableSAP_IDM_Monitor.exe
Connection methodODBC
Ports
  • 5000 (ASE)
  • 1521 (Oracle)
  • 1433 (MSSQL)
Lookup files
  • itesys.sapidmmonitor.dispatcherloglevel.ovl
  • itesys.sapidmmonitor.dispatcherstate.ovl
  • itesys.sapidmmonitor.housekeepingstate.ovl

Default parameters

Parameter namePossible valuesDefaultDescription
Host<ip> | <hostname>emptyHostname or IP of the target system. If you use a virtual hostname on your SAP servers, please use also the virtual host to connect.
DBNamestringemptyName of the database
DBUsernamestringemptyDatabase user
DBPasswordstringemptyPassword of the database user

Sensor-specific parameters

Parameter namePossible valuesDefaultDescription
DBTypeASE | ORACLE | MSSQLASEDefines which database type is used
DBSchemaPrefixstringMXMC_db.dbo

Schema prefix of the IDM database

  • ASE: Usually MXMC_db.dbo
  • ORACLE: Usually MXMC_OPER
  • MSSQL: Usually MXMC_db.dbo
Minutesnumber60Count of past minutes to check for job logs
AdditionalQueries<file1>,<file2>,<file3>,…NONE

Additional queries to create custom channels. The queries have to be specified as .sql files in the folder SAP_IDM_Monitor.


File syntax:

  • The channel will be named after the filename without .sql
  • The unit of the returned value can be defined in the first line of the sql file as follows:
    Unit=<Unit>[:f]
    (:f is optional to define if the value is a float value)
    Example: Unit=Percent:f (Unit is defined as Percent and the value is handled as float)
CustomOnlyfalse | truefalseDefines wether only the queries from the AdditionalQueries parameter should be used.

Channels

Channel nameDescriptionLookup file
Dispatcher <Name> stateCurrent state of the dispatcher <Name>. The state of a dispatchers where the LAST_VISITED timestamp is older than two minutes will be recognized as UNKNOWN.itesys.sapidmmonitor.dispatcherstate.ovl
Dispatcher <Name> JRE log levelCurrent JRE log level of the dispatcher <Name>itesys.sapidmmonitor.dispatcherloglevel.ovl
Log errorsNumber of errors in the job log within the past <Minutes>
Log warningsNumber of warnings in the job log within the past <Minutes>
Checked-out packagesNumber of checked-out packages. (The checked-out packages and the current developer are also shown in the sensor message.)
Entries in provisioning queueNumber of entries in the provisioning queue
ID Store <Name> active identitiesNumber of active identities per ID store
Inactive RepositoriesNumber of inactive repositories
Housekeeping statusDisplays the status of enabled housekeeping jobs. A job with an empty schedule time will be recognized as failed.
Jobs/Tasks in error stateDisplays the count of jobs and tasks in status error.
<AdditionalQuery>Result of additional query defined in a .sql file for the parameter <AdditionalQueries>

Preparation

If you use a monitoring user which has no access to the Identity Management database schema, please use the following SQL commands to give the necessary access:

grant select on mc_dbschema to <user>
grant select on MC_Dispatcher to <user>
grant select on MC_LOGS to <user>
grant select on mc_jobs to <user>
grant select on mc_package to <user>
grant select on MXP_Provision to <user>
grant select on idmv_vallink_basic_active to <user>
grant select on MXI_IDStores to <user>
grant select on mc_proc to <user>
grant select on MC_REPOSITORY to <user>
warning

Also check permissions for additional queries you defined in the parameter <AdditionalQueries>.

Important notes

warning

Please check the limits if they fit for your alerting.

Changelog

VersionChanges
2024.04Fixed bug during check of dispatcher state by LAST_VISITED date
2024.01
  • Added possibility to define additional queries
  • Added parameter CustomOnly to use the sensor with custom queries only
2023.03Corrected selection of logs when using Oracle database.
2022.08
  • Added channel for number of inactive repositories
  • Added channel for housekeeping status
  • Improved dispatcher status check regarding the LAST_VISITED flag in the database
2021.06
  • Collecting information via database instead of SSH
  • New channel for log errors and warnings
  • New channel for checked-out packages
  • New channel for count of entries in provisioning queue
  • New channel for count of active identities per ID store
  • New channel for dispatcher JRE trace level
1.4.1.2First stable release.