Sentry Performance Tracing

[mpass99]

Relates to #270

With Sentry's Distributed Tracing we can connect the Tracing of our applications to get a more detailed view into the time behavior.

For Poseidon we just have to enable the tracing functionality of Sentry. For that see also: 38ffc3e9.

The tracing connection between the application is done automatically by Sentry (via the trace-id http header; See).

With only this we would still have two separate transactions - one for Submission create and one for Submission Score. To join them we can enable the Sentry Tracing for the JavaScript Frontend.

[MrSerth]

Awesome, thanks for getting that started! I was reviewing commit-by-commit and find all changes plausible. Besides reviewing, I also started having a look at Sentry and was happy to see some traces there ;).

What I was still thinking are two things regarding the spans:

1. Should we add additional spans, e.g., in some filters running with every request or other often-used methods?
   This would allow us to see more details, such as shown in this trace.
2. Can we add the current (custom) span names into the "description" field and rather an "identifier" as the current name? This would allow to see the name for spans. For example, compare this custom span to this pre-defined span. We might also come up with an own naming scheme, e.g., poseidon.operation, poseidon.manager, poseidon.storage, poseidon.nomad.execute, influx.send, nomad.query, response.render, ...

Regarding linking: Yes, let's use the trace ID and let's generate it through the JavaScript frontend and pass it along.

[mpass99]

Good remarks!
I added an identifier for the custom spans.
Also, I added more custom spans for the most used and most time consuming functionality, Execute. If you would like to know the time behavior of other methods, please let me know.

[codeclimate]

Code Climate has analyzed commit 7ab8dca and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 69.3% (65% is the threshold).

This pull request will bring the total coverage in the repository to 72.6% (-0.1% change).

View more on Code Climate.

[MrSerth]

Awesome! I was just testing the new tracing with CodeOcean, and it works like a charm!

Let's evaluate the responses once we have some data to identify where to add more details. :)