• State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    25
  • Views views
    188
  • Users 0 members are here

Loss of part of the events

Bohdan Hotsuliak

Hi

Here's the situation: I didn't pay attention to see if this happens on all connector types, but now I'm setting up a Flex Connector Regex File and everything is working fine, however I noticed if I manually send into the file one event, they don't do not enter the active channel, and if I transmit more than one event, then the one that is the first in the list - it is always lost and does not enter the channel.

What is the problem ? Can it be related to the configuration file or is this a feature of flex connectors?

P. S. If the connector is restarted and the file with events is cleared and added events to an empty file, they are sent to the active channel in full.

Thanks in advance

Bohdan
  • 0

    Don't want to create a new section for this.

    The question relates to the same connector. Problem with time formatting.

    This is how the time looks in the event - "timestamp": "2024-05-16T12:34:56Z", and this is how I described my configuration file:

    token[1].name=Date

    token[1].type=TimeStamp

    token[1].format=yyyy-MM-dd HH:mm:ss.SSS to make the time look like this - 27 Jun 2024 12:13:33 MSK

    But instead of the time of the event itself in the end time field, I get, as it seems to me, the time of receipt by the agent

  • Verified Answer

    +1

    Hello Bohdan, 

    I am proposing you extend your experiment and try to send a few more events and you will see that the first event will start to appear in your active channel.

    This behavior only happens with the file reader type connector and the sources constantly updating the file. 

    You are not losing the events and I can assure you that. Those are kept cached and sent when new events are read/processed by the file reader connector delayed.

    It is also true that in that file you have only one event that will not be sent until a new event is present/processed by the connector and even then the new one will not be sent until new events appear in the connector. Also, it is true that if the connector is been restarted then all the cached events will be sent as well.

    I will not consider this a but as long as your file is constantly updated but it can be an issue if the file containing source events is not constantly updated.

    Best Regards, 

    Daniel

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.