For a small JIRA installations or hosted instances where there are not dedicated webserver administrators and nobody monitor the application, often problems need to become critical before are investigated.

Similary to JRA-15109 there are many advantages of such as feature.

Perhaps the most significant are:

1. Monitor in a better way "helth" of the application - some of the user don't even know what is a web app server (Tomcat/Reisen) and where to look for the log files.
2. Diagnose problems in their early stage - e.g. mailhandler issues/misconfiguration are not visible without access to the log file.
3. Users would attempt to address common and obvious issues listed in the log file if the would have a "convenient" access to the logs.
4. In overall it should impact number of support request logged in SAC.

Many web based application already include similar features.

A simple solution only send the logs or warnings, where complex implementations include ability to set up triggers and monitors on various custom defined events.