jpkrohling_jpk

If you are interested in contributing it to the jaegertracing GitHub repository, I'm sure the Jaeger community would welcome it :)

Would you be interested in writing a guest blog post about it?

Jaeger is just the concrete implementation. OpenTracing is what you should think about using when writing your application. That said, you could benefit from automatic instrumentation via OpenTracing framework integration libraries (JAX-RS, Servlets, ...). Or use the Java Agent. But in the end, I think there is value in manually instrumenting your code, specially around your business transactions. This way, you can monitor your business metrics, instead of "http requests" or "cpu load".

There are discussions about it happening. If you haven't yet, join the community and make your opinion heard :)

We have it both in our Terms and Conditions page (hint: Belgium is missing there, but that's a mistake) and in our activation form.

No, we haven't. It's missing only from the Terms and Conditions webpage. We have Belgium in our hearts, in our language switcher and in our activation form :-)

Yes. It's missing in the language switcher because of a technical problem, but you can find Israel on the activation form.

Questions that we'll gladly answer at [email protected] ;-)