• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
        • Enterprise Synthetic Monitoring
      • Synthetic Classic
        • Synthetic Classic Open Q&A
      • BSM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Dorian C. · Aug 19, 2014 at 08:53 PM · diagnostics

Filters and Purepath node aggregation

Comment

People who like this

0 Show 0
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

2 Replies

· Add your reply
  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Dorian C. · Aug 19, 2014 at 08:58 PM

I started using Dynatrace a few weeks ago and one of the thigns that bother me when analysing Purepaths is the fact that the amount of nodes explodes on a regular basis since apparently EVERY SINGLE occurence of a method call / event / purepath node in general is displayed in the Purepath tree.

I found a useful option in the configuration of the JDBC sensor pack which allows me to aggregate all of the similar SQL Statements that are children of the same node.

 

I wanted to know if the same was possible for methods or for any node that is not a leaf of the tree. In many cases, this makes Purepaths tedious to read at best, and completely useless in some cases.

Another great feature, if it doesn't already exist, would be to allow for complex inclusive and exclusive filters, and not just a Find feature, in order to select what I want to see or not.

Is anyone else having this problem?!

 

Regards,

Dorian

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users
avatar image

Answer by Dorian C. · Aug 19, 2014 at 09:01 PM

Oh and in case the reason for this is that methods that are called very often shouldn't be instrumented (because of their overhead), well... sometimes the critical piece of information for the diagnosis lies in those methods, we need to know where in the tree and how many times they're called.

Sometimes these methods are also the only thing worth instrumenting, because thats all the app code does (call a method a billion times), and we need to find that out at some point.

Comment

People who like this

0 Show 0 · Share
10 |2000 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Your answer

Hint: You can notify a user about this post by typing @username

Up to 10 attachments (including images) can be used with a maximum of 52.4 MB each and 262.1 MB total.

Welcome to the
Dynatrace Community Forums

Check out the Forum User Guide and Forum Guidelines to learn how to get started.

Community Member of the Month
February 2019

Announcing Dynatrace's Community Member of the Month for February 2019, Larry R.! Click here to read more!

Employee Member of the Month
February 2019

Announcing Dynatrace's Employee Member of the Month for February 2019, Dave M.! Click here to read more!

Live webinar: AIOps done right through enhanced Dynatrace AI root cause detection

Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!

Live webinar: AIOps done right through enhanced Dynatrace AI root cause detection

Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!

NAM 2019 Beta is available

Would you like to have an early taste of what we have cooked up for 2019? We would love to hear your feedback and improve some of the new features. Check NAM 2019 Beta release notes.
Sign up today!

Follow this Question

Answers Answers and Comments

No one has followed this question yet.

Related Questions

Repository Incident 2 Answers

How to interpret the purepath tree 3 Answers

.Net agent connected but no purepath 12 Answers

Share Webdashboard publicly 3 Answers

.NET process version mismatch 1 Answer

Forum Tags

nginx java dotnet docker 6.5 ios customization knowledge sharing browser agent mobileapp sensor chart 7.1 hybris 6.3+ production incidents Dynatrace Managed php javascript processes monitoring nodejs uem splunk license framework good to know installation web services plugin splitting rest webserver reports kubernetes 7.0 errors rum mainframe 6.1 account configuration forum user guide security web dashboard agent load window oneagent upgrade diagnostics search scheduler appmonsaas log analytics database performance warehouse services web performance monitoring user sessions test automation transactionflow measures business transaction migration plugins android dashlet server purelytics 6.2 rest api system profile appmon appmon 7 mobile monitoring collector adk messagebroker purepath apache guardian appmon iis 7.2 user actions dashboard mq kibana client continuous delivery unique users postgresql sensors documentation alerting auto-detection 6.3 administration
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A
      • Enterprise Synthetic Monitoring
    • Synthetic Classic
      • Synthetic Classic Open Q&A
    • BSM Open Q&A