Documentation Connector for SLM 1.00

Transcription

1 Connector for SLM 1.00

2 Home Release notes Get an insight of the latest features and everything that is new in this version. Get started Initiate your understanding on the concepts of Operations Connector for SLM. Install Use these procedures to install, set up, and configure Operations Connector for SLM. Upgrade Use these procedures to upgrade from previous versions to current version. Administer Use this section to set up and administer Operations Connector for SLM.

3 Troubleshoot Resolve problems that you may encounter while using Operations Connector for SLM. Develop Use these resources to develop solutions and maximize the utility of APIs.

4 Release Notes This section provides information about the new features of Operations Connector for SLM Whats new in Connector for SLM 1.00 OpsCx for SLM provides the following functionality: Collection of SLM metrics from the OMi server and stores into the Operations Agent database. Topology self-discovery, the self-discovery policy retrieves topology data about the SLM integration environment itself. The Operations Manager i (OMi) has been renamed to Operations Bridge Manager (OBM) with the release. <comments voting="plus" />

5 Get started This section provides information about key concepts of operations Connector for Service Level Management (OpsCx for SLM). Service Level Management (SLM) helps you define, track, and report on service levels from a business perspective. SLM gives you reports that let you measure and monitor application service levels against business objectives, define realistic, quantifiable service-level objectives, and track performance in real time. SLM enables you to report on performance to ensure that your IT environment is meeting the set expectations. Product Concepts OpsCx for SLM provides the following functionality: Collection of SLM metrics from the OMi server and stores into the Operations Agent database. The Operations Manager i (OMi) has been renamed to Operations Bridge Manager (OBM) with the release. Topology self-discovery, the self-discovery policy retrieves topology data about the SLM integration environment itself. The following image is a sample for SLM integration self-discovery:

6 <comments voting="plus" />

7 Install This section provides information on the following to help you install and configure OpsCx for SLM: Support Matrix Installation tasks Post-installation tasks Uninstall <comments voting="plus" />

8 Support Matrix Before installing OpsCx for SLM, go through a list of the Supported Systems Management Applications and consider the Supported Application Software prerequisites. Supported Systems Management Applications OpsCx for SLM supports the following systems management applications and their versions: Application Application Performance Management (SLM) 9.30 Supported Versions Supported Application Software The sections that follow list the prerequisites that need to be fulfilled to enable installation of OpsCx for SLM. Before you install OpsCx for SLM, the following software applications must be installed and configured. Application Operations Manager i (OMi) Operations Agent Required Version or later The Operations Manager i (OMi) has been renamed to Operations Bridge Manager (OBM) with the release onwards JDK 1.8 version or above should be installed on the Operations Agent system. For information on installation and configuration, see the corresponding documentation. Other Prerequisites and Requirements To configure and administer OpsCx for SLM, familiarize yourself with OBM. For example, you can learn how to customize Aspects and Policies. For more information, see the OBM documentation. Conventions Used in the Installation, Configuration, and Other Procedures The following placeholders are used in the instructions throughout this document. When performing the steps specify the actual value in place of each placeholder. Placeholder Meaning (Default) Values, Examples, Notes Version Product version string of OpsCx for SLM: major version, minor version, and build number. Example: This string represents the version and the build number 41.

9 OvInstallDir OvDataDir Program installation directory of Operations Agent that is used by OpsCx for SLM. Default value (Windows): C:\Program Files\HP\HP BTO Software Value (Linux): /opt/ov Default value (Windows): Data installation directory C:\ProgramData\HP\HP BTO Software of Operations Agent that The C:\ProgramData directory is hidden by default. is used by OpsCx for SLM. Value (Linux): /var/opt/ov All paths in this document use slashes (/) as path delimiters except in contexts where the operating system specifics are stated. When performing the steps use the path delimiters that your operating system supports. <comments voting="plus" />

