stasionok

Incoming Hook Logger is designed for developers who need to debug or monitor incoming webhook requests sent to their WordPress site. It captures all request data without interrupting the original request flow, allowing other plugins to process the webhooks as usual.
<h3>Key Features:</h3>
<ul>
<li>Multiple URLs: Specify one or more URLs (or partial URLs) to monitor.</li>
<li>Full Data Capture: Logs request method, full URL, headers, raw body, and sender’s IP.</li>
<li>Admin Interface: View logs directly in the WordPress dashboard with two tabs (Settings and Logs).</li>
<li>Filtering & Search: Easily find specific entries by filtering by URL or searching through body and headers.</li>
<li>Secure Storage: Logs are stored in a dedicated database table (<code>wp_webhook_logs</code>) and accessible only to administrators.</li>
</ul>

Incoming Hook Logger

Log incoming webhooks (URL, headers, body, IP). View, filter, and search in the WordPress admin without blocking other plugins.

paniko

To use the custom appenders, add this code in your init plugin for example: Choose among appenders (LoggerAppenderDailyFile, LoggerAppenderRollingFile, LoggerAppenderFile, LoggerAppenderMail, LoggerAppenderMailEvent), for each type you must 
specify the relative parameters, how to official documentation of log4php.
<ul>
<li>
For rolling file appenders:
 ‘1MB’, My_Logger::ROLLING_APPENDER => true, My_Logger::ROLLING_MAX_BACKUP_INDEX => 5 ); $mylogger = My_Logger::get_instance(“”, My_Logger::ROLLING, $parameters); $this->logger = $mylogger->getLogger(); //for debug you add: $this->logger->debug($parameters); $this->logger->debug(“test”); ?></li>
<li>
For mail appender: ”, My_Logger::MAIL_TO => ”, My_Logger::MAIL_SUBJECT => ”, My_Logger::THRESHOLD => My_Logger::LEVEL_DEBUG//6: Sets the root logger level to DEBUG. This means that logging requests with the level lower than DEBUG will not be logged by the root logger. ); 
 $mylogger = My_Logger::get_instance(“”, My_Logger::MAIL, $parameters); ?>
</li>
</ul>
** SET Logger threshold ** A level describes the severity of a logging message. There are six levels, show here in descending order of severity. You can set level of logger, add the parameter:
<ul>
<li>FATAL Highest Very severe error events that will presumably lead the application to abort.</li>
<li>ERROR … Error events that might still allow the application to continue running.</li>
<li>WARN … Potentially harmful situations which still allow the application to continue running.</li>
<li>INFO … Informational messages that highlight the progress of the application at coarse-grained level.</li>
<li>DEBUG … Fine-grained informational events that are most useful to debug an application.</li>
<li>TRACE Lowest Finest-grained informational events.</li>
</ul>
If do you want put a logger in frontend, add this code in template script: ‘1MB’, My_Logger::ROLLING_APPENDER => true, My_Logger::ROLLING_MAX_BACKUP_INDEX => 5, My_Logger::THRESHOLD => My_Logger::LEVEL_DEBUG ); 
 $mylogger = new My_Logger(“”, My_Logger::ROLLING, $parameters); 
 $logger = $mylogger->getLogger(); $logger->debug(“test my logger”); ?>
For more info read the API documents of log4php:<a href="http://logging.apache.org/log4php/docs/appenders.html" title="API Documents" rel="nofollow ugc">Apache Log4php Docs</a>
** Configuration ** You can set configuration path file to export your logger, in the plugin’s settings.

WP MyLogger

This plugin use Apache log4php™ libary for create custom loggers on your file system or mail account. Is possible specify the type (rolling, daily), n …

Incoming Hook Logger vs WP MyLogger