Configuring SevOne Observer jobs
Using the SevOne Observer functionality, you can load monitored servers and their relationships, and then visualize this data as a topology view.
Before you begin
Important: The SevOne Observer supports SevOne version 6.2.0 & API version 2.20.0.
Ensure you have the SevOne server details to hand, such as the username and password.
About this task
A SevOne Observer job extracts SevOne managed servers and their relationships via REST API calls.
You define and start the following job.
SevOne Load job
Run this job whenever you need SevOne topology data refreshed.
By default, Load jobs are one-off, transient jobs that do a full upload of all requested topology data as soon as they are triggered.
You can also run these jobs (again) from the Observer UI, or schedule them to run at set times when configuring them.
SevOne resources and relationships loaded by the SevOne Observer job
| Vertex | Description |
|---|---|
| Server | SevOne managed server |
| Ipaddress | IP address associated with the server managed by SevOne |
Procedure
Define or edit the following parameters, then click Run job to save and run the job.
Encryption requirement: See the Configuring observer jobs security topic for more information.
SevOne Observer job parameters for Load job
| Parameter | Action | Details |
|---|---|---|
| Unique ID | Enter a unique name for the job | Required |
| Data Tenant | Specify the data tenant used for the device group or groups. | Required |
| Hostname | Enter the SevOne hostname | Required |
| Username | Specify the SevOne username | Required |
| Password | Specify the SevOne password | Required. Use plain text. |
| Device group path | Specify the device group path to be discovered. To discover more than one group, enter a comma-separated list. | Required |
| Number of SevOne hops | Choose the number of hops to be discovered | Required. Default is 1, maximum hops is 3. |
| Generate debug support file | Set this parameter to 'True' in order to capture the output of the next scheduled job run as a file. This file will be stored with an observer's log files and can be used to debug observer issues, for example at the request of your designated Support team, or while using a test environment. For one-off jobs (that is, Load jobs), this parameter reverts to 'False' after the next completed run. To examine the output produced, you can load the generated debug file using the File Observer. | Optional |
| Job schedule | Specify when the job runs | Optional. Load jobs only. |
| Observer job description | Enter additional information to describe the job | Optional |