Extend readinessprobe to show if not-ready state is due to not being able to publish or not being able to subscibe

[seppelucas]

Natsomatch pods suddenly and temorarily become not ready. and status check returns a 500 code.
it would be nice to know where the error comes from.

currently there is checked on: is_healthy = forever_stats.get_count() > 0 && forever_stats.get_last_publish() < 10;

track data received and published in different stats so the is_health can check on both.