# Java Rich Client Instrumentation

**URL:** <https://community.dynatrace.com/t/java-rich-client-instrumentation/9342>\
**Category:** Open Q&A\
**Tags:** oneagent, java\
**Created:** [November 24, 2017, 3:19pm UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342 "2017-11-24T15:19:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\
**Post date:** [November 24, 2017, 3:19pm UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342/1 "2017-11-24T15:19:44Z")

</div>

Is Java rich client instrumentation on the Roadmap for Dynatrace?

---

<div class="post-metadata">

**Author:** ![kristof\_renders](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/kristof_renders/32/19857_2.png) [@kristof\_renders](https://community.dynatrace.com/u/kristof_renders)\
**Post date:** [November 24, 2017, 3:32pm UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342/2 "2017-11-24T15:32:41Z")

</div>

Hi Patrick,

This is already possible by defining custom service detection rules.

There you can add custom entry points.

Not as automated as with AppMon but it does the trick.

KR,  
Kristof

---

<div class="post-metadata">

**Author:** ![Joe\_Hoffman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/joe_hoffman/32/30752_2.png) [@Joe\_Hoffman](https://community.dynatrace.com/u/Joe_Hoffman)\
**Post date:** [November 24, 2017, 6:31pm UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342/3 "2017-11-24T18:31:38Z")

</div>

Patrick,

Depending on what rules you try to define, you might run into a limitation in Dynatrace where it restricts what classes can be defined as a custom entry point. AppMon did not have such a limitation. This likely could happen when defining a rule such as java.lang.x.y.z. These types of rules can be defined but requires manual editing of the associated JSON text, something only possible with elevated privileges thru the debug UI. There has been discussion about permanently putting in rules for rich clients, but in the meantime this workaround worked great for me for a recent opportunity which sealed the deal. Ping me for details.

---

<div class="post-metadata">

**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\
**Post date:** [November 27, 2017, 7:33am UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342/4 "2017-11-27T07:33:25Z")

</div>

We are currently evaluating for a customer where both appmon and SaaS/Managed are in use already, so both would be an option for that application.

For SaaS/Managed, we would instrument the application with a PaaS agent, then define the custom entry points?

---

<div class="post-metadata">

**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\
**Post date:** [February 13, 2018, 1:34pm UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342/5 "2018-02-13T13:34:57Z")

</div>

For Reference:

With OpenKit it will be possible to get Real User Monitoring data from rich clients and trace web requests to the backend!

---

<div class="post-metadata">

**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\
**Post date:** [May 22, 2018, 8:36am UTC](https://community.dynatrace.com/t/java-rich-client-instrumentation/9342/6 "2018-05-22T08:36:20Z")

</div>

Tested it with a java rich client an it worked great for both appmon and dynatrace.