10 Installation tasks Installation of OpsCx for SLM consists of the following tasks. 1. Download OpsCx for SLM. 2. Install OpsCx for SLM. Download Ops Connector for SLM Perform the following steps to download OpsCx for SLM. 1. Download the Operations Connector for Service Level Management Content Pack from the following website: Unified Marketplace. 2. The software package contains the file OperationsConnector_for_SLM.zip. Install Ops Connector for SLM 1. Copy the OperationsConnector_for_SLM.zip file to location of your choice on the OBM Data Processing Server host, and unpack the archive. 2. Go to the location of the unpacked archive and run the following command on the respective operating system hosts: For Windows: cscript OpsCxInstall.vbs -i For Linux: OpsCxInstall.sh -i (Provide executable permission to the OpsCxInstall.sh file before running the script.) Verify Ops Connector for SLM Installation To verify the OpsCx for SLM artifacts, perform the following: 1. On the OBM console, go to Administration > Setup and Maintenance > Content Packs. 2. Select Operations Connector for SLM from the Content Pack Definitions pane. The Operations Connector for SLM - Details pane displays the summary information about OpsCx for SLM. Also, the Problems Found field displays a message No problems found. 3. On the OBM console, go to Administration > Monitoring > Management Template and Aspects. 4. In the Configuration Folders pane: Configuration Folders > Operations Connector > SLM, click Aspects to verify if OpsConnector for SLM Configuration is created. <comments voting="plus" />

11

12 Post-installation tasks This section describes how to configure the OpsCx for SLM. To complete the configuration, execute the instructions in the following sections: 1. Deploy Management Templates 2. Configuration Options Deploy Management Templates To deploy the Management Template, follow these steps: 1. Log on to OBM console. 2. Go to Administration > Monitoring > Management Templates & Aspects. 3. Select the following in the Configuration Folders pane: Configuration Folders > Operations Connector > SLM > Aspects. Expand the folders if required. 4. In the Management Templates & Aspects pane, expand the OpsConnector for SLM Configuration. Select a required version of the Management Template. 5. Click Assign and Deploy Item icon. The Assign and Deploy wizard appears. 6. In the Configuration Item tab, select the system to which you want to assign the management template and then click Next. 7. In Required Parameters tab, perform the following steps: 1. Double-click Value for SLM Hostname. The Parameter: SLM_Hostname appears. Type the SLM host name the FQDN of the server and click OK. 2. Double-click Value for SLM Username. The Parameter: SLM_Username appears. Type the SLM Domain Manager API user name and click OK. 3. Double-click Value for SLM password. The Parameter: SLM_password appears. Type the SLM API password and click OK. Make sure to update the Java path in the Configuration parameter. For more information, see Configuration Options topic. 8. Click Next in the Required Parameters tab. 9. (Optional) In Parameter Summary, click Show Expert Parameter icon. The Expert Parameters will be listed. These parameters will have default values defined. You may customize these values as required or continue to use the default values. For the list of parameters and more information on the parameters, see Configuration Options. 10. (Optional) Clear the Enable Assigned Objects check box in the Configure Options tab if you do not want to enable the assignment immediately. 11. Click Finish. Verify Management Template Deployment Perform the following tasks to verify the successful deployment of the Management Template:

13 1. Log on to the OBM console. 2. Go to Administration > Monitoring > Deployment Jobs. The Deployment Job page should be blank to indicate a successful deployment. On the successful deployment of the OpsCx for SLM, the data source OPSCX_SLM gets created in the Operations Agent datastore. For more information on the tablename and the fields, see Develop section. Configuration Options This section describes configurable options for integrating SLM withopscx for SLM. All options are configured with default values you can modify. Option Policy Parameters HTTP SCHEMA JAVA PATH Log Level SLM SERVER TIMEZONE CustomerID SLA CONFIGURATION DATA SLA CONFIGURATION DATA POLLING INTERVAL SLA CONFIGURATION DATA SLAID CALCULATION RESULT CI ID CALCULATION RESULT CALENDAR ID CALCULATION RESULT KPI ID CALCULATION RESULT SLA ID CALCULATION RESULT WEEK CALCULATION RESULT YEAR CALCULATION RESULT DAY Description HTTP schema to be used in the SLM APIs. HTTPs for secured connection is the default. However, HTTP can be set based on the SLM API. Default value: https The path of Java installed directory on the node. Select the directory till bin. Example: C:\Program Files (x86)\java\jre1.8.0_151\bin JDK 1.8 version or above should be installed on the Operations Agent system. Log Level for OpsCx for SLM. Default: ERROR Time zone of the SLM Server. This timezone will be used to construct the startdate and enddate in SLA Calculation APIs. Default: GMT Customer ID parameter for all APIs. Default value: 1 Enable/Disable the SLA Configuration API. On disabling the SLA Configuration API response will not be fetched. Default value: Enable Polling interval for SLA Configuration API. Takes the number of hours as value. Minimum value allowed to set is 0.1. Example: meaning once in two and a half hours. Default value (numeric): 24 SLA ID Parameter to be used in SLA Configuration API. CI ID to be used in SLA Calculation Results API Call. Leave it empty for all CIs. CalendarId to be used in SLA Calculaton results API call. Leave empty for all SLA defined calendars. KPI Id to be used in SLA Calculation Results API call. Leave empty for all KPIs. SLAID is one of the parameter in SLA Calculation Results. Enable SLA Calculation Results for Weekly report view. On disabling the SLA_CalculationResults Weekly API response will not be fetched. Default value: Enable Enable SLA Calculation Results for yearly report view. On disabling the SLA_CalculationResults Yearly API response will not be fetched. Default value: Enable Enable SLA Calculation Results for Daily report view. On disabling the SLA_CalculationResults Daily API response will not be fetched. Default value: Enable

