<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Kommentare zu: Eating Our Own Dog Food: How dynaTrace does Continuous APM Internally in Development with dynaTrace TA Lead Stefan Frandl</title>
	<atom:link href="http://blog.dynatrace.com/2010/01/27/eating-our-own-dog-food-how-dynatrace-does-continuous-apm-internally-in-development-with-dynatrace-ta-lead-stefan-frandl/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dynatrace.com/2010/01/27/eating-our-own-dog-food-how-dynatrace-does-continuous-apm-internally-in-development-with-dynatrace-ta-lead-stefan-frandl/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 19:15:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>Von: h.e.</title>
		<link>http://blog.dynatrace.com/2010/01/27/eating-our-own-dog-food-how-dynatrace-does-continuous-apm-internally-in-development-with-dynatrace-ta-lead-stefan-frandl/comment-page-1/#comment-11660</link>
		<dc:creator>h.e.</dc:creator>
		<pubDate>Wed, 03 Feb 2010 13:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1412#comment-11660</guid>
		<description>Thank Share</description>
		<content:encoded><![CDATA[<p>Thank Share</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Bernd</title>
		<link>http://blog.dynatrace.com/2010/01/27/eating-our-own-dog-food-how-dynatrace-does-continuous-apm-internally-in-development-with-dynatrace-ta-lead-stefan-frandl/comment-page-1/#comment-11480</link>
		<dc:creator>Bernd</dc:creator>
		<pubDate>Sat, 30 Jan 2010 13:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1412#comment-11480</guid>
		<description>I&#039;d like to add that Stefan&#039;s team used the dynaTrace Development Edition, which has been optimized for continuous integration and agile development teams. dynaTrace Development Edition is part of the dynaTrace Continuous APM solution, which includes further the Test Center Edition and the Production Edition to enable lifecycle oriented performance management.

I have heard from many CTOs, CSAs and VP Devs that while they need to be more proactive, its too hard to enforce proactive use of profilers within development teams. Therefore we found that the only thing that works is automation of performance tests in CI environments with continuous feedback to the team and development management.

When asked &quot;where to start&quot; in CI, I found further that its very helpful to take service level goals from production and bring them back to engineering into CI. Thats what I then call performance engineering. If an applicatio is already in production, then another helpful approach is to e.g. use dynaTrace Production Edition to capture business transactions, prioritize them by business criticality and performance weaknesses and take the top 5 into CI for proactive performance management.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to add that Stefan&#8217;s team used the dynaTrace Development Edition, which has been optimized for continuous integration and agile development teams. dynaTrace Development Edition is part of the dynaTrace Continuous APM solution, which includes further the Test Center Edition and the Production Edition to enable lifecycle oriented performance management.</p>
<p>I have heard from many CTOs, CSAs and VP Devs that while they need to be more proactive, its too hard to enforce proactive use of profilers within development teams. Therefore we found that the only thing that works is automation of performance tests in CI environments with continuous feedback to the team and development management.</p>
<p>When asked &#8220;where to start&#8221; in CI, I found further that its very helpful to take service level goals from production and bring them back to engineering into CI. Thats what I then call performance engineering. If an applicatio is already in production, then another helpful approach is to e.g. use dynaTrace Production Edition to capture business transactions, prioritize them by business criticality and performance weaknesses and take the top 5 into CI for proactive performance management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Chris</title>
		<link>http://blog.dynatrace.com/2010/01/27/eating-our-own-dog-food-how-dynatrace-does-continuous-apm-internally-in-development-with-dynatrace-ta-lead-stefan-frandl/comment-page-1/#comment-11449</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 29 Jan 2010 15:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1412#comment-11449</guid>
		<description>Thanks Andi &amp; Stefan for this great blog.</description>
		<content:encoded><![CDATA[<p>Thanks Andi &amp; Stefan for this great blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Florian</title>
		<link>http://blog.dynatrace.com/2010/01/27/eating-our-own-dog-food-how-dynatrace-does-continuous-apm-internally-in-development-with-dynatrace-ta-lead-stefan-frandl/comment-page-1/#comment-11416</link>
		<dc:creator>Florian</dc:creator>
		<pubDate>Thu, 28 Jan 2010 13:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dynatrace.com/?p=1412#comment-11416</guid>
		<description>Kudos for this excellent article!</description>
		<content:encoded><![CDATA[<p>Kudos for this excellent article!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

