Improvements

Upgrade JMXFetch to 0.29.0 and enable JMXFetch by default. #838
- To disable it add the one of the following config:
  - System Property: dd.jmxfetch.enabled=false
  - Environment Variable: DD_JMXFETCH_ENABLED=false
Bundled jmx integrations must now be configured via (default still disabled):
- System Property dd.jmxfetch.<integration>.enabled=true
- Environment Variable DD_JMXFETCH_<INTEGRATION>_ENABLED=true
New config options are passed through that enable datadog-agent config files to be used for JMXFetch. For example, the following will load jmx configs in those two files that have jvm_direct: true in their instance setup:
- dd.jmxfetch.config.dir=/opt/datadog-agent/etc/conf.d
- dd.jmxfetch.config=activemq.d/conf.yaml,jmx.d/conf.yaml
- Environment variables can also be used: DD_JMXFETCH_CONFIG_DIR and DD_JMXFETCH_CONFIG
JMXFetch now uses the same logging system as dd-java-agent. This will help reduce logging noise when using JMXFetch.
Allow async propagation by default within Spring Controllers #856

Fixes

Prevent Glassfish's classloader from blacklisting classes added to the bootstrap by the agent #839
Improve Kafka instrumentation scope handling #859
Avoid setting Kafka headers when connected to an old/incompatible broker #836
Use default service name for Kafka Consumers #854 (Reverted in #861 -- 0.29.1)
Use default service name for RabbitMQ Consumers #855 (Reverted in #861 -- 0.29.1)

For a full list of changes please reference the milestone for this release.