Implementation Guide › Implementation › Data Gathering (Data Source Expert) › Work Files › RejectedEvents.txt

RejectedEvents.txt

This file contains all Events that the Adapter failed to send to CA Business Service Insight because the Event value, defined as one requiring translation, has no matching ID in the translation table. This means that the relevant translation was not performed. Each Event that has at least one value waiting for translation is written to the rejectedEvents file.

At the beginning of every run, the Adapter first attempts to send CA Business Service Insight the Events from the rejectedEvents file as it tries to find the matching ID for the relevant value in the translation table. If the value is found, the Adapter sends the Event and deletes it from the file. If a matching value is not found, the Event remains in the rejectedEvents file.

It is possible to configure the upper limit for the number of rejected Events that can be reached by setting the RejectedEventsUpperLimit parameter in the Adapter configuration file. When the limit is reached, the Adapter stops reading new records and enters a 'Blocked' status. This can be seen when the debug output is displayed on screen during the Adapter execution. If you see a continuous string of uppercase B's, then the Adapter is blocked and requires some of the pending entries to be translated before it loads any more data.

The Pending Events are written to the file in an XML format. Following is an example of an Event from the file:

<rejectedEvent
	createDate="1062330841"
	translator="Translator">
	<event
	inputFormat="InputFormat">
		<field name="resource" type="3" value="Server333p"/>
		<field name="timestamp" type="4" value="1036108800"/>
		<field name="memory_utilization" type="2" value="26.71"/>
		<field name="cpu_utilization" type="2" value="78.85"/>
	</event>
</rejectedEvent>