[ https://issues.jboss.org/browse/WFLY-10847?page=com.atlassian.jira.plugin... ] Gary Brown commented on WFLY-10847: ----------------------------------- [~juraci.costa] Based on the examples above, if we go for one tracer per EAR then all tracing is reported against the same "service" - which might be ok, but doesn't necessarily provide the clarity about what activity occurred in the individual components. If however we take the other route, and a tracer per component in the EAR, then I assume this would also mean that each EJB Jar would also have its own tracer? Not necessarily a bad thing if being used by multiple WAR files in the same EAR, but may be over the top of the EAR contains many individual EJB Jars. Two questions: 1) Is it possible to provide a configuration option that would enable switching between either mode - so it becomes a user decision? 2) If a tracer is created per component in the EAR, can the "service name" be composed of the EAR and deployment name? -- This message was sent by Atlassian JIRA (v7.5.0#75005)