Data suppliers deliver values that are displayed in the Alert Monitor. They each belong to the individual system components and create monitoring objects that report values to the monitoring architecture. These values are displayed in the monitor sets.
It can be useful to check the status of the data collection methods if problems occur in the monitoring architecture. You can find out the most important information about the assigned data collection methods on one hand by choosing Properties, if you choose the data collection method in the Methods tab page by double clicking it. On the other hand, you can find out the definition and runtime status of the data collection method of an MTE by choosing Display Details (
)
This method is very time-consuming for obtaining an overview of the data collection methods and their status for the MTEs of an entire monitor. The technical view Status Data Collector exists as an alternative for this purpose.
In this technical view, you can also manually start the data collection method for any MTE to which a data collection method is assigned. To do this, choose the relevant MTE by double clicking it. This is useful, for example during test phases or for MTEs for which you require the current value, even if it is not yet time for the next start of the method.
Note that when you start a data collection method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.
Procedure
To activate the Status Data Collector technical view, follow the procedure below:
...
1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.
2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.
3. Choose Views ® Status Data Collector. The alert tree now no longer displays the alert status and reported values, but information about the data collection methods of the MTEs of the monitor.
Result
The view displays the following information about the data collection methods that are assigned to the individual MTEs of the monitor:
· Assigned data collection method: If the MTE is assigned an active data supplier, the system will display in the corresponding column, as the active data suppliers are not defined in the monitoring architecture
· Type of the data collection method; depending on the definition of the method, the following types are possible:
| Type | Description |
| [Running in agent] | The method is periodically executed in a  CCMS agent |
| [Running in Autoabap] | The method is executed periodically in the dialog process. |
| [Running in Background] | The method is periodically executed in the background process as a job. |
| [Kernel function] | The method is automatically executed in the C kernel. |
| [???] | The method type is not yet known; this type is only displayed for a short type after the method is created. |
· Definition status of the method:
| Type | Description |
| PRESET | The method has just been created; the properties of the method are still determined by the settings in the data supplier. After a maximum of five minutes, the system reads the current settings of the method from the active properties variant and changes the definition status. |
| DBSET
WPSET | The settings of the active properties variant are already included in the properties of the method in this status. However, as it is not in the CHECKED definition status, you should check whether the method is released as a data collection method. |
| CHECKED | The method is released and can therefore be executed. |
| CEN_CHECKED | The method is executed in a CCMS agent; as all settings for the method are set in the agent, do not change these settings manually. |
· Runtime status of the method:
| Type | Description |
| Ready | The method is ready for the next execution; however, this is not yet due. |
| Run required | The method is to be executed, however the responsible dispatcher has not yet started the method. |
| Running | The method is currently running; the color of the corresponding attribute is yellow. |
| Error
Fatal Error | An error occurred during the last run of the method. The difference between the two statuses is that a method in the status Error is started again at the next scheduled run, a method in the status Fatal Error is not. A method in the status Fatal Error is only started again after a warm start of the monitoring segment (see Resetting the Segment to WARMUP Status). The color of the corresponding attribute is red.
You can also reset the method status by selecting the corresponding MTE, choosing Display Details (), and, on the following screen, choosing Edit ® Method Status ® Reset ® Select Data Collection Method. |
The time specification after the runtime status shows the time since which the method has been in this status.
· Frequency of the method call in seconds (Cycle):
The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.
Keyword: BASIS
Title : Basis Displaying the Technical View: Status Data Collector
).
Central Performance History of the Monitoring Architecture start page
). This method is very time-consuming for obtaining an overview of the auto-reaction methods for the MTEs of an entire monitor. The technical view Status Autoreaction exists as an alternative for this purpose. 
). The alert tree now no longer displays the alert status and reported values, but the assigned Collection and Performance Schemata.