14 CALCULATION RESULT HOUR CALCULATION RESULT MONTH CALCULATION RESULT QUARTER CALCULATION RESULT WEEK POLLING INTERVAL CALCULATION RESULT DAY POLLING INTERVAL CALCULATION RESULT HOUR POLLING INTERVAL CALCULATION RESULT MONTH POLLING INTERVAL CALCULATION RESULT QUARTER POLLING INTERVAL CALCULATION RESULT YEAR POLLING INTERVAL TRACKING PERIODS TRACKING PERIODS POLLING INTERVAL TRACKING PERIODS TRACKING PERIOD ID CALENDARS CALENDARS CALENDARID CALENDARS POLLING INTERVAL KPIS KPI KPIS KPID KPIS POLLINGINTERVAL Enable SLA Calculation Results for Hourly report view. On disabling the SLA_CalculationResults Hourly API response will not be fetched. Default value: Enable Enable /Disable SLA Calculation Results for Monthly report view. On disabling the SLA_CalculationResults Monthly API response will not be fetched. Default value: Enable Enable SLA Calculation Results for Quarterly report view. On Disabling the SLA_CalculationResults Quarterly API response will not be fetched. Default value: Enable Polling interval for SLA Calculation Results Week API.Takes the number of hours as value. Example: 1 week = 24 * 7 = 168 hours Default value: 168 hours Polling interval for SLA Calculation Results day API. Takes the number of hours as value. Example: 1 day = 24 hours Default value: 24 hours Polling interval for SLA Calculation Results Hour API. Takes the number of hours as value. Minimum value allowed to set is 0.1. Example: meaning once in two and a half hours. Default value (numeric): 1 Polling interval for SLA Calculation Results Month API. Takes the number of hours as value. Example: 1 Month = 24 * 30 = 720 hours Default value: 720 hours Polling interval for SLA Calculation Results Quarter API. Takes the number of hours as value. Example: 1 Quarter = 24 * 90 = 2160 hours Default value: 2160 hours Polling interval for SLA Calculation Results Year API. Takes the number of hours as value. Example: 1 Year = 24 * 365 = 8760 hours Default value: 8760 hours Enable/Disable the Tracking period API. On disabling the Tracking Period api response will not be fetched. Default value: Enable Polling interval for Tracking Period API. Takes the number of hours as value. Example: meaning once in two and a half hours. Default value (numeric): 24 The trackingperiodid is one of the parameter in Get Tracking Periods. Enable/Disable the Calendar API. On disabling the api response will not be fetched. Default value: Enable CalendarID is one of the parameter in Get Calendars. Polling interval for Calendar API. Takes the number of hours as value. Example: meaning once in two and a half hours. Default value (numeric): 24 Enable/Disable the Kpi API. On Disabling the KPI API response will not be fetched. Default value: Enable The kpiid is one of the parameter in GET KPIS. Polling interval for Kpi API. Takes the number of hours as value. Example: meaning once in two and a half hours. Default value (numeric): 24

15 INDICATOR STATUSES INDICATOR STATUSES POLLING INTERVAL SLM HOSTNAME SLM USERNAME SLM PASSWORD DUMPRAWDATA RECORDS BATCH SIZE Self-Discovery Parameters SELF DISCOVERY SELFDISCOVERY POLLINGINTERVAL Enable/Disable the Indicator Status API. On disabling the GetIndicatorStatus APIresponse will not be fetched. Default value: Enable Polling interval for Indicator Status API. Takes the number of hours as value. Example: meaning once in two and a half hours. Default value (numeric): 24 Hostname of the SLM server. Type the FQDN of the SLM server. Rest call username for SLM Rest call password for SLM If set, will dump the API results received from SLM to the agent system for debugging. Default value: No The batch size of the records. Default value: 2500 Enable/Disable the SELF DISCOVERY. Default value: Enable Polling interval for SELF DISCOVERY. Takes the number of hours as value. Example: Once in two and a half hours. Default value (numeric): 24 <comments voting="plus" />

