Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Configuration Management System (CMS)2018.05

Use > JMX Reference > Data Flow Management Methods > How to View Job Information on the Data Flow Probe

How to View Job Information on the Data Flow Probe

This task describes how to view job information (for example, job threads and Trigger CIs) saved to the Data Flow Probe's PostgreSQL database. You work with the JMX console.

This task includes the following steps:

Access the MBean operations
Use the following procedure to access the JMX console on the Data Flow Probe and to invoke the JMX operations.
1. On the probe machine, launch the Web browser and enter the following address:
  
  https://localhost:8453
  
  You may have to log in with the user name (default: sysadmin) and password.
2. Click the Local_<machine name or IP address> > type=JobsInformation link.
Locate the operation to invoke

On the MBean View page, select type=JobsInformation. Locate the required operation. For details, see Discovery Job Operation Commands and Job Operation Parameters.

The following is a list of operations that can be invoked in the above procedure:

viewJobProblems

Enter the name of a job to retrieve a list of Trigger CIs that have problems for that job. Enter the name of a Trigger CI to retrieve a list of problems for that trigger CI. If no values are entered, all the jobs and triggers that have problems are displayed.

For details on the job operation parameters, see Job Operation Parameters.

Column	Description
Job ID	Displayed if the jobID field is left empty. The job name as it appears in Data Flow Management. Click a job to go to its viewJobStatus page, to view its status and scheduling information.
Trigger CI	Displayed if the triggerID field is left empty. The CMDB object ID of the trigger for a job.
ErrMsgCode	The error message hash string (error hash ID).
ErrParams	The error parameters.
Severity	The severity of the error. For details on severity levels, see Error Severity Levels.

viewJobResults

Fill in one or more of the parameters to return a list of CIs that have been discovered by a job.

For details on the job operation parameters, see Job Operation Parameters.

When Hide Touched CIs Info is set to True, the results page displays the following information:

Column	Description
Job Name	Displayed if the jobID field is left empty. The job name as it appears in Data Flow Management. Click a job to go to its viewJobStatus page, to view its status and scheduling information.
CI Type	Click to filter the list to show results for one CIT only.
Total CIs	Click to go to the viewJobResultCiInstances page, to view a list of all CIs that have been discovered by a job.
Triggered CIs	Click to go to the viewJobTriggeredCIs page, to view a list of all Trigger CIs that have been discovered by a job.
Last Discover Time	The date and time that the job was invoked.

When Hide Touched CIs Info is set to False, the results page displays the following information:

Column	Description
Job Name	Displayed if the jobID field is left empty. The job name as it appears in Data Flow Management. Click a job to go to its viewJobStatus page, to view its status and scheduling information.
CI Type	Click to filter the list to show results for one CIT only.
Touched CIs	Click to go to the viewJobResultCiInstances page, to view a list of those CIs discovered by the job that are Touched CIs. For details, see Job Operation Parameters.
Non Touched CIs	Click to go to the viewJobResultCiInstances page, to view a list of those CIs discovered by the job that are not Touched CIs.
Triggered CIs for Touched CIs	Click to go to the viewJobTriggeredCIs page, to view a list of those Trigger CIs included in a job that are Touched CIs.
Triggered CIs for Non Touched CIs	Click to go to the viewJobTriggeredCIs page, to view a list of those Trigger CIs included in the job that are not Touched CIs.
Last Discover Time	The date and time that the job was invoked.

You can further filter results in the results page by entering text filters in one of the fields, and clicking the Search button.

viewJobsStatuses

Click the viewJobsStatuses button to return status and scheduling information for all jobs. You can choose to filter the results. For details, see Job Operation Parameters.

Note This page is saved under \DataFlowProbe\runtime\jobsStatuses once a day.

The results page displays the following information:

Column	Description
No.	The number of the job in the list.
Job Name	The job name as it appears in Data Flow Management. Click a job to go to its viewJobStatus page, to view its status and scheduling information.
Status	The severity of the job's status, as calculated by the Probe. Blocked. Not in use. Removed. The job is no longer active. Done/Total Triggers. The number of trigger CIs that the Probe finished running on, against the total number of triggers for the job. For example, (28/69) indicates that there is a total of 69 triggers for the job, while the Probe has completed running on 28 of those triggers. Scheduled. The job is scheduled to run. For details on scheduling jobs, see Discovery Scheduler Dialog Box. A red background signifies that a thread has run longer than expected and may be stuck. A green background signifies that the job is running as expected.
Triggered CIs	The Trigger CIs that have been run by the job. Click to go to the viewJobTriggeredCIs page.
Errors & Warnings	The number of errors and warnings for a specific job. Click to go to the viewJobErrorsSummary page, to view a list of error and warning messages reported on this job.
Last Invocation	The date and time that the job was last run.
Next Invocation	The date and time that the job is next scheduled to run.
Last Total run duration (seconds)	The length of time, in seconds, taken to run the job in the previous invocation. This is calculated according to the start time of the first trigger until the end time of the last trigger, even if triggers were added later on.
Avg run duration (seconds)	The average duration (in seconds) per trigger of the time it took the Probe to run this job.
Recurrence	The number of times that the job was invoked. Click to go to the viewJobExecHistory page, to retrieve a history of job invocations.
Results	The number of CITs that have been discovered by the job. Click to go to the viewJobResults page to view the CITs. Note Displayed when hideResults parameter is set to False.

