Skip to end of metadata
Go to start of metadata

The list below provides an overview about the planned upcoming features.

  • Support for Firefox - DONE!
  • AJAX Memory diagnostics (Browser, DOM)
  • De-obfuscation of JavaScript code
  • Timeline visualization and correlation of JavaScript errors and exceptions - DONE!
  • Automated regression reporting DONE! - In Premium

Following is a list of all additional wishes that came in on this page over the last couple of weeks

  • Support for Chrome
  • Support for IE Web Browser Control
  • Save Filter Settings on Views
  • Memory Diagnostics -> Analyze Memory and DOM Leaks
  • Stop Recording Option - DONE!
  • Support for Automation -> automatically extract information from a recorded session - DONE! - In Premium
  • Support for HAR File Format - DONE!
  • Support for showslow.com - DONE!
  • Additional Page Timing Metrics, e.g.: Time to First Render, Time to DOM Ready, ... - DONE!

You are invited to comment on the proposed features and explain why they are important to you. To do so, simply log in and use the comment function below. We will take your votes and comments for future planning into consideration. 

  • No labels
  1. Integration with other monitoring tools (i.e. Keynote or Gomez) to help debug their transactions

  2. Drill-up : double click on a function in JavaScript source should show me everything where this function is involved. Stack, calls, times, etc ... I can sense this information is all "behind" but it is not possible to reach it at the click of a button.

    1. You can get this information in the HotSpot view.
      1) Locate your method
      2) Double Click it
      3) Analyze who called the method in the Back Trace Tree
      4) Analyze which calls were done by this method in the Forward Trace Tree

    • More specific Filters please. Plus possibility to save filter settings to filter sets.

          We do AJAX analysis spearate from GUi analysis (which images are loaded, etc.).

    • more specific mouse event filters. MouseMove does not interest most of the time, only click events.
    • correlation of an event leading to an ansyc call plus it's callback.
    1. ad filters
      The table views have a Custom Table Filter option accessible via the top left toolbar button. Here you can specify filters on time, content, size, duration, ...

      ad events
      The Timeline View allows you to visualize mouse moves, mouse clicks, key strokes, errors, ... individually. The toolbar allows you to turn on/off these events.
      Also - the PurePath View allows you to filter on JavaScript triggers like Mouse Moves, Clicks, KeyStrokes, ... -> this will then only show you those JavaScript traces that were triggered by these events
      Last but not least - you can double click a JavaScript trigger in the Summary Page -> this will open up the PurePath view automatically filtered with the clicked JavaScript trigger

      ad correlation
      The PurePath not only shows you where the async calls have been set-up, e.g.: Timers or XHR. The PurePath also includes the actual async methods that got executed when the timer was triggered or when the XHR response came back as part of the onreadystatechange event

  3. 1. AJAX Memory *and CPU* diagnostics (Browser, DOM)!!!  DOM and VML in IE7/IE8 are CPU and memory hogs. Show in timeline or otherwise correlate with user events and network requests/responses.

    2. Summary statistics grouped by URL for network requests (total, avg, median, stddev, median: bytes, bytes/sec, etc)

    3. Record and playback of user keyboard/mouse events like Selenium or integrated with it.

    1. Another vote for Memory diagnostics.

    2. Memory analysis is an absolute must-have on top of this already fantastic wealth of information. Our application suffers from crashes in IE (not FF or Webkit) after the memory footprint of IE becomes larger than 500MB (FF and Webkit never go over ~150MB with the exact same use-pattern).
      I would LOVE to be able to see what's eating this memory!

      I understand that all browsers, but especially IE, have trouble garbage-collecting DOM-elements when linked with (anonymous?) js-snippets. So some indication which events cause DOM-elements to disappear, but not garbage-collected would be great.

    3. I agree with John, memory diagnostics would be great.

      Anytime before the end of the week is fine.  (wink)

      Great product, woud be amazing with memory stat capture.

    4. AJAX Memory?? any progress? it is number 2 on the list, but posts stopped in 2010? We need a javascript /DOM heap dump! we need it mapped to the javascript create and reference creations with reference counters. Dynatrace has a great system/article for JVM heap dump analysis to find memory leaks. The industry needs a javascript/DOM solution for the browser, that is similar. Any Hope?

      Also any one know the memory limits of the browsers and how they scale with the machines memory? IE,FF..

      1. Hi John

        There has only been little progres on this as the browser vendors do not provide memory diagnostics interfaces similar to the JVM and CLR. We are in constant discussion with the browser vendors and hope that there will be something coming up that will make it easier.
        On the other hand we are working with some individuals that have already done research on browser memory diagnostics and hope to leverage that. We know that this is a big topic - but - due to the technical challenges and the resources we would need to implement its still only on the wish list and NOT YET in the product.

        Our Premium Edition provides a feature to automatically monitor process memory, thread, ... usage of the browser process. This is the first step.

        Keep these postings coming as this gives us additional arguments when talking with the browser vendors that we need those interfaces

        Andi

  4. From Olivier Percebois-Garve:
    "I would be nice if you would consider adding a "stop recording" button. I've been looking for it during a long time, plus I suspect it is also the reason why dynatrace is very slow to "wake up" after a while."

  5. Great program!  It has been quite helpful in helping to find bottlenecks in code.

    It is quite useful that it is possible to select rows in the Time Chart of the PurePaths screen and then copy them to the clipboard and then paste into a text editor (as XML).  However, when we do this, we only get the "Start" and "Duration" figures.  I'd like to also be able to get the breakdown of the "duration", into "Wait" "DNS" "Connect" "Server" "Transfer", as well as the "Response Size" in bytes.  I know that the "copy" is meant to be generic, encompassing all of the types of network activity, but it should be possible to do this.  Maybe as an additional column that contains activity-specific information?

    Thanks for the great program and I look forward to continue using it in the future.

    1. You can get these detailed values when you copy the content from the network view. The Copy feature copies the visible columns that you see in lists or trees. But you bring up a good point - for indidivual activity types we could add additional information that we show in the details dialog when copying the content to the clipboard.
      For now you can drill into the Network view but consider your request as noted for future improvements
      thanks for the great feedback

  6. It would be nice to be able to sort the Sessions by name or date/time. This would allow me to group my test cases together. It would also be nice the the 'duration' field was populated with something other than 0 on the 'summary' (right click on session). Thanks!

    1. Sorting by date/name is now supported in dynaTrace AJAX Edition 1.6

  7. It would be convenient to have an indication of the current level of zoom applied to a timeline.

    I often take screenshot of small portions of the timeline in order to document the effect of different versions of our code. Having a indication of the level of zoom would help me to use the same scale in every screenshot.

    1. right now - X-Axis contains the current timeframe. So - when you are zoomed in you can always see in which timeframe you are zoomed it. This should help in your case - but I agree - a better visualization would be helpful
      thanks for the input - i've forwarded this to our team

  8. Few things I would like to see:

    • Separate CSS rendering profiling. Time it took to scan CSS files and apply styles to the page. Number of selectors applied, total number of selectors, etc.
    • Support for automatic export of traces to a remote disk or versioning system.
    • Stop button (as mentioned above). It's inconvenient to close IE every time you are done with profiling.
    • Possibly JS API to automatically add markers.
    1. Thanks for the input - these are all great requests.
      I have good news for you on your 4th bullet point: there is already a JS API that allows you to set markers. Check out the following blog entry and scroll down to "Advanced Step - adding custom markers".

      1. Great. Didn't know about it. Thanks! One more request:
        I don't know if it's possible, but it would be nice to be able to mark the time when page started showing up on the screen in timeline. Not page_load event, but just as soon as some rendering started.

  9. Good to see Firefox support will be added in the next upcoming release.

    And it's good to see requests for Chrome to be supported. I would extend this and sugguest support for WebKit (so Chrome & Safari)

    But lastly, and probably most awkward to implement would be be Apple Mac support? I use a Mac for development at home and a PC at work. I know lots of PHP developers who work on Macs and would appreciated the AJAX edition being compatible (me included).

    1. thanks for that input - will add it to our list

      1. +1 for this feature. We are mac users and appreciate the mac client for dynatrace server, but wish the ajax edition would also be ported.

  10. X X

    1. Show the time labels at the top of timeline. When many hosts are involved in the page the labels are scrolled outside of the view. Alternatively make time labels visible regardless of scrolling.

    2. Needs more detail regarding the renedering activities (reference to specific HTML/css would be nice) to troubleshoot inefficient HTML layouts, etc.

    3. There are periods of high CPU consumption in the browser when it's not clear what is going on because theis no rendering activities, downloads or JavaScript. Need more detail regarding these "blank" areas.

    4. Allow the UI to show the downloads from the same host on multiple rows instead of the overlapping display on one row. I know you have the tooltips, but display on multiple lines is easier to visualize.

    1. great input. will add these to our internal list - thanks

  11. Hi

    another small suggestion, it would cool to be able to export the  "Contributor" and "Stack Element" Data to excel the same way we can for the "Activity" frame. (it is currently not possible to select multiple lines)

    1. thanks - added to our internal list

  12. Hi

    - I wish if I can compare the sessions and the pages, so I can easily identify the improvements on my application. 

    1. With 1.6 you can now multi select the list in the summary view. From there you can copy/paste the content over to e.g.: excel that allows you to compare different sessions.
      does this work for you?

      1. Thanks Andreas

        I have tried to copy the list and past it directly into excel,but the copied data was XML markup.
        I pasted it innto my text editor and save it as XML, open it with IE, then right click => Export to Excel => (thumbs up)

        Every thing is OK.

        (info) But advanced comparison could be useful if we want to go deep in the improvement sources.

        (info) Any way, Export as XML or Export to Excel could be useful  items in the context menu of the summary list

         Thanks a lot Andreas

  13. Hi

    I noticed something today in the purePaths view :
    The duration includes asynchroneous function (i.e setInterval or setTimeout).

    So if some code waits 1000ms and then get executed in 10ms, the purePaths reports 1010ms.

    Whilst it is true that it taken 1010ms for the function to complete, it is not 1010ms of "blocking" execution, but only 10ms. So at a first look such function appears to be have a big impact on performance, but in fact it is neglectible.

    So my wish is to have a display of the "really blocking execution duration" in the purePaths.

    1. Look at the JS column. This columns tells you the JavaScript executing time exluding the wait time

  14. +1 for the suggestion by Ilya: " it would be nice to be able to mark the time when page started showing up on the screen in timeline. Not page_load event, but just as soon as some rendering started"

    Also are you planning on supporting the export of performance data in the HAR format? http://groups.google.com/group/firebug-working-group/web/http-tracing---export-format

    1. we are looking into both things a) the requests Ilya suggest and b) supporting certain export formats
      thanks for letting us know what you guys out there need in your day2day job

  15. I haven't found a way to get dynaTrace Ajax Edition to indicate whether a file is compressed or not (gzip or deflate).  All downloaded files sizes on the Networks tab seem to show the uncompressed file size even if the file was compressed.  This makes it hard to determine whether or not compression is functioning as expected on the Web Servers or Load Balancer.  Check out the http packet sniffing tool Charles for a great implementation of this.  They even tell you what % compression was achieved.

    1. Hi Kristian
      Right now we are not able to capture all HTTP Headers and also do not get the information about compressed vs. uncompressed. We already have this in our list of enhancements. Right now I propose to use tools such as Charles to analyze http compression

  16. Hi Andreas

    a few points I have noticed :

    When the timeline is zoomed a lot, it is very hard to scroll : either the arrows become very slow or if the cursor is used, then it is too fast. A "hand" feature allowing to drag the timeline would be very convenient.

    Another point would be to add an option to make the text of the marks always visible. That would help taking screenshots with this information.

    Also the marks could get their timing in their current execution block.

    When exploring the execution block, it would be nice to see the marks appears as well.

    Olivier

    1. all great points to make the tool easier to use - adding it to our internal RFE list for the next versions

  17. Hi

    I have some more wishes
     (and may very well have more soon since I'm now our "dynatrace contact point" and I am gathering feedback).

    1. export of subparts of the purePath. 
    It would be great if we could do "Show selected  node as root" and then "export". It makes really sense for us, since we have very long timelines and are often interested in only a small part of it.

    2.I'd be interested in a "show most expensive native functions" feature. In fact when I explore the purePath, I often dive until I can find what is the native function that takes time. On some action we have hundreds of calls to getElementById. Dynatrace could have a feature tu underline this fast. It would be great if it could display on the timeline.

    that's it for now, wish you a great weekend
    Olivier

    1. Hi Olivier. To your point 2) the Hotspot view is perfect for this. Just open the hotspot view and identify the most expensive method (either in terms of execution count or exec time)

  18. One more for the road.

    Without to dig in the server-side activity, I would be interested in having more details on the network activity.
    HttpWatch provides a distinction between the "transfert" part and the "receive" part. We noticed that several factors can affect the "receive" part, for instance the size of the response or the cpu activity at that moment. I wished I could have some more details on that.

    -Olivier

  19. Hi,

    just a couple of thoughts.

    I have some pages which load things in background, after onready and onload, but don't display anything (ie: analytics tracking javascript). In this case I usually use "time to last render" as a Key Performance Indicator, do you think it's possible to add it to KPIs ?

    I don't know if it's traceable, but is it possible to add (in timeline) when the page is not interactive? When it's blocked by intensive javascript or by loading of external resources (inevitable document.writes as in advs).

    Thank you very much for your work.
    Fabio

    1. We can easily calculate the time of the last Drawing activity on a page - but this really only makes sense if your user is not triggering any rendering activity after the page is fully loaded.
      We would actually need to use the last rendering activity before the onunload event - which is triggered before you move to the next page. So - if you look at your timeline - would that always make sense for you? A KPI that returns the time of the last drawing activity on the page before the onunload event?

  20. I would like to see the ability to view the contents of AJAX requests. Currently, the tool captures the content of the AJAX response but not the content of the request.

  21. When do you plan to add the FireFox support? Apparently you have a great tool here but what I really need to use it is cross-browser support, at least for FF and IE.

    1. Hi Dominik

      Our engineers are already working on it. As you said - it is a great tool and the next step is to provide the same tool for multiple browsers.

      1. Thanks for your fast response, Andreas! Is there any rough ETA? Like - is it 8 weeks or rather a year until FF will be supported?

        1. I can't nail down a date yet but we keep you posted with our progress. 8 weeks is probably to soon for a releaseable version but it shouldnt take a year :-)

          1. alright - thanks a million!

  22. It would be fantastic to be able to see which DOM nodes are being affected by repaint or redrawing. So, if a CSS change happened at one level and it's causing a repaint at a higher level, it'd be great to be able to see this. 

    1. I agree with that. I'd like to find where a given redraw has been scheduled, and the opposite, i.e, where is executed a scheduled redraw.

      1. yes I agree - would be a great thing to know. Unfortunately we do not get this information from the current versions of IE that we support. We got it on our list but right now it is a technical limitation from the browser side

  23. Since I am working on a news website, I am looking more at initial load. One very important apsect of this, is the number of connections that the browser is able to open. To visualize this, it would be nice to be able to see on multiple line the network activity. Currently, downloads are displayed over eachothers, it makes it difficult to see the detail of each download. 

    1. have some good news about this. Our DevTeam and Test Center Edition provide this feature in the Timeline. Not only can you turn on to visualize individual network connections, you can also turn on individual Server-Side Worker Threads (in case you have dynaTrace running on your AppServer)

  24. Alternate timeline view?

    I've been using a few different tools to evaluate the performance of my web application.  I've been using dynatrace to delve into the nitty-gritty details of my application which is great because I can see every thing that is going on. 

    I've also been using a tool called HttpWatch professional (not free) that shows less information than dynatrace but it presents that information in a very clear and concise way.  It lets me see the relationship of request to actions.  It helps to highlight potential issues in a way that "pops."  I'd like to see a similar layout for dynatrace, maybe an alternate way of viewing the timeline?

    1. Hi Matthew
      Do you have a screenshot or a sketch on how this alternative view could look like?

    1. working with the MS IE Team on getting that version supported (smile)

  25. I use Linux a my primary O/S all day everyday.  I currently use the dT Client on OpenSuSE 11.3 and run the dT Server on SLES 11.1  Now that dT AJAX supports FireFox, when will Linux be supported? 

    1. we dont have any timeframe that we can share. right now we are working on creating support for IE9. Other browsers and platforms are on our list. May I ask: where do you run your automation tests? also on Linux? Or on windows?

      1. We use a combination of both.

  26. Please...memory diagnostics. Even if you start with something simple. Chrome has some support, but it looks like it can only take heap snapshots of relatively small heaps.

    Definitely something that my company would gladly pay for!

  27. D B

    Why doesn't the "Content-Encoding:gzip" show up in the Response Headers when receiving gzipped compressed data from the web server? Can it also show the compressed and uncompressed size?

  28. It would be nice in the Ajax edition to be able to specify the name of a page in the reports. We have sites where the URL is the same whether you are logged in or not, but the user experience and features on the page are different. At present, it is difficult to keep the results of the logged in users separate from the logged in users. If there was a field that we could type into (similar to the add Mark field), it would be nice to have the contents of the field used as a prefix to the name of the URL that is being tested in the reports.

    1. We have a feature in our commercial product that allows you to specify a "Timer Naem". There is a public entry that shows Timer Names in the combination with Selenium: How to include dynaTrace in your Selenium Tests. This post will show you what "Timers" look like

      1. So that method won't work with the Ajax Edition?

        1. correct. its not part of the free product

  29. Quick question - Is there an estimated time frame for Chrome support?

    Also is Safari on the roadmap for support?

    Thanks,
    Jake

    1. Hi Jake,

      we are considering to extend the range of supported browsers (and devices) for browser diagnostics by moving to a different technology. We are still in an early stage in that endeavor and can therefore not commit to any timeline.

      Best regards,

      Guido