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 in the Agile Service Manager UI. It is installed as part of the core installation procedure.

Before you begin

Important: The SevOne Observer supports SevOne version 6.5.1 & API version 2.20.0.

Ensure you have the SevOne server details to hand, such as the username and password.

The observer is installed as part of the core installation procedure.

About this task

A SevOne Observer job extracts SevOne managed servers via REST API calls. The Observer loads and updates the servers and their relationships within the Netcool Agile Service Manager core topology service.
Enhanced modeling:

For past releases, the SevOne Observer modeled relationships from device to device, but from the 30 August 2023 release onwards it models relationships from network interface to network interface.

Restriction: The SevOne Observer supports network device interface data for full links only (partial links are not supported).

Remember: In the Agile Service Manager UI, you will only see relationships between network interfaces for full links, but not partial links. The following link examples (from the SevOne Topology Report) show the differences between a full link and a partial link.
Full link example
Partial link example
You define and start the following jobs.
Load job
Run this job whenever you need SevOne topology data refreshed.
By default, these jobs are one-off, transient jobs that perform a full upload of all requested topology data as soon as they are triggered.
You can also run these jobs (again) manually from the Observer UI, or schedule them to run at set times when configuring them.
The SevOne Observer loads the following resources and their relationship into the Agile Service Manager core topology service:
Table 1. 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

Configure a SevOne Observer job

  1. On the Observer jobs page, perform one of the following actions:
    To edit an existing job
    Open the List of options overflow menu next to the job and click View & edit.
    To create a new job
    Click Add a new job + and select the SevOne Observer tile.
  2. Define the following parameters, then click Run job to save and run the job.
    Table 2. Load job parameters
    Parameter Action Details
    Unique ID Enter a unique name for the job. Required
    Hostname Enter the SevOne hostname. Required
    Data Tenant Specify the data tenant used for the device group or groups. 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 hop Choose the number of hops to be discovered. Required. Default is 1, maximum hops is 3.
    Generate debug support file
    Set the optional Generate debug support file 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. The file is saved to the following locations:
    On-prem
    $ASM_HOME/logs/<obs>-observer/
    On OCP
    /var/log/itsm/<obs>-observer
    		 Optional
    Job schedule

    Specify when the job should run, and whether it should run at regular intervals.

    By default the job runs immediately, and only once.

    Optionally you can specify a future date and time for the job to run, and then set it to run at regular intervals after that.

    Optional. Transient (one-off) jobs only.

    If you set a job schedule, the run intervals must be at least 90 seconds apart, and if you set them at less than 15 minutes, a warning is displayed, as the frequency can impact system performance.
    Observer job description Enter additional information to describe the job. Optional