Troubleshooting of performance problems is very often – if not almost always – viewed as a reactive activity. Frankly, I have often seen it done in such a reactive as a firefight; however effective troubleshooting should build upon a solid diagnostics process. If you handle troubleshooting as if firefighting rather than based on solid diagnosis, [...]
Read full post >>
Performance Almanac
dynaTrace CTO and Founder Bernd Greifeneder talking about the future of Testcenters. Will test centers as we know them fade away? What are the drivers for changes and how should test centers react to them?
Read full post >>
The dynaTrace Blog became a great tool for us to interact with you – our community – throughout 2009. The feedback we got on our posts has shown that the discussed topics on Application Performance Management, Architecture, Patterns and Practices, Virtualization, AJAX, Java, .NET, … are of value and great interest. Besides server-side related performance [...]
Read full post >>
Several years ago JavaScript was seen as a „playground“ due to compatibility problems with browsers and high maintenance costs. Under the term AJAX JavaScript made the breakthrough in the last years. One of the reasons is the availability of libraries and better support of the major browser platforms. Prototype, script.aculo.us and jQuery are under the [...]
Read full post >>
Ajax, Performance
When do we add logging?
In order to analyze problems, developers tend to add additional logging information to the source code. There are different logging frameworks available, e.g.: log4j, log4net, EnterpriseLibrary Logging, … which provide an easy and extensible way to create log files. Logging offers additional insight into what’s actually going on in in the application [...]
Read full post >>