https://community.dynatrace.com/t5/Real-User-Monitoring/How-can-i-search-for-the-services-in-the-new-and-awesome/m-p/298087#M7332 <P>I’ve been exploring the new and "awesome" <STRONG>Experience Vitals</STRONG> app lately. While the UI is sleek and the focus on modern web metrics is great, I’m finding myself a bit lost trying to replicate the 100% visibility I had in the "classic" views. Specifically, I’m struggling with two things:</P><P><STRONG>1. Where is the Service Flow in the new app?</STRONG></P><P>In the old world, jumping from a User Action to the <STRONG>Service Flow</STRONG> was a one-click journey. In Experience Vitals, I can only see a fraction of what I used to.</P><UL><LI><P>Am I missing a hidden button or an "Intent" to see the backend services called by the app?</P></LI><LI><P>What is the fastest way to get from a frontend "Experience" metric to the actual Service Flow in this new ecosystem?</P></LI></UL><P><STRONG>2. The OTel vs. OneAgent Backtrace Dilemma</STRONG></P><P>I’ve started instrumenting some services with <STRONG>OpenTelemetry</STRONG>, but I’ve hit a wall: I can’t seem to get a proper <STRONG>Backtrace</STRONG> for traceability. It feels like I'm losing that "Smartscape magic" where everything is automatically stitched together.</P><P>To help the discussion, I’ve put together this quick comparison of what we might be "trading off" when moving from OneAgent to OTel in the new apps: somethin like this</P><P>&nbsp;</P><TABLE><TBODY><TR><TD><STRONG>Feature</STRONG></TD><TD><STRONG>Dynatrace OneAgent (Auto)</STRONG></TD><TD><STRONG>OpenTelemetry (Manual)</STRONG></TD></TR><TR><TD><SPAN><STRONG>Setup</STRONG></SPAN></TD><TD><SPAN>Zero-code, automatic injection.</SPAN></TD><TD><SPAN>Manual SDK instrumentation &amp; context propagation.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Traceability</STRONG></SPAN></TD><TD><SPAN>Automatic Backtrace and Service Flow.</SPAN></TD><TD><SPAN><STRONG>Context gaps</STRONG> if propagators aren't perfect.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Code-Level Depth</STRONG></SPAN></TD><TD><SPAN>Deep (Method-level, CPU/Memory profiling).</SPAN></TD><TD><SPAN>Limited to manually created Spans/Attributes.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Maintenance</STRONG></SPAN></TD><TD><SPAN>Auto-updates via OneAgent.</SPAN></TD><TD><SPAN>Manual dependency management &amp; SDK updates.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Integration</STRONG></SPAN></TD><TD><SPAN>Native "out-of-the-box" in all apps.</SPAN></TD><TD><SPAN>Requires Grail/DQL knowledge for full visibility.</SPAN></TD></TR></TBODY></TABLE><P>&nbsp;</P><P><STRONG>Has anyone found a way to bridge this gap?</STRONG> Is there a specific configuration in the OTel Collector or a shortcut in the new UI that makes this "awesome" app as powerful as the classic one for deep-dive analysis?</P><P>Looking forward to your insights!</P> Tue, 21 Apr 2026 21:55:39 GMT rgarzon1 2026-04-21T21:55:39Z https://community.dynatrace.com/t5/Real-User-Monitoring/How-can-i-search-for-the-services-in-the-new-and-awesome/m-p/298087#M7332 <P>I’ve been exploring the new and "awesome" <STRONG>Experience Vitals</STRONG> app lately. While the UI is sleek and the focus on modern web metrics is great, I’m finding myself a bit lost trying to replicate the 100% visibility I had in the "classic" views. Specifically, I’m struggling with two things:</P><P><STRONG>1. Where is the Service Flow in the new app?</STRONG></P><P>In the old world, jumping from a User Action to the <STRONG>Service Flow</STRONG> was a one-click journey. In Experience Vitals, I can only see a fraction of what I used to.</P><UL><LI><P>Am I missing a hidden button or an "Intent" to see the backend services called by the app?</P></LI><LI><P>What is the fastest way to get from a frontend "Experience" metric to the actual Service Flow in this new ecosystem?</P></LI></UL><P><STRONG>2. The OTel vs. OneAgent Backtrace Dilemma</STRONG></P><P>I’ve started instrumenting some services with <STRONG>OpenTelemetry</STRONG>, but I’ve hit a wall: I can’t seem to get a proper <STRONG>Backtrace</STRONG> for traceability. It feels like I'm losing that "Smartscape magic" where everything is automatically stitched together.</P><P>To help the discussion, I’ve put together this quick comparison of what we might be "trading off" when moving from OneAgent to OTel in the new apps: somethin like this</P><P>&nbsp;</P><TABLE><TBODY><TR><TD><STRONG>Feature</STRONG></TD><TD><STRONG>Dynatrace OneAgent (Auto)</STRONG></TD><TD><STRONG>OpenTelemetry (Manual)</STRONG></TD></TR><TR><TD><SPAN><STRONG>Setup</STRONG></SPAN></TD><TD><SPAN>Zero-code, automatic injection.</SPAN></TD><TD><SPAN>Manual SDK instrumentation &amp; context propagation.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Traceability</STRONG></SPAN></TD><TD><SPAN>Automatic Backtrace and Service Flow.</SPAN></TD><TD><SPAN><STRONG>Context gaps</STRONG> if propagators aren't perfect.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Code-Level Depth</STRONG></SPAN></TD><TD><SPAN>Deep (Method-level, CPU/Memory profiling).</SPAN></TD><TD><SPAN>Limited to manually created Spans/Attributes.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Maintenance</STRONG></SPAN></TD><TD><SPAN>Auto-updates via OneAgent.</SPAN></TD><TD><SPAN>Manual dependency management &amp; SDK updates.</SPAN></TD></TR><TR><TD><SPAN><STRONG>Integration</STRONG></SPAN></TD><TD><SPAN>Native "out-of-the-box" in all apps.</SPAN></TD><TD><SPAN>Requires Grail/DQL knowledge for full visibility.</SPAN></TD></TR></TBODY></TABLE><P>&nbsp;</P><P><STRONG>Has anyone found a way to bridge this gap?</STRONG> Is there a specific configuration in the OTel Collector or a shortcut in the new UI that makes this "awesome" app as powerful as the classic one for deep-dive analysis?</P><P>Looking forward to your insights!</P> Tue, 21 Apr 2026 21:55:39 GMT https://community.dynatrace.com/t5/Real-User-Monitoring/How-can-i-search-for-the-services-in-the-new-and-awesome/m-p/298087#M7332 rgarzon1 2026-04-21T21:55:39Z