Checking System Status General Steps

Transcription

1 Checking System Status General Steps

2 Contents Overview Check General System Status Check Data Being Collected Into the System Check ETL Processes Check Data Transfers System Alerts... 9 Check System Alerts... 9 Application Alerts of High Importance... 9 Add or Configure an Alert Rule

3 Overview The following procedures are used to check the status of the system and to see where an issue could be. There is not a strict order on which to follow these procedures. Please refer to the Admin Guide for more information. 1. Check General System Status To check the general Status of the system, click on the down arrow next to the System Status. This will display different metrics of the system. Numbers in Black and Green means that the metric is OK. Numbers in Yellow means a warning and that the metric should be check. Numbers in Red represents an issue and the metric needs to be checked. Clicking over the metric will display the corresponding area where the issue can be check. 3

4 2. Check Data Being Collected Into the System To check if the data is being transferred into the system, go to Collectors -> Processes Verify that the different collector processes are running. If the processes have a different state, could mean an issue with the collector. To get more information click into the + next to the Process Id. Possible reasons a process is not running - The process was stopped to allow for system maintenance. - The process is not needed to be running - There is a problem with the process itself that cause it to stop. Select the Locations Tab (Collectors -> Locations). 4

5 Verify that all the active locations are On Time. If they have a different state, could mean an issue with that location. To get more information click into the + next to the Location Id. Possible reasons a location has not been collected - There are no new files in the collection location o There are no new tests been run. o There is a problem with the process that generates the new files. o The new files name doesn t have the format or pattern expected. - The system is not able to access the collection location o The logging credentials are not correct. o The collection location is down. o The connection between the system and the collection location is down. Select the Files Tab (Collectors -> Files) Verify that all the files collected have a Successful state. If they have a different state, could mean an issue with that file. Possible reasons a file collection is not Successful - The connection between the system and the collection location has problems. - The file is corrupted. 5

6 3. Check ETL Processes To check the ETL processes, go to ETLs -> Processes Verify that all the ETLs processes state is running. If the ETLs processes have a different state, could mean there is an issue with that ETL process. To get additional information, click into the + next to the Process name. Possible reasons a process is not running - The process was stopped to allow for system maintenance. - The process is not needed to be running - There is a problem with the process itself that cause it to stop. Select the Files tab. 6

7 Select the Loaded lower tab to see the list of files that has been loaded. Select the Failed lower tab to see the list of files that weren t loaded. If the files haven t been loaded, could mean there is an issue with that file. Possible reasons a file was not loaded - The information in the files is not as expected. - There is no information in the file. - The information is corrupted. 7

8 4. Check Data Transfers To check data transfer errors, go to Data Transfers - > Jobs Verify that the status of each data transfer is InProgress or Completed. If the data transfers have a different state, could mean that there is an issue with that data transfer. Possible reasons for data transfer problems - Connection to the data base is down - Data base is busy - Data base is not running 8

9 5. System Alerts Check System Alerts To check the System Alerts, go to Alerts -> Data Loading. Check the type of Alerts that has been raised. To get more information about any alert click into the + at the beginning of the row. If needed or required, select an alert and acknowledge it. Repeat the previous process to the System Health Alerts ( System Health Tab) and Application Alerts ( Application Tab). Some alerts will indicate an issue that will not affect the performance of the application, like alerts that indicate that a record inside a file is not valid. Other alerts will indicate an issue that affect the performance of the application, like alerts that indicate that the application was not able to access the database. Application Alerts of High Importance Though many of the system error alerts are important, it is worth noting that some of the most important application alerts include: CEM This Alert indicates that xsa (i.e. VisionWorks-Analytics-MSA or VisionWorks-Analytics- TSA) did not receive a file from the Controller System (i.e. Landslide or LUMOS). xsa will generate this Alert first. CEM This Alert indicates that xsa did not load a new file into the xsa Database. xsa will generate this Alert second. Add or Configure an Alert Rule This section provides information about how to Add and Configure an alert rule that may trigger a notification (i.e. , SNMP trap, etc.) when specific threshold conditions are met. 9

10 Note: It is recommended that customers configure these Application Alerts into their monitoring systems (i.e. If these Alerts happen, then the customer should be urgently notified that the xsa system is impaired (e.g. dead) and some repair action is urgently needed). Please refer to the Administrator Guide for further information. Steps to Add a New Rule Important: Before adding a new rule, a destination must be configured within the admin console. Details on setting up a destination can be found within the Administrator Manual. To add a new rule, perform the following: 1. Navigate to the Admin Console > Alerts Manage Alerts 2. Select > Add from the upper button toolbar. The Add a new Rule screen will appear. 3. Enter the required information as shown in the following example image. 4. Press > Save to Apply the rule. Note: When an error alert code CEM is generated (as shown in the above example image), the system will send the notification to the destination(s) selected. (The destination Paul is shown in the example image to receive these notification alerts.) 10