Provide better formatted page for individual messages

[pholica]

The web interface currently provides only JSON view for individual messages. In this form, the message is presented just as how datagrepper captured and processed the message and for some users may lead to confusion that the presented json is the message itself.

It would be nice to provide view similar to what email clients provide to have headers and other information that the message body itself separated so that it's clear for everyone what the headers are and what the message body is.

[ggallen]

A specific instance of this problem is the following...

The jms-messaging-plugin allows messages to be selected using message checks. Message checks are implemented using JSON path syntax. So when users see the message JSON displayed in datagrepper, they are using that JSON to create their message check. This doesn't work as the actual JSON message is different, so the trigger ends up being useless as it never fires.

One of the main problems is the "msg" entry. It seems that datagrepper adds this field and puts the message content below this. This is not obvious to users, and they end up writing JSON path expressions like $.msg.content_types[0]. This clearly is incorrect, and it a result of the way the message is being presented to the user.

[thrix]

yeah +1