16 Connector for SLM:1.00/Release notes/install/uninstall This section describes how to remove the OpsCx for SLM artifacts. Complete the steps in the following order: 1. Remove the content pack from the OBM host system. 2. Remove the software from the OpsCx host system. From the OBM Console 1. In the OBM console, go to Administration > Monitoring > Assignments & Tuning. 2. From Select a view drop-down box, click Systems_Infrastructure. 3. Click on node where OpsCx for SLM is configured. 4. From the Assignments Details pane select the Assigned Item and click to remove the deployed Management Template. From the Operations Agent node 1. Log on to the Operations Agent node where the OpsCx for SLM is configured. 2. Stop the integration service by issuing the following command(s): Windows: ovc -stop slm Linux: cd /opt/ov/bin./ovc -stop slm 3. Unregister the integration service by issuing the following command(s): Windows: ovcreg -del slm Linux: cd /opt/ov/bin./ovcreg -del slm

17 Upgrade OpsCx for SLM 1.00 is the first release of the SLM Connector. There is no upgrade available since this is the first release. <comments voting="plus" />

18 Administer This section describes additional configuration information for the Operations Connector for Service Level Management. Modify or Customize the Parameters After deploying the Management Template, OpsCx for SLM allows you to customize or modify the policy's expert parameters and the out-of-the-box parameters if required. You must ensure to run the restart tool so that the changes are reflected on both the servers. After successful installation and deployment of Management Template of OpsCx for SLM you may modify the expert parameters as required. For the list of parameters and more information on the parameters, see Configuration Options topic. Follow these steps to modify or update the expert parameters: 1. Log on to the OBM console. 2. Click Administration > Monitoring > Assignments & Tuning. 3. From Select a view drop-down box, click Systems_Infrastructure. 4. Click on node where OpsCx for SLM is configured to view the Assignment Details. The Parameters are listed in Assignment Details pane. 5. Double-click on the parameter row that requires to be changed. The Parameter: <Parameter Name> box appears. 6. Type the value in the text box and click OK. Configuring OpsCx for SLM for Non-root User Mode The OpsCx for SLM can be run in a Non-root user mode. This can be achieved with the following steps: Important If the OpsCx for SLM Template is already deployed to the OBM server, the assignment should to be removed and re-deployed after switching to the non-root user. For steps to remove assignment, see Uninstall topic. 1. The Operations Agent system should be configured to run under non-root or non-local System account. For more information to switch Operations Agent to non-root user, see the Operations Agent Documentation. 2. Make sure to complete the required changes on the OBM server to support communication to a non- root user configured Operations Agent system. 3. The port used for Operations Agent (to run under non-root or non-local System account) system should also be configured in the OBM server. Perform the following steps on the Operations Agent system: 1. Run the command ovconfchg ovrg server edit.

19 2. Add the following line to the file: [bbc.cb.ports] PORTS=<FQDN>:<PORT> where,fqdn - the fully qualified domain name of the Operations Agent host. PORT - port used for Operations Agent (to run under non-root or non-local System account). 4. Restart the OBM services. Managing the Integration Service OpsCx for SLM enables you to manage its integration service OpsCx for SLM. You can start, stop and restart this service from the OBM console. See the following section for the steps to start, stop, restart the services. Starting, Stopping or Restarting the Service While you do not need to manually start or stop the integration service of OpsCx for SLM in normal circumstances, there may be cases when this action is necessary. To start or stop the integration service, perform these steps: On the OBM console: 1. Log on to the OBM web interface. 2. Click Administration > Monitoring > Assignments & Tuning. 3. From Select a view drop-down box, click Systems_Infrastructure. 4. Expand and right-click on the Operations Agent system where the OpsCx for SLM is configured. 5. Click Launch Tool. The Select Tool window appears as follows: 6. The tool provides the following options: 1. Start OpsCx for SLM Service - Click this option to start the OpsCx for SLM Service on Agent node. 2. Stop OpsCx for SLM Service - Click this option to stop the OpsCx for SLM Service on Agent node. 3. Status of ovc on Agent - Click this option to check status of ovc. 7. Click Next. The Preview window appears with the task details. 8. Click Run. 9. The Execution result displays the icon on successful execution of the service. 10. Click Close.

