Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

skinnyandbald's avatar

Laravel Flare -- NOT grouping errors thrown for different tenants

Hey! We're using Laravel Flare -- and no luck w/ Googling.

We have multiple tenants using our app -- today, if two separate "tenants" throw the same error (e.g. Updating customer failed: Customer does not exist), Flare groups them.

We've added custom context to identify the tenant BUT the flare errors are still grouped today.

If the SAME error is thrown but for different tenants, we want them to show up as separate errors (so it's clear in our logging that it's happened to different customers).

Is there a way to throw an error and add context for Flare so we don't log an error for two separate tenants under the same error?

It'd seem like authenticated users would trigger separate errors -- I'm speculating based on docs -- but these are server-triggered events, not run on behalf of authenticated users.

Any tips or suggestions? I've always been a fan of Flare for basic apps, but is this a situation where Sentry, Honey Badger (or something else) would be a fit for exception handling & logging?

0 likes
0 replies

Please or to participate in this conversation.