Defining 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.

Remember: Swagger documentation for the observer is available at the following default location: https://<your host>/1.0/sevone-observer/swagger

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
sevone_observer_common.sh
The configuration file you use to customize SevOne Observer settings.
The parameters defined here are then used by the sevone_observer_load_start.sh script to trigger the SevOne Observer job.
Tip: Alternatively, you can set the appropriate environment variables. If an environment variable is set, it takes precedence over the configuration file settings.
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

To edit the parameters in the configuration file

  1. Open the sevone_observer_common.sh configuration file and edit the following parameters:
    Table 2. Load job parameters
    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 hop Choose the number of hops to be discovered. Required. Default is 2, maximum hops is 3.

To start the Load job

  1. To start the SevOne job, use the following commands: 
    $ASM_HOME/bin/sevone_observer_load_start.sh

Results

This job loads all requested data, and runs only once. Run this job whenever you need the topology data refreshed.

What to do next

You can also use the following scripts:
sevone_observer_load_stop.sh
Stops the Load job
sevone_observer_job_list.sh
Lists the status of current jobs
sevone_observer_log_level.sh
Sets the log level
Remember: As an alternative to being configured using the Observer Configuration UI, observer jobs have scripts to start and stop all available jobs, to list the status of a current job, and to set its logging levels. These scripts can be run with -h or --help to display help information, and with -v or --verbose to print out the details of the actions performed by the script, including the full cURL command. For the on-prem version of Agile Service Manager, observer scripts are configured for specific jobs by editing the script configuration files.