fix(tap): Don't send events if output is empty

[ArunPiduguDD]

Overview

When sending output events via tap, we can run into issues with the async channel output type if the output is empty. Add a check to see if the output is empty before attempting to send events.

Testing

Tested with demo_logs, unit tests

[jszwedko]

Rather than this, would it be possible for the channel receiver to be able to handle an empty list of events? Just wondering if you'd considered and discarded that option already.

[ArunPiduguDD]

The issue is the buffer size of the channel, if it's too small then the async channel output type will have issues. Though now that I'm thinking about it, this might not be the ideal solution. Let me do some further investigation

[bruceg]

This looks like an obvious band-aid fix, but makes me wonder how output_events could be empty. Is it something we need to check before this point or handle differently in the output methods?

[ArunPiduguDD]

This looks like an obvious band-aid fix, but makes me wonder how output_events could be empty. Is it something we need to check before this point or handle differently in the output methods?

Output events is empty if no events have been processed by the pipeline / the tapped components

[bruceg]

Output events is empty if no events have been processed by the pipeline / the tapped components

Right, my question is, how would we reach this point if no events have been processed?