Defining Juniper CSO Observer jobs
Using the Juniper CSO Observer, you can define a full load job that will gather topology data from Juniper CSO. It is installed as part of the core installation procedure.
Before you begin
Important: The Juniper CSO observer supports the on-premise Juniper CSO version
4.1.0.
Ensure you have the Juniper CSO details to hand, such as details of the Juniper CSO API server and its credentials.
Remember: Swagger documentation for the observer is available at the following default
location: https://<your
host>/1.0/junipercso-observer/swagger
About this task
The Juniper CSO Observer retrieves topology data from Juniper CSO Release 4.1 via REST APIs exposed by CSO API server.
junipercso_observer_common.sh
- The configuration file you use to customize Juniper CSO Observer settings.
You define and start the following job. You must edit the parameters in the configuration file
before running this job.
- Load job
- A transient (one-off) job that loads all requested topology data.
Procedure
To edit the parameters in the configuration file
To start the Load job
What to do next
You can also use the following scripts:
- junipercso_observer_load_stop.sh
- Stops the Load job
- junipercso_observer_job_list.sh
- Lists the status of current jobs
- junipercso_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.