python - Sentry keeps returning nonexistent incident id's -

We have a project in Django. I use sentry to gather information on HTTP 500 errors.

There is an option to add event information to request header in the box, so you can handle it in your app.

There is a mixture of Tastypie which looks like this:

  class Sentry500Mixin (object): def _handle_500 (self, request, exception): if not isinstance (exception , TastypieError) and the settings are not. DEBUG: sentry_exception_handler (Request = request) data = {'error_message': 'Sorry, this request could not be processed.', 'Event': getattr (request, 'Sentry', none)} back self .error_response Request, Data, response_class =  

When 500 error occurs, we receive responses like this:

    < Code> {"Error_message": "Sorry, this request could not be processed.", "Event": {"id": "3459b30f87ea4116a0a2855be576bbb3", "project_id": "5"}}  

The thing is that if you take ID of this incident and you If you go to the entry, then it is a good chance that there will be no incident with this ID, and there is no such incident which looks like this, I am sure that I am checking the right project and if this incident has not been created Logically, the orthodontist can not back you an ID, but it did.

Any help and ideas are greatly appreciated. Thanks.

As @Eric-e in a comment Explained, event_id is generated on the client.

There is no guarantee of the UDP protocol.

Are you using the UDP protocol? If you are, then the map does not map for a real event in the event_id sect. Router / Switch / Network Tool Your package may have lost any guarantees with the UDP that wrt delivery, order, or duplicate packets.

I am assuming the code for code as HTTP / HTTPS TCP .

Solution:

• Check the double firewall rules,
• Try other protocols and make sure that it is not a problem with the sentry server.

Why use UDP?

• Some handshake = it's fast,
• No connection = break the connection There is no problem with (such as reboot for Sentry Server).