Features
- SOAP Tracing
- Currently you still have to manually add the following SOAP Handlers:
org.stagemonitor.tracing.soap.TracingClientSOAPHandler,org.stagemonitor.tracing.soap.TracingServerSOAPHandler. These add server and client spans for JAX-RS SOAP calls and propagate the span context (aka. correlation ids/B3 header). - Correlation of pageload spans with backend spans. This means that the span of the initial browser page load is attached to the same trace as the backend spans. When using the stagemonitor Kibana plugin, the browser span and the backend span are displayed in the same graph.
- Don't log errors when reporting spans to Elasticsearch fails (#300)
- Add logging of non-default configuration options (#291)
- Adds a
stagemonitor.versiontag to all spans. This is useful for example if you want to find out which of your services are still using old stagemonitor versions. Also logs the version on startup.
Bug Fixes
- Fix Ajax table in in-browser-widget (#295)
- Fix false negative status log saying that DataSource instrumentation failed
- URL encode ids in ES incident repo to support whitespaces (#301)
Special anouncement
We are currently working on a stagemonitor Kibana plugin which visualizes distributed traces: https://github.com/stagemonitor/stagemonitor-kibana