20 On the Operations Agent system (additional option to manage the services): 1. Open a command prompt window. 2. If OpsCx for SLM is hosted on Linux system, change current directory: cd /opt/ov/bin 3. To start, stop or restart the integration service, run the appropriate command: To Start the service: ovc -start slm To Stop the service: ovc -stop slm To Restart the service: ovc -restart slm Related topics Configuration Options <comments voting="plus" />

21 Troubleshoot If you encounter problems while using OpsCx for SLM, you can often solve them yourself. This section is intended to help you. General Troubleshooting Guidelines When investigating an issue, first verify that: Your issue is not related to the third-party software or hardware. Otherwise, contact the corresponding vendor for assistance. You have the latest operating system and software application patches installed on the affected systems. Settings in the configuration files of Operations Connector for Service Level Management are correct: the file structure and syntax are preserved, the values are valid. <comments voting="plus" />

22 General troubleshooting Product Log Files Operations Connector for Service Level Management records actions performed by its services into log files. Occurrences of unexpected behavior are also added as entries into the log files. You can use the logged information to investigate issues. Log Files Location Operations Connector for Service Level Management creates and maintains the following log files: List of Log Files in the <OvDataDir>/log/ folder: 1. System.txt 2. opscx-java-path-validation.txt 3. opscx-slm.txt Changing Log Levels The log entries have different Log levels. By default ERROR value is set in Operations Connector for Service Level Management. Following log levels are available in Operations Connector for Service Level Management: 1. INFO 2. DEBUG 3. WARN 4. ERROR The default log level is ERROR. To change the log level, follow these steps: 1. Log on to the OBM console. 2. Go to Administration > Monitoring > Assignment & tuning. 3. From Select a view drop-down box, click Systems_Infrastructure. The left pane with the list of system(s) appears. 4. Click on the required system. The Assigned Item lists the OpsConnector for SLM Configuration for the selected system. 5. In Assignment Details tab, click icon to see the list of Expert Parameters. 6. Double-click on Log Level parameter. The Parameter: Log Level pop-up appears 7. In the drop-down list select the log level required and click OK.

23 Troubleshooting Scenarios Symptom Description Resolution Symptom SLM process does not start After successful deployment of OpsCx for SLM and parameter configurations, the SLM processes are not starting. This issue is because Java application is not installed on the Operations Agent node. The /log/opscx-java-path-validation.txt log file consists of a message that Java is prerequisite for OpsCx for SLM deployment. Install the recommended Java application on Operations Agent node and update the java path in the Configuration parameter to resolve this issue. SLM Service is not running Description This issue may occur due to the schedule set for SLM in the APIs. Resolution To resolve this issue, restart the SLM service using the Select Tool described in the Administer section. Before Contacting Software Support If you cannot solve your issue, report it. Before contacting Software Support, ensure that: You have performed the general checks. See General Troubleshooting Guidelines. You have verified your problem is not described in this chapter. You have collected relevant data that might be required to send to Software Support: a description of your problem, characteristics of your environment, related entries logged in the operating system event log or in the Operations Connector for Service Level Management log files. The Software Support personnel will then provide you with further instructions. Among other things, you may be asked to change the Operations Connector for Service Level Management logging severity level, to repeat or perform particular operations in your Operations Connector for Service Level Management environment, and to collect specific data from your system and send them to Software Support. To contact Software Support, see the web site at <comments voting="plus" />

24 Develop This section helps you learn the SLM API capabilities and the metrics that can be accessed programmatically through these APIs. Application Programming Interface <comments voting="plus" />

