Missing fingerprints on events

[dcramer]

Might try to resolve this myself, but events right now aren't fingerprinted at all which means every node's unique error becomes a unique issue in Sentry, but what you really want is that every unique type of error is a unique issue (and every pod experiencing that error bubbles up to the same issue).

There's a few approaches to this, but the current sentry-kubernetes does this fairly well.

[dcramer]

Example of an event from sentry-kubernetes: https://sentry.io/share/issue/be9e0777979344f3b76af9acffff9acc/

[dcramer]

Also realizing this ticket is not correct - you are setting a fingerprint, but I would advise removing the node name from it. That would achieve what I'm looking for, and you'll find it makes Sentry a lot more powerful.

It, for example, allows you to create a breakdown of all nodes experiment out of memory issues.

[wichert]

I don't actually include the node name in the fingerprint directly, so I'm wondering where that comes from.