Logic App Diagnostics provides the capability to export the logs to either Event Hubs and to storage. Using Event Hubs, you can set up Streaming Analytics to gather any trends.
Another feature to help tracking messages through a workflow is the Client Tracking ID. This will allow you to correlate messages between actions and any nested workflows. The client can set the header property x-ms-client-tracking-id to a unique value that can be tracked. If no ID is provided by the client, the value is autopopulated.
Also, under the Logic app action blade as shown later, you have access to the input and output message links. From this, you can view the contents of the messages.
The two tools that should be part of your tool belt when performing end-to-end testing:
- Postman: http://www.getpostman.com/ to construct HTTP request messages to your Logic Apps
- RequestBin: http://requestb.in/ to capture the HTTP requests that will be sent to an API App from the Logic App by replacing the URL of the API App with the temporary URL provided by RequestBin
Another useful tool is JSONSchema: http://jsonschema.net . This automatically generates JSON schema from a sample JSON message according to the IETF JSON Schema Internet Draft Version 4. This is useful to validate the schema definition in a Logic App HTTP trigger, for example.