ccprog

This plugin is derived from the no longer supported 
<a href="https://wordpress.org/plugins/wordpress-logging-service" rel="ugc">WordPress Logging Service</a>. 
Despite that it is not compatiple with it, and there is no upgrade path from one 
to the other.
<h4>Features</h4>
<ul>
<li>No log entries generated by the plugin itself, all come from external API calls</li>
<li>Organisation of log entries in freetext categories</li>
<li>Severity levels</li>
<li>Freetext log messages</li>
<li>Entries can be marked as seen and then filtered from being displayed again</li>
<li>Filtering by minimum severity level</li>
<li>Sort by date, category, user name, severity or blog name (in Multisite installations)</li>
<li>Access to the log page can be granted by user role</li>
</ul>
<h3>API</h3>
<h4>Constants</h4>
Check to test if the plugin is active:
<pre><code>CLGS = true
</code></pre>
Defined severity levels:
<pre><code>CLGS_NOSEVERITY = 0
CLGS_INFO = 1
CLGS_NOTICE = 2
CLGS_WARNING = 3
CLGS_ERROR = 4
CLGS_FATALERROR = 5
</code></pre>
<h4>Functions</h4>
<pre><code>clgs_is_registered ( $category )
</code></pre>
<ul>
<li><code>string $category</code></li>
</ul>
returns <code>true</code> if <code>$category</code> is registered.
<pre><code>clgs_register ( $category, $description )
</code></pre>
registers <code>$category</code> as a log category. <code>$description</code> will be shown in the 
management page. 
It is good practice to use unique categories for each plugin that publishes 
log messages.
<ul>
<li><code>string $category</code> At most 190 (unicode) characters</li>
<li><code>string $description</code> can contain HTML same as comments (filtered by 
 wp_kses_data)</li>
</ul>
returns <code>false</code> if the category is already registered or it is too long.
<pre><code>clgs_clear ( $category )
</code></pre>
deletes all log entries of <code>$category</code>.
<ul>
<li><code>string $description</code> existing category</li>
</ul>
returns number of deleted entries or <code>false</code> if action failed.
<pre><code>clgs_unregister( $category );
</code></pre>
deletes all log entries and then removes <code>$category</code>.
<ul>
<li><code>string $description</code> existing category</li>
</ul>
returns <code>false</code> if false if action failed.
<pre><code>clgs_log( $category, $text, $severity = null, $user = null, $blog_id = null, $date = null );
</code></pre>
writes a new log entry in the specified category
<ul>
<li><code>string $description</code> a registered category name</li>
<li><code>string $text</code> the logged message, can contain HTML same as comments (filtered 
by <code>wp_kses_data</code>)</li>
<li><code>int $severity</code> one of defined severity levels (see above); if missing defaults to 
 CLGS_NOCATEGORY</li>
<li><code>int | string | WP_User $user</code> user id, slug or WP user object are aceptable; if missing 
defaults to current user (or a placeholder if none is logged in)</li>
<li><code>int $blog_id</code> blog id; if missing defaults to current blog</li>
<li><code>int | double | string $date</code> a UNIX timestamp or a string recognized by <code>strtotime()</code>; 
if missing defaults to current time</li>
</ul>
returns <code>false</code> if entering the log failed.

Custom Logging Service

Provides a simple API for storing miscellaneous log entries and displays them in a Dashboard subpage.

webheadcoder

What happens if WP-Cron stops working?
WordPress, Themes, and Plugins would never know if a new version is out. You could login to your website everyday for months, and never see any notices about updates. If you’re not careful you’ll soon have an out of date WordPress installation susceptible to hackers. Scheduled posts would never get published, auto drafts never deleted… you get the picture. Your website would crumble up and die.
Use Woocommerce? Subscriptions? Customers would never get billed again! Sessions would never be deleted. Scheduled sales would never appear. Your website would become bloated while giving away subscriptions for one time payments.
WP-Cron is important. So make sure it keeps working.
Think of this plugin as insurance, but free. WordPress, plugins, themes, and servers are all moving parts that can be updated at anytime. You can’t guarantee any of these changes won’t break your website in some way. While it’s not likely WP-Cron will stop working, if it does, you better know about it.
Every 24 hours this plugin automatically checks to see if WP-Cron is still able to run. Obviously, it does not depend on WP-Cron. Instead it sets its own transients that expire over 24 hours. Whenever the transient expires it checks to make sure WordPress can run WP-Cron. If an unexpected error occurs the you’ll get an email.
In addition to checking if WP-Cron CAN run, this plugin now logs all hooks running with WP-Cron and if they fail or complete. You’ll be able to see what ran, when it ran, how long it took, and if it completed.
For your convenience The WP-Cron Status Checker is displayed on your WordPress admin dashboard. The status page is accessible through the Tools -> WP Cron Status side menu.
Know when WP-Cron doesn’t complete
When a WP-Cron hook fails you’ll get notified soon after. A hook “fails” when it takes longer than 5 minutes to complete. You’ll get an email within 24 hours (or based on the plugin’s settings) to notify you of any failures.
Sometimes a plugin runs some code that abruptly exits the process and there is no way of knowing when it stopped. WP-Cron Status Checker does it’s best to detect this type of code. If it’s caught, the elapsed time is not recorded and you’ll see “N/A” with an “Incomplete” status. Other times when it’s caught you’ll see an “Exit” status which is considered complete. <a href="https://webheadcoder.com/wp-cron-status-checker/" rel="nofollow ugc">Please see the plugin page for more on completion statuses.</a>
PRO Version 
The PRO version removes the 3 log limit and lets you choose to keep logs longer and email more frequently. Please see more on the plugin page: <a href="https://webheadcoder.com/wp-cron-status-checker/" rel="nofollow ugc">https://webheadcoder.com/wp-cron-status-checker/</a>

WP-Cron Status Checker

I know I created this plugin, but I am also using it and it has warned me WP Cron stopped working.  I'm not sure what the error was.  WP Cron just stopped working for a short while and then started working the next day right before I contacted the web host.

Caught an error

I debug WordPress websites for a living and a stopped, paused or failed cron is often a problem. I use this plugin to help in the process. Thanks to the dev!

One request. At first, it was very hard to find where to find the status (it's a widget on the dashboard btw). It would be helpful if this was mentioned somewhere in the description of the plugin (unless its there already and I missed it). 

Cheers!

Very handy tool in my debug tool kit

This is an easy way to check if WP-cron is enabled and jobs are actually running. Don't let the relatively low number of active installations mislead you, I suspect many people may use this plugin just like I did - install it just to check WP-cron is doing ok, then remove the plugin again.

My only criticism is that I had expected to be able to view the WP-cron status on this plugin's settings page, instead I had to look for it in the Dashboard.

Good tool to check WP-cron


I installed by mistake, intending to use a simple tool to monitor and log WP-Cron activity. It appears, this is now another freemius plugin which seems to me to be a bait, because description and screenshots are not accurate and up to date.



To use this plugin is now required to give all your personnal data or to register/subscribe. This shouldn't be required for such limited functionality plugin. An unnecessary and intrusive step for something as simple as viewing cron logs



Thankfully, better alternatives exist. Installed by mistake, uninstalling by will.


Almost a bait because it requires personnal data

If WP-Cron runs important things for you, you better make sure WP-Cron always runs!

Custom Logging Service vs WP-Cron Status Checker