This version contains an important bug fix and all users of 0.80.* are strongly encouraged to update.
Bug Fixes
- Previously, a timer for each distinct operation name was created. Now only operation names which are derived from Spring MVC controller methods, JAX-RS endpoints,
@Tracedmethods and JDBC queries (whose operation names are the name of the topmost method on the call stack which belongs to your project) are timed. This considerably reduces the cardinality of the operation name and the amount of created timers.- Attention: a malicious user could abuse the previous behavior by accessing a large number of random (even non existing) URLs. A timer for each of those URL would be created which could potentially fill the heap and overwhelm your time series database. Even if users are not malicious, a far higher number of timers will be created which caused trouble for some users.
- The operation name of requests from Spring's RestTemplate don't contain query parameters anymore.
- Note that by default, no timers will be created for external http requests anymore as the cardinality of the operation names can be quite large, for example when the url contains path parameters.
- Previously a timer would have beed created for each distinct url. Because the url did also contain the query parameters, there has been the potential for a explosion of timers being created.
Enhancements
- End User Monitoring
- Non-sampled EUM spans are not processed so that they require less resources
- Introduced new field
timing.resourcewhich is a combination of all timing values which belong to resource fetching. See https://w3c.github.io/navigation-timing/timestamp-diagram.svg - Discarding of beacons with invalid timing values (time < 0 || time > 10min)
- Don't log Elasticsearch credentials (#282)