Amend connection count to avoid oversized count
Amend connection count to avoid oversized count

Since the log analysis merely needs to know if a connect/disconnect is redundant,
only report 0, 1, or '2' connections to indicate 2 or greater.  log analysis
then would want to seek out a connect with eventdata of '1' and disconnect with
eventdata of '0' and mostly ignore the '2' info.  Desire for more data
could be done by actually counting the connects and disconnects, this is
just to provide a fast path to finding the 'first connection' and 'last disconnect'
signatures.

jjohnson42/confluent,michaelfardu/thinkconfluent,whowutwut/confluent,whowutwut/confluent,jufm/confluent,michaelfardu/thinkconfluent,chenglch/confluent,jjohnson42/confluent,xcat2/confluent,jjohnson42/confluent,jufm/confluent,xcat2/confluent,xcat2/confluent,jufm/confluent,chenglch/confluent,jjohnson42/confluent,michaelfardu/thinkconfluent,chenglch/confluent,chenglch/confluent,whowutwut/confluent,michaelfardu/thinkconfluent,whowutwut/confluent,jufm/confluent,xcat2/confluent,michaelfardu/thinkconfluent,chenglch/confluent,jjohnson42/confluent,jufm/confluent,xcat2/confluent