Should you use a log or a metric?

Publisher preview

> TL;DR: Logs are for debugging, metrics are for analysis. Log what was true when something happened, so you can reconstruct it later. Make it a metric when there's a number you'll track over time, even when nothing is wrong. Since Sentry added Logs and Application Metrics, there are now two ways to record that something happened in your app, and they can look pretty similar: Sentry.logger.info("user.signup") versus Sentry.metrics.count("user.signup"). Both store attributes, both include shared context automatically, and both can be filtered, grouped, and counted. So when you're instrumenting your code, which one do you reach for? If you've read when to reach for errors, traces, logs, and metrics, you know we've covered this before. Logs and metrics are the two that trip people up most, and one signup flow is enough to show when to use which.

A saved ApplyDjinn digest is not available for this story yet.

This preview is supplied by the publisher. The complete publication remains at its original source.