Takayuki Miyauchi

TAROSKY INC.

Once you have installed and activated it, you can check the following activities.
<h3>Features</h3>
<ul>
<li>Super lightweight and it doesn’t affect site’s performances.</li>
<li>It has passed over 100 patterns unit test, you can use it with confidence in the enterprise.</li>
<li>Extensible event saving logs, so you can develop own add-ons for collecting it.</li>
<li>Saving logs the following activities on WordPress
<ul>
<li>Publish, update or delete published posts.</li>
<li>Activate or deactivate plugins or themes.</li>
<li>Updating WordPress core, plugins, language files.</li>
<li>Users login action</li>
<li>Login and posting via XML-RPC</li>
<li>PHP errors (On the debug mode, it also save Warning and Notice)</li>
</ul>
</li>
<li>WP-CLI command ready.</li>
</ul>
<h3>Detail of saving logs</h3>
<ul>
<li>WordPress
<ul>
<li>Core updates</li>
<li>Plugin/Theme updates</li>
<li>Language updates</li>
</ul>
</li>
<li>Post/Page/Attachment
<ul>
<li>Created</li>
<li>Updated</li>
<li>Deleted</li>
</ul>
</li>
<li>Plugin
<ul>
<li>Activated</li>
<li>Deactivated</li>
</ul>
</li>
<li>Theme
<ul>
<li>Switched</li>
</ul>
</li>
<li>User
<ul>
<li>Logged in</li>
</ul>
</li>
<li>XML-RPC
<ul>
<li>Authenticated</li>
<li>Created</li>
<li>Updated</li>
<li>Deleted</li>
</ul>
</li>
<li>PHP
<ul>
<li>Errors</li>
<li>Warnings (WP_DEBUG only)</li>
<li>Notices (WP_DEBUG only)</li>
</ul>
</li>
</ul>
<h3>WP-CLI</h3>
Get a list of logs.
<pre><code>$ wp log list --posts_per_page=5
</code></pre>
Get a list of specific level of logs.
<pre><code>$ wp list --level=error --posts_per_page=5
</code></pre>
<h3>Issues</h3>
<a href="https://github.com/tarosky/logbook" rel="nofollow ugc">https://github.com/tarosky/logbook</a>

Logbook

great!

色々なことをログに残せるので、どう変更したか後で見返せれて便利です！
そして、XML-RPCのログインをwarmで警告してくれるので、改竄を防げれて安心です。
もうこのプラグインなしではやっていけられません。

Excellent!!

Great!!!

This plugin is for logging users' activities. You can check anytime who and what has changed.

Akeda Bagus

This plugin is intended for developer to send data to Simperium. Followings are use cases in which this plugin might come in handy:
<ol>
<li>You need post-processing (for instance pinging dozen web services after a post is published) without blocking request. In this case you call provided actions or helper methods, then you spawn long-live process (either from the same server or different server) that listens to changes from your Simperium bucket for post-processing.</li>
<li>You need to log events that happen during request lifecycle under restricted circumstances (for instance it won’t possible to access log files on the server).</li>
</ol>
How to use it
Once this plugin is installed and activated, you can send data to Simperium in following ways:
<ol>
<li>Via action hook: <code>do_action( 'simperium_send_data', $bucket, $data )</code> or <code>do_action( 'simperium_send_buffered_data', $bucket, $data )</code>. The first hook, will send the <code>$data</code> immediately, while the later will send the data to buffer and will send all buffered data to Simperium at once after calling <code>do_action( 'simperium_flush_buffer', $bucket )</code>. If <code>$bucket</code> arg is provided, it only flushes buffered data that’s targetted to <code>$bucket</code>.</li>
<li>Via helper method: <code>WP_Simperium::send_data( $bucket, $data )</code> or <code>WP_Simperium::send_buffered_data( $bucket, $data )</code>. To flush buffer, you call <code>WP_Simperium::flush_buffer( $bucket )</code>. Again, <code>$bucket</code> arg is optional.</li>
</ol>
The value of <code>$data</code> MUST BE in key-value array structure as nested structure is not supported by Simperium.
Before using the action hooks or helper methods, you need to supply Simperium app credentials via <code>simperium_config</code> filter, for example:
<pre><code>add_filter( 'simperium_config', function() { return array( 'app_id' => 'YOUR_APP_ID', 'api_key' => 'YOUR_API_KEY', ) } ); </code></pre>
In addition to <code>app_id</code> and <code>api_key</code> you can pass <code>username</code> and/or <code>access_token</code> to the array config. If <code>access_token</code> is omitted, the plugin will request <code>access_token</code> from Simperium with provided <code>username</code> (if exists) or <code>get_bloginfo( 'admin_email' )</code> and store the info in option. Subsequent calls will read <code>access_token</code> information from option, but can be bypassed by providing <code>access_token</code> in array config. It’s preferred to supply your own <code>access_token</code> or <code>username</code> that hasn’t registered yet. Please keep in mind that token has 30 days life span. If you’re using <code>access_token</code> that’s automatically retrieved by the plugin, you don’t need to worry as scheduled event will refresh the token per 29 days.
Sender Examples
I’ve created <a href="https://github.com/gedex/wp-simperium-sender-examples" rel="nofollow ugc">sender examples plugin</a> that you can use as a starting point, though it will run without any customization. Currently it has following features:
<ul>
<li>Send post data once post status is transitioned to public.</li>
<li>Send new comment.</li>
<li>More will come later..</li>
</ul>
Consumer Examples
I’m working to provide listener apps, written in PHP (stay tuned!), for now you can check <a href="https://simperium.com/samples/" rel="nofollow ugc">Simperium examples</a> and their awesome libraries.
Contributing
<ul>
<li>Development of this plugin is done on <a href="https://github.com/gedex/wp-simperium" rel="nofollow ugc">GitHub</a>. Pull requests are always welcome.</li>
<li>For Sender apps feedback, please check its <a href="https://github.com/gedex/wp-simperium-sender-examples" rel="nofollow ugc">GitHub repo</a>.</li>
<li>For Consumer apps feedback, please stay tuned!</li>
</ul>

Simperium

This plugin contains easy-to-use API that uses WP HTTP API to send data to Simperium.

Logbook vs Simperium