Error tracking for Minecraft plugins

The problem

When your plugin throws on a server, the console shows a stack trace and the server keeps running. The owner might send it to you; usually they don't. You find out from a one-star review, weeks later, with no version and half a stack trace.

How it works

1. Add the SDK and call PluginAnalytics.start(this, key) in onEnable.
2. Every exception that goes through your plugin's code is captured on the server: event handlers, commands, tasks and anything you log with an exception.
3. Player names, IP addresses and UUIDs are replaced before anything is sent, and errors arrive in your dashboard grouped by stack trace.

try {
    database.save(arena);
} catch (SQLException e) {
    analytics.captureError(e); // errors you catch yourself, too
}

What you see

• Issues grouped by cause, with how many times and on how many servers
• The plugin versions where each issue was first and last seen
• Full stack traces, readable even for ProGuard-obfuscated plugins
• Regressions: an issue you resolved that comes back in a newer version notifies you
• Your plugin's own log lines from every server, grouped by message (Pro)

Questions