Currently, SumoLogic is being used to track ALL activity, error, usage, warning, data, and debug logs, that are logged by any user action, or any messages that a service my company uses communicates between other services. Anytime a button is clicked, a page is accessed, workflow is done, or process is completed by an end-user, we log the action in Sumo. Anytime a service or ec2 is running and completes a process or sends/receives a service message, we log that interaction between services. This robust logging allows us to pinpoint specific areas where we need to get more information or want to track specific metrics. We have set up our implementation with Sumo to log anything we tell it to log. If we want a message logged every time an end-user logs in and clicks a certain button, we can log that specific of information down to the second they did it and which browser version they were on. The level of logging is all up to how much you build into your service logging.