The DaaS management appliances allow monitoring via the standard WBEM (web-based enterprise management)/CIM (common information model) interface.
You can install the wbemcli client, which can be used with queries or with plugin scripts in conjunction with tools like Nagios for monitoring. You can also use any tool which supports WBEM/CIM management, such as open source clients like OpenPegasus browser client, CImNavigator, openPegasus CLI client, and MS CIM Studio. The DaaS platform, however, has only been tested with the wbemcli client tool for CIM data verification.
Note the following:
For security purposes, the only account that has access to CIM monitoring services is cim-user. You set the password for this account during the bootstrap process. As a result, scripts and plugins must be updated to specify the cim-user credentials. For example:
wbemcli -noverify -nl -v ei 'https://cim-user:Desktonefirstname.lastname@example.org:5989/root/cimv2:Desktone_InstalledProduct'
Small Footprint CIM Broker (SFCB) uses the appliance certificate instead of a self-signed certificate, enabling the client to verify the certificate/server identity. As a result, queries to CIM providers can be made by specifying the platform public CA file or adding it as a trusted certificate on the client machine. This change is optional, but it is recommended that clients be updated. The Service Provider administrator can pull the public CA certificate (/usr/local/desktone/cert/rootCA.pem) from the SP appliance. The public CA certificate is common for all appliances. For example:
wbemcli --cacert /etc/daas-cim/client.pem -nl -v ei 'https://cim-user:Desktoneemail@example.com:5989/root/cimv2:Desktone_InstalledProduct'Note:
The copied rootCA.pem is renamed client.pem in example above. This renaming is not necessary.