Monitor platform operations via Job list

<< Click to Display Table of Contents >>

Raynet One > 1.1 > User Guide > Organize your IT landscape 

Monitor platform operations via Job list

When it comes to platform operations (also: jobs), these usually are either inventory or discovery runs. Depending on the degree of complexity within your IT landscape, the number of IT assets and the variety of operating systems, individual jobs will pile up. The job list helps you keep track of your platform operations and to stay in control. In this chapter, you will learn how to

 

capture the "big picture" of platform operations with little effort,

find various job-related details views,

collect evidence of platform operation to compare against your expectation,

get an impression of correct platform response to user request,

distinguish between successful and unsuccessful jobs, and

"interpret" results in the main Job details view.

 

The next series of chapters explains the topic by working on your own IT landscape. Please make sure to have the platform configured correctly for the execution of real platform jobs.

 

finger1

Be aware:
Some step-by-step guides rely on knowledge about work-flows covered in former chapters. Please read this documentation carefully to not trip over more compact step descriptions.

Interpretation of job details

The details views provided related to job details is a rich hive of information. It can used to create statements about IT landscape technical health. Highly technical information is provided for effective troubleshooting. Intermediate information pieces should be connected to form a complete process. Details of running jobs change rapidly, requiring certain skills in technical analysis to keep up. Troubleshooting information does not have to make sense, or is misleading at worst. To say the least, job analysis is not an easy task which requires a good strategy.

 

It is recommended to split job analysis across multiple departments. Basic job details such as job success and duration are properly understandable by people of any trade. When it comes to investigating failed jobs, for example troubleshooting, the specific jobs should be redirected to IT administration consisting of technically inclined people.

 

Some aspects of job analysis intersect with the broad topic IT landscape maintenance (troubleshooting). In that case, the information is of technical nature.

 

clip0326

 

Excerpt of the main Job list, highlighting the State column. This column gives a good indication of the current state of each job. Use it to assess the overall platform performance on your IT landscape, without requiring much technical insight.

 

clip0327

 

Instrument log view of the Zero Touch Unix Device Scan instrument. It is the most involving part of job analysis. It should be performed by technically inclined people only.