Overriding the checksum of an event client-side

[Sven Grunewaldt]

Hi,

I'm trying to understand how Sentry groups its messages. From the different sources I checked it looks like a message will receive a checksum which identifies the group under which it will be "saved". [1]

What I don't completely understand is how these checksums are generated. Apparently it will be either sent by the client or will be created by on of the interfaces associated with the event.

When I log a line with send_message in my PHP file it will ALWAYS land in the same group, regardless of the message, the parameters or extra data. As far as I understand this is because the Sentry server will create a checksum based on the stacktrace, which is obviously always the same.

Considering the info I found I guess I need to override the checksum client side, but I couldn't find any info on how to do that exactly - just putting a "checksum" key in the extra data didn't work.

[1]: http://stackoverflow.com/questions/13331973/how-does-sentry-aggregate-errors

[@@]

I changed the client

--
You received this message because you are subscribed to the Google Groups "sentry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to getsentry+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[David Cramer]

If the stack trace is the same and its not the same messages then it must be an incorrect stack trace. If you have an example that would be useful so we could squash the bug.

In the near future we will be removing client side checksums to simplify application logic (it's already been done in various clients).