Sometimes the absence of messages, for example, errors and exceptions, may save time during troubleshooting and debugging by pointing to what was not happening and provide additional insight. For example, on the picture below we see the same exceptions in the new and old incidents. However, in the old incident we see another exception that was linked to one unavailable server in distributed broker architecture. Therefore, we can assume provisionally that all servers were operational when the new incident happened.
Missing Message pattern is different from Missing Component (Volume 4, page 342) pattern where the latter may point to the component that was not loaded or executed, or simply that it was not selected for tracing.
3.137.223.255