viewJobStatus

Enter the name of a job to return its status and scheduling information.

For details on the job operation parameters, see Job Operation Parameters.

The results page displays the following information:

Column	Description
Threading info	The total number of worker threads created by the invocation, the free worker threads, and the stuck worker threads.
Total work time	The time that the Probe took to run this job.
Tasks waiting for execution	A list of jobs together with the number of Trigger CIs that are awaiting activation.
Max. Threads	The number of threads that are serving this job.
Progress	A summary of the current run, that is, since the specific run was activated. For example, `Progress: 2017 / 6851 destinations (29%)` means that out of 6851 CIs, 2017 CIs have already run.
Working Threads information	Thread Name. The thread that is now running this job. Click to go to the viewJobThreadDump page. You use this page when a thread is running for a long time, and you must verify that this is because the thread is working hard, and not because there is a problem. Curr Dest. ID. The name of the node on which the job is running. Curr Dest. IP. The IP for which the job is discovering information. Work Time (Sec). The length of time that this thread is running. Communication Log. Click to go to the viewCommunicationLog page, to view an XML file that logs the connection between the Probe and a remote machine. For details, see the Create communication logs field in the Execution Options Pane.
Discovery Jobs Information table	Status. The severity of the job's status, as calculated by the Probe. For details, see Status. Triggered CIs. Click to go to viewJobTriggeredCIs page, to view a list of Trigger CIs that are part of a job. Errors & Warnings. Click to go to viewJobErrorsSummary page, to view a list of error and warning messages reported on this job. Last invocation. The date and time that the job was last run. Next invocation. The date and time that the job is next scheduled to run. Last Total run duration (seconds). The length of time, in seconds, taken to run the job in the previous invocation. This is calculated according to the start time of the first trigger until the end time of the last trigger, even if triggers were added later on. Avg run duration (seconds). The average duration (in seconds) per trigger of the time it took the Probe to run this job. Recurrence. The number of times that the job was invoked. Click to go to viewJobExecHistory page, to view a history of job invocations.

Note Click Results below the table to go to the viewJobResults page to view the CITs that have been discovered by the job.

viewJobTriggeredCIs

Fill in one or more of the parameters to return a list of Trigger CIs that are part of a job.

For details on the job operation parameters, see Job Operation Parameters.

The results page displays the following information:

Note Depending on the triggers, other information might also be displayed.

Column	Description
No.	The number of the job in the list.
Triggered CI ID	The CI instances that have been discovered by the job. Click to go to the viewJobTriggeredCIs page to view information about their CITs.
Last Execution Start Time	The date and time that the job last started running.
Last Execution End Time	The date and time that the job last finished running.
Service Exec. Duration (ms)	The maximum time that it took for a job to run in the last invocation, not including periods when the job did not run. Compare this result with the total execution duration. For example, when several jobs run simultaneously, but there is only one CPU, a job might have to wait for another job to finish. The service duration does not include this waiting time, whereas the total duration does.
Total Exec. Duration (ms)	The time that it took for a job to run in the last invocation, including the periods when the job did not run.
Last Run Status	The status of the last run, that is, whether the run succeeded or failed. In case of failure, click to go to the viewJobProblems page, to view a list of Trigger CIs with problems.
Priority	The priority of the job. Note The lower the value, the higher the priority.

The following is a list of parameters used in the above operations:

ciType. The name of the CI type (for example, ip, host).

data. A textual field in the DiscoveryResults table that contains information about the discovered object. For example:

<object class="ip">
<attribute name="ip_probename" type="String">EBRUTER02</attribute>
<attribute name="ip_address" type="String">16.59.58.200</attribute>
<attribute name="ip_domain" type="String">DefaultDomain</attribute>
</object>

Error Id. The error message hash string (error hash ID) that is displayed in the Jobs_Problems table.
HideRemovedJobs.True: do not display jobs that have run previously and are not relevant to the current run.
Hide Touched CIs Info. Touched CIs are CIs which were discovered in previous invocations. DFM already has information about these CIs, so there is no need for the Probe to send the information to the server again. The server identifies that these CIs are relevant and that there is no need to enforce the aging mechanism on them. For details on aging, see The Aging Mechanism Overview.

True: the table displays the total number of CIs and the total number of Trigger CIs for each CIT. False: The table displays the total number of CIs and Trigger CIs divided between touched CIs and non-touched CIs.
includeNonTouched. Enables filtering the table to view non-touched CIs. Choose between viewing non-touched CIs only, all CIs (touched and non-touched), or none:
includeNonTouchedCIs. See includeNonTouched.
includeTouched. Enables filtering the table to view touched CIs. Choose between viewing touched CIs only, all CIs (touched and non-touched), or none.
includeTouchedCIs. See includeTouched.
jobID. The name of the job, for example, Host Applications by PowerShell:
maxRows. The maximum number of rows that should be displayed in the results table. The default is 100 or 1000.
maxTriggeredCIs. See maxRows.
objectID. The CMDB object ID.
hideRemovedJobs. Hides information about jobs with the status, REMOVED. These are jobs that have run previously but that are not currently scheduled to run.
hideResults. Indicates whether or not to hide the Results column. If the Results column is present, you can navigate to the job results. For more information, see viewJobResults , and viewJobsStatuses .
triggerCI. The CMDB object ID of the trigger for a job.
triggeredCiID. See triggerCI.

Send Help Center feedback