25 Application Programming Interface The SLM external API can be used to retrieve the SLA configuration properties and calculation results, in order to consume this data in external applications. According to the SLM server http/https configuration, set http or https in the configuration parameter HTTP SCHEMA. The API syntax gets updated using this parameter automatically. OpsCx for SLM API List Following is the list of SLM APIs consumed by OpsCx for SLM. These can be enabled/disabled from the SLM Configuration Policies. API Description OA Data source Tablename Get SLA Configuration Data Get SLA Calculation Results Get Calendars Get Tracking Periods Get KPIs To get SLA configuration data. To retrieve the SLA calculation results. This API supports filtering by CI, KPI, tracking periods, and calendars. To retrieve the calendars defined in the system. To retrieve the tracking periods defined in the system. To retrieve the KPIs defined in the system. SLM_SLA_CONFIGURATION SLM_SLA_CALENDER SLM_SLA_TRACKINGPEIOD SLM_SLA_TARGET Hourly_SLA_CalculationResults Daily_SLA_CalculationResults Weekly_SLA_CalculationResults Monthly_SLA_CalculationResults Quaterly_SLA_CalculationResults Yearly_SLA_CalculationResults SLM_Calendar SLM_TRACKINGPERIOD SLM_KPI Get Indicator Statuses To retrieve indicator statuses. SLM_INDICATORSTATUSES According to the configuration parameter SLM HOSTNAME value, the API parameter <Gateway Server> gets updated automatically. <comments voting="plus" />

26 Get SLA Configuration Data API Syntax: Server>/topaz/slm/customers/<CustomerId>/sla/<slaId> where, <CustomerId> is the Customer ID (use 1 for non-hpe SaaS deployment). <slaid> is the SLA RTSM ID (non-mandatory parameter; leave empty to get all SLAs in the system). <Gateway Server> is the SLM server. API Polling Frequency [Format 24 hours] : Default Value = 24 Hours, configurable in Hours The response for SLA CONFIGURATION API are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename SLM_SLA_CONFIGURATION: Field Description Agent Datatype slaid SLA ID TEXT name SLA display name TEXT description SLA description TEXT details SLA details TEXT type OLA, SLA, or UC TEXT creator Username of the user which created the SLA TEXT timezone SLA time zone TEXT url Link to the contract details from an external source. TEXT classification Formal or informal TEXT customerid CI ID of the organization specified as the customer of the SLA TEXT customername CI name of the organization specified as the customer of the SLA TEXT providerid CI ID of the organization specified as the provider of the SLA. TEXT providername CI Name of the organization specified as the provider of the SLA. TEXT state Preliminary, Running, or Terminated TEXT startdate enddate SLA start date, long value representing the date in milliseconds since January 1, :00:00 GMT. SLA end date, long value representing the date in milliseconds since January 1, INT64 INT64 targetid IDs of the SLA targets INT32 The SLA CONFIGURATION API output may consist of an SLA ID with multiple CALENDER IDs, TARGET IDs and TRACKINGPERIOD IDs. Following are the look-up tables that store these IDs in individual records. These values can be obtained based on the SLA ID of the base table SLA CONFIGURATION. The output fields for SLM_SLA_CALENDAR configuration are as follows:

27 id Field Description Agent Datatype Unique ID of the record for the particular SLA ID mapped to SLA_CONFIGURATION table. INT64 slaid SLA ID TEXT calendarid Calendar ID The output fields for SLM_SLA_TRACKINGPERIOD configuration are as follows: id TEXT Field Description Agent Datatype Unique ID of the record for the particular SLA ID mapped to SLA_CONFIGURATION table. INT64 slaid SLA ID TEXT trackingperiodid Tracking Period ID The output fields for SLM_SLA_TARGET configuration are as follows: id TEXT Field Description Agent Datatype Unique ID of the record for the particular SLA ID mapped to SLA_CONFIGURATION table. INT64 slaid SLA ID TEXT trackingperiodid Taget ID INT64 <comments voting="plus" />

28 Get SLA Calculation Results API Syntax: Server>/topaz/slm/customers/<CustomerId>/ciSummary/<view>/sla/<slaId>/calendar=<calen darid>&startdate=<startdate>&enddate=<enddate>&ciids=<ciids>&kpiid=<kpiid where, <CustomerId> is the Customer ID (use 1 for non-hpe SaaS deployment). view is Mandatory; report view. Use one of the following: hour, day, week, month, quarter, year, weektodate, monthtodate, quartertodate, yeartodate or slatodate. <slaid> is the SLA ID (use "all" for all SLAs). <calendarid> is Optional, SLA calendar ID (leave empty for all SLA defined calendars, see [#GetCalender Get Calendar]). startdate is in seconds. Mandatory for closed periods only. enddate is in seconds. Mandatory for closed periods only. ciids is Optional. Comma separated CI IDs; leave empty for all SLA CIs (or SLA nodes when slaid is "all"). kpiids is Optional. KPI internal ID (as it appears in the KPI repository UI); leave empty for all KPIs. This API does not support Outage KPI. <Gateway Server> is the SLM server. For hour: Server>/topaz/slm/customers/<CustomerId>/ciSummary/hour/sla/<slaId>/calendar=<calenda rid>&startdate=<startdate>&enddate=<enddate>&ciids=<ciids>&kpiid=<kpiid The response for SLA Calculation Results API for hour are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename Hourly_SLA_CalculationResults: Field Description Agent Datatype slaid SLA ID TEXT ciid CI ID TEXT startdate enddate ciname Period start time, long value representing the date in seconds since January Period end time, long value representing the date in seconds since January If you make a request for a single SLA, the CI name is displayed along with the CI. The CI name is not displayed if the CI ID and SLA ID are the same. INT64 INT64 TEXT trackingperiod Tracking period of the sample: hour TEXT calendar Calendar of the sample. See [#GetCalender Get Calendar]. TEXT KpiType KPI ID INT64 KpiDisplayName KPI display name TEXT

29 KpiStatus KPI status ID INT64 StatusDisplayName KPI status display name TEXT KpiValue KPI numeric value INT64 For day: Server>/topaz/slm/customers/<CustomerId>/ciSummary/day/sla/<slaId>/calendar=<calendar Id>&startDate=<startDate>&endDate=<endDate>&ciIds=<ciIds>&kpiId=<kpiId The response for SLA Calculation Results API for day are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename Daily_SLA_CalculationResults: Field Description Agent Datatype slaid SLA ID TEXT ciid CI ID TEXT startdate enddate ciname Period start time, long value representing the date in seconds since January Period end time, long value representing the date in seconds since January If you make a request for a single SLA, the CI name is displayed along with the CI. The CI name is not displayed if the CI ID and SLA ID are the same. INT64 INT64 TEXT trackingperiod Tracking period of the sample: day TEXT calendar Calendar of the sample. See [#GetCalender Get Calendar]. TEXT KpiType KPI ID INT64 KpiDisplayName KPI display name TEXT KpiStatus KPI status ID INT64 StatusDisplayName KPI status display name TEXT KpiValue KPI numeric value INT64 For week: Server>/topaz/slm/customers/<CustomerId>/ciSummary/week/sla/<slaId>/calendar=<calenda rid>&startdate=<startdate>&enddate=<enddate>&ciids=<ciids>&kpiid=<kpiid The response for SLA Calculation Results API for week are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename Weekly_SLA_CalculationResults: Field Description Agent Datatype slaid SLA ID TEXT ciid CI ID TEXT startdate enddate ciname Period start time, long value representing the date in seconds since January Period end time, long value representing the date in seconds since January If you make a request for a single SLA, the CI name is displayed along with the CI. The CI name is not displayed if the CI ID and SLA ID are the same. INT64 INT64 TEXT trackingperiod Tracking period of the sample: week TEXT calendar Calendar of the sample. See [#GetCalender Get Calendar]. TEXT KpiType KPI ID INT64 KpiDisplayName KPI display name TEXT KpiStatus KPI status ID INT64 StatusDisplayName KPI status display name TEXT KpiValue KPI numeric value INT64

30 For month: Server>/topaz/slm/customers/<CustomerId>/ciSummary/month/sla/<slaId>/calendar=<calend arid>&startdate=<startdate>&enddate=<enddate>&ciids=<ciids>&kpiid=<kpiid The response for SLA Calculation Results API for month are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename Monthly_SLA_CalculationResults: Field Description Agent Datatype slaid SLA ID TEXT ciid CI ID TEXT startdate enddate ciname Period start time, long value representing the date in seconds since January Period end time, long value representing the date in seconds since January If you make a request for a single SLA, the CI name is displayed along with the CI. The CI name is not displayed if the CI ID and SLA ID are the same. INT64 INT64 TEXT trackingperiod Tracking period of the sample: month TEXT calendar Calendar of the sample. See [#GetCalender Get Calendar]. TEXT KpiType KPI ID INT64 KpiDisplayName KPI display name TEXT KpiStatus KPI status ID INT64 StatusDisplayName KPI status display name TEXT KpiValue KPI numeric value INT64 For quater: Server>/topaz/slm/customers/<CustomerId>/ciSummary/quarter/sla/<slaId>/calendar=<cale ndarid>&startdate=<startdate>&enddate=<enddate>&ciids=<ciids>&kpiid=<kpiid The response for SLA Calculation Results API for quarter are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename Quaterly_SLA_CalculationResults: Field Description Agent Datatype slaid SLA ID TEXT ciid CI ID TEXT startdate enddate ciname Period start time, long value representing the date in seconds since January Period end time, long value representing the date in seconds since January If you make a request for a single SLA, the CI name is displayed along with the CI. The CI name is not displayed if the CI ID and SLA ID are the same. INT64 INT64 TEXT trackingperiod Tracking period of the sample: quarter TEXT calendar Calendar of the sample. See [#GetCalender Get Calendar]. TEXT KpiType KPI ID INT64 KpiDisplayName KPI display name TEXT KpiStatus KPI status ID INT64 StatusDisplayName KPI status display name TEXT KpiValue KPI numeric value INT64 For year: Server>/topaz/slm/customers/<CustomerId>/ciSummary/year/sla/<slaId>/calendar=<calenda rid>&startdate=<startdate>&enddate=<enddate>&ciids=<ciids>&kpiid=<kpiid

31 The response for SLA Calculation Results API for year are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename Yearly_SLA_CalculationResults: Field Description Agent Datatype slaid SLA ID TEXT ciid CI ID TEXT startdate enddate ciname Period start time, long value representing the date in seconds since January Period end time, long value representing the date in seconds since January If you make a request for a single SLA, the CI name is displayed along with the CI. The CI name is not displayed if the CI ID and SLA ID are the same. INT64 INT64 TEXT trackingperiod Tracking period of the sample: year TEXT calendar Calendar of the sample. See [#GetCalender Get Calendar]. TEXT KpiType KPI ID INT64 KpiDisplayName KPI display name TEXT KpiStatus KPI status ID INT64 StatusDisplayName KPI status display name TEXT KpiValue KPI numeric value INT64 <comments voting="plus" />

32 Get Calendars API Syntax: Server>/topaz/slm/customers/<CustomerId>/repositories/calendars/<calendarId> where, <CustomerId> is the Customer ID (use 1 for non-hpe SaaS deployment). <calendarid> is the Calendar ID (leave empty for all calendars in the system). <Gateway Server> is the SLM server. API Polling Frequency [Format 24 hours] : Default Value = 24 Hours, configurable in hours The response for SLM Calender API are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename SLM_Calendar: Field Description Agent Datatype id Calendar ID TEXT name Calendar display name TEXT description Calendar description TEXT scheduledescription A string representing the calendar scheduling configuration. TEXT <comments voting="plus" />

33 Get Tracking Periods API Syntax: Server>/topaz/slm/customers/<CustomerId>/trackingPeriods/<trackingPeriodId> where, <CustomerId> is the Customer ID (use 1 for non-hpe SaaS deployment). <trackingperiodid> is the Tracking period ID (leave empty for all calendars in the system). <Gateway Server> is the SLM server. API Polling Frequency [Format 24 hours] : Default Value = 24 Hours, configurable in hours The response for SLM Tracking API is as follows. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename SLM_TRACKINGPERIOD: Field Description Agent Datatype id Tracking period ID TEXT name Tracking period display name TEXT <comments voting="plus" />

34 Get KPIs API Syntax: Server>/topaz/slm/customers/<CustomerId>/repositories/indicators/kpis/<kpiId> where, <CustomerId> is the Customer ID (use 1 for non-hpe SaaS deployment). <kpiid> is the KPI ID (leave empty for all KPIs in the system). <Gateway Server> is the SLM server. API Polling Frequency [Format 24 hours] : Default Value = 24 Hours, configurable in hours The response for SLM KPI API are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename SLM_KPI: Field Description Agent Datatype id KPI ID INT64 name KPI display name TEXT <comments voting="plus" />

35 Get Indicator Statuses API Syntax: Server>/topaz/slm/customers/<CustomerId>/repositories/indicators/targets> where, <CustomerId> is the Customer ID (use 1 for non-hpe SaaS deployment). <Gateway Server> is the SLM server. API Polling Frequency [Format 24 hours] : Default Value = 24 Hours, configurable in hours The response for SLM KPI API are as following. These fields are stored in the Operations Agent datastore OPSCX_SLM with the tablename SLM_INDICATORSTATUSES: Field Description Agent Datatype id Target/Status ID (as it appears in the calculation results) INT64 name Target/Status display name TEXT <comments voting="plus" />

36