Skip to main content

Why did User Misery suddenly stop?

Issue

I want to know why User Misery showed data and then dropped to nothing after a certain date.

Applies To

  • All SaaS Customers

  • Releases

  • Performance Metrics

Resolution

User Misery counts unique users whose load times are more than four times your satisfactory threshold. If Sentry can’t identify the users, the metric will be empty.

One common cause of a sudden change is enabling Prevent Storing of IP Addresses.

For anonymous traffic, Sentry often uses the IP address as the user ID. If the IP is scrubbed to null and there are no other user fields available, Sentry can’t calculate User Misery.

Check whether that setting changed:

  1. Go to Organization Settings → Audit Log.

  2. Filter for project.edit.

  3. Look for an edit that set scrub_ip_address to True for the project, around the date when User Misery stopped showing data.

You can also check Project Settings → Security & Privacy to see whether Prevent Storing of IP Addresses is enabled.

Fix (pick one):

  • Turn Prevent Storing of IP Addresses off if you’re OK with storing IP addresses, or

  • Keep IP scrubbing enabled and identify users in the SDK using id, email, or username, so User Misery doesn’t depend on the IP address. See Identify Users.

For more details on how the metric works, see User Misery.

Did this answer your question?