Description:
The Event Collector (EC) schema can be extended to introduce a custom attribute. Doing so requires the creation of a custom component and the attributes associated with it. The custom audit data is written into the extended attribute table EC_EVENT_ATTR. If the custom attribute is passed into the EC Event API's with an invalid value for its declared data type, the event itself is successfully populated into the EC_EVENT table. However, this invalid custom attribute is not written into the EC_EVENT_ATTR table.


Symptoms:
The invalid custom attribute value is not getting populated into the EC_EVENT_ATTR table. Though there is an entry in the EC_EVENT table.

Below is an example how this issue can be reproduced -

1). Register the component. See the registerComponent.xml file.

2). Register an attribute of type DATE, named as “NLSONPASSDT”. Use the componentId from the response of the register component (Response of registerComponent.xml). See the registerAttributes.xml file. 

3). Once the attribute is registered, it will be listed in EC_ATTRIBUTE table.

4). Send an event with this custom attribute containing an invalid millisecond.

Obtain the attribute ID from the response of register attributes (Response of registerAttributes.xml). See the sendEvent.xml file.

6). Change the value as follows and resend the event. An entry can be seen in the EC_EVENT_ATTR table.

For a DATE type attribute.

2). Do not include milliseconds if second granularity is acceptable.

3). Use a value which complies with a supported literal format.

JIRA : WRM-8652 has been opened to log a warning/error when an attribute value is ignored.

See the attached file for reference. (Filenames: registerAttributes.xml, registerComponent.xml, Response_of_registerAttributes.xml, Response_of_registerComponent.xml, sendEvent.xml).