You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Added support for tracking [time spent by span type](https://www.elastic.co/guide/en/kibana/7.3/transactions.html).
5
+
Can be disabled by setting [`breakdown_metrics`](https://www.elastic.co/guide/en/apm/agent/java/7.3/config-core.html#config-breakdown-metrics) to `false`.
6
+
* Added support for [central configuration](https://www.elastic.co/guide/en/kibana/7.3/agent-configuration.html).
7
+
Can be disabled by setting [`central_config`](https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-central-config) to `false`.
8
+
* Added support for Spring's JMS flavor - instrumenting `org.springframework.jms.listener.SessionAwareMessageListener`
9
+
* Added support to legacy ApacheHttpClient APIs (which adds support to Axis2 configured to use ApacheHttpClient)
10
+
* Added support for setting [`server_urls`](https://www.elastic.co/guide/en/apm/agent/java/1.x/config-reporter.html#config-server-urls) dynamically via properties file [#723](https://github.com/elastic/apm-agent-java/issues/723)
* Added option to use `@javax.ws.rs.Path` value as transaction name [`use_jaxrs_path_as_transaction_name`](https://www.elastic.co/guide/en/apm/agent/java/current/config-jax-rs.html#config-use-jaxrs-path-as-transaction-name)
13
+
* Instrument quartz jobs ([docs](https://www.elastic.co/guide/en/apm/agent/java/current/supported-technologies-details.html#supported-scheduling-frameworks))
14
+
* SQL parsing improvements (#696)
15
+
* Introduce priorities for transaction name (#748)
16
+
17
+
Now uses the path as transaction name if [`use_path_as_transaction_name`](https://www.elastic.co/guide/en/apm/agent/java/current/config-http.html#config-use-path-as-transaction-name) is set to `true`
18
+
rather than `ServletClass#doGet`.
19
+
But if a name can be determined from a high level framework,
20
+
like Spring MVC, that takes precedence.
21
+
User-supplied names from the API always take precedence over any others.
22
+
* Use JSP path name as transaction name as opposed to the generated servlet class name (#751)
23
+
8
24
9
25
## Bug Fixes
10
26
* Some JMS Consumers and Producers are filtered due to class name filtering in instrumentation matching
11
27
* Jetty: When no display name is set and context path is "/" transaction service names will now correctly fall back to configured values
12
28
* JDBC's `executeBatch` is not traced
13
29
* Drops non-String labels when connected to APM Server < 6.7 to avoid validation errors (#687)
30
+
* Parsing container ID in cloud foundry garden (#695)
31
+
* Automatic instrumentation should not override manual results (#752)
14
32
15
33
## Breaking changes
16
34
* The log correlation feature does not add `span.id` to the MDC anymore but only `trace.id` and `transaction.id` (see #742).
@@ -862,7 +883,8 @@ it's content is deleted when the application starts.
862
883
A boolean specifying if the agent should integrate into SLF4J's https://www.slf4j.org/api/org/slf4j/MDC.html[MDC] to enable trace-log correlation.
863
884
If set to `true`, the agent will set the `trace.id` and `transaction.id` for the currently active spans and transactions to the MDC.
864
885
You can then use the pattern format of your logging implementation to write the MDC values to your log file.
865
-
If you are using logback or log4j, add `%X` to the format to log all MDC values or `%X{trace.id}` to only log the trace id.With the help of Filebeat and Logstash or an Elasticsearch ingest pipeline,
886
+
If you are using logback or log4j, add `%X` to the format to log all MDC values or `%X{trace.id}` to only log the trace id.
887
+
With the help of Filebeat and Logstash or an Elasticsearch ingest pipeline,
866
888
you can index your log files and correlate them with APM traces.
867
889
With this integration you can get all logs belonging to a particular trace and vice-versa:
868
890
for a specific log, see in which context it has been logged and which parameters the user provided.
@@ -920,6 +942,8 @@ When multiple agents are active, they'll tend towards spreading evenly across th
920
942
If outgoing HTTP traffic has to go through a proxy,you can use the Java system properties `http.proxyHost` and `http.proxyPort` to set that up.
921
943
See also [Java's proxy documentation](https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html) for more information.
922
944
945
+
NOTE: This configuration can only be reloaded dynamically as of 1.8.0
946
+
923
947
924
948
[options="header"]
925
949
|============
@@ -1459,6 +1483,14 @@ The default unit for this option is `ms`
1459
1483
#
1460
1484
# boot_delegation_packages=co.elastic.apm.agent.*
1461
1485
1486
+
# When enabled, the agent will make periodic requests to the APM Server to fetch updated configuration.
1487
+
#
1488
+
# This setting can be changed at runtime
1489
+
# Type: Boolean
1490
+
# Default value: true
1491
+
#
1492
+
# central_config=true
1493
+
1462
1494
# Disables the collection of breakdown metrics (`span.self_time`)
1463
1495
#
1464
1496
# This setting can not be changed at runtime. Changes require a restart of the application.
@@ -1475,7 +1507,7 @@ The default unit for this option is `ms`
@@ -1615,7 +1647,7 @@ The default unit for this option is `ms`
1615
1647
# Type: Boolean
1616
1648
# Default value: false
1617
1649
#
1618
-
# use_jaxrs_path_for_transaction_name=false
1650
+
# use_jaxrs_path_as_transaction_name=false
1619
1651
1620
1652
############################################
1621
1653
# Logging #
@@ -1651,7 +1683,8 @@ The default unit for this option is `ms`
1651
1683
# A boolean specifying if the agent should integrate into SLF4J's https://www.slf4j.org/api/org/slf4j/MDC.html[MDC] to enable trace-log correlation.
1652
1684
# If set to `true`, the agent will set the `trace.id` and `transaction.id` for the currently active spans and transactions to the MDC.
1653
1685
# You can then use the pattern format of your logging implementation to write the MDC values to your log file.
1654
-
# If you are using logback or log4j, add `%X` to the format to log all MDC values or `%X{trace.id}` to only log the trace id.With the help of Filebeat and Logstash or an Elasticsearch ingest pipeline,
1686
+
# If you are using logback or log4j, add `%X` to the format to log all MDC values or `%X{trace.id}` to only log the trace id.
1687
+
# With the help of Filebeat and Logstash or an Elasticsearch ingest pipeline,
1655
1688
# you can index your log files and correlate them with APM traces.
1656
1689
# With this integration you can get all logs belonging to a particular trace and vice-versa:
1657
1690
# for a specific log, see in which context it has been logged and which parameters the user provided.
@@ -1688,6 +1721,8 @@ The default unit for this option is `ms`
1688
1721
#
1689
1722
# If outgoing HTTP traffic has to go through a proxy,you can use the Java system properties `http.proxyHost` and `http.proxyPort` to set that up.
1690
1723
# See also [Java's proxy documentation](https://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html) for more information.
1724
+
#
1725
+
# NOTE: This configuration can only be reloaded dynamically as of 1.8.0
0 commit comments