PurePerformance

Erik Landsness, Director Network Operations Center & SRE at Beachbody, talks us through his last 1.5 years in his role where he has been transforming the role and culture of the traditional NOC team from human-based Dashboard analytics to a Automated Self-Healing Zero-Dashboard Culture. While they haven’t yet reached that end state they have made big strides. Erik shares with us how to gradually transform into a modern operations team that automates things that humans shouldn’t do – such as staring at dashboards on walls 😊Erik is also presenting at Dynatrace PERFORM 2018. Make sure to check out his session to learn first hand! https://www.dynatrace.com/perform/speakers/

Are you still deploying machines manually? Do you have to login to machines to apply changes? Do you spend hours or even days to detect infrastructure issues messing with your test execution or even production? We have the answer for your pain: Listen to this podcast!Markus Heimbach leads the Infrastructure and Service team at Dynatrace and explains how they got rid of Snowflakes (not in the political sense), tackled the Configuration Drift issue, and how his team became a Service Organization powering the innovation at Dynatrace R&D. Get a glimpse of his talk track from his presentation at #devone.at - https://speakerdeck.com/markusheimbach/infrastructure-as-code As another teaser: you will hear about Test Automation of Infrastructure Code, leveraging Docker and Kubernetes (k8s) and how to use and leverage Immutable Infrastructure!

We typically hear about agile transformation being driven from development and eventually pushing it towards operations. But it doesn’t have to be that way as we hear from Nestor and Abeer who helped transform their operations team from Waterfall (Traditional Ops), to Partial Scrum (Intro to Agile) and then Kanban (more defined structures for Ops using Agile principles). Listen in and learn what the differences are between Agile in Dev and Agile in Ops, which metrics they use to measure the success and how they are now pushing towards a DevOps transformation from Ops towards Dev.If you want to chat live with Nestor and Abeer then take the chance and meet them at PERFORM 2018 ( http://perform.dynatrace.com ) where they give us more insights into their transformation

Most of us remember the DDOS attack last year executed through thousands of Security Camera IoT devices. This raised security questions around IoT but also helped the public to understand that IoT (Internet of Things) is a real thing.In this session, we learn from Harald Zeitlhofer ( https://twitter.com/HZeitlhofer ) why he rather likes to call this hot trend IoE (Internet of Everything), what the key use cases of IoE are and how proper monitoring of these devices might have been the key to detect the attack before it actually happened.To learn more about this exciting next big thing we suggest to start with Harald’s latest blog posts on his most favorite topic.

If you believe OpenStack and OpenShift are pretty much the same thing. you better listen to this episode with Martin Etmajer ( https://twitter.com/metmajer ). He explains what OpenShift is, how it differentiates from Cloud Foundry and other PaaS platforms, and which major contribution it can have to successful DevOps transformations.To put it in his words: OpenShift provides great user experience for developers to push their code changes automatically, packaged as containers, into different environments without having to worry about where and how these containers run or how they scale up & down. You should also check out his presentations from Red Hat Summit on Monitoring and Logging in OpenShift ( https://www.slideshare.net/martinetmajer ) as well as more material on http://www.dynatrace.com/openshift.

Project Jigsaw, G1 as default garbage collector, ahead-of-time compilation, Stack Walking API and many more changes that you should be aware of when upgrading to Java 9. Philipp Lengauer, whom we met at devone.at, gives us all the answers and technical deep dive into all these JVM changes. Especially for performance engineers an episode worth while listening to.If you want to learn more check out Philipps presentation at devone:https://youtu.be/Nsg_rhlf4_U?list=PLfi6VUNSzNYmUyeZ2BTM_WmZjgi0FOqRl

If you thought EC2 was the first service offered by Amazon Web Services and if you think 53 in “Route 53” is just a random number then you should listen to this 101 on AWS Podcast. This time we got to chat with Wayne Segar ( https://www.linkedin.com/in/wayne-segar-6222ba57/ ) who has been helping companies to move to new cloud technologies and services such as AWS. Wayne gave us a great overview of the key services in Compute, Database, Storage, Management, Development as well as how Monitoring works with AWS.If you want to make your first steps with AWS, such as deploying your first EC2 Instance or Application on Elastic Beanstalk, then feel free to follow our 101 AWS Monitoring Tutorial:https://github.com/Dynatrace/AWSMonitoringTutorials

Why would I move to .NET Core? If I move, can I just recompile my .NET code with the new .NET Core and run it on Linux? Or is there more to it? What is .NET Core at all and what does it provide as compared to ASP.NET Core? Can I still monitor my .NET Applications the same way as in the past or is there a new approach for tracing and monitoring? And is it true that all of this is now available on GitHub as Open Source project?Get answers to all these questions by listening to this episode where we got to talk with Christoph Neumueller @discostu105 ( https://twitter.com/discostu105 ) and Gergely Kalapos @gregkalapos ( https://twitter.com/gregkalapos ). Christoph and Gergely are two lead engineers for the Dynatrace .NET Agent technology. They are also code contributors to the .NET Open Source and other open source projects such as SuperDump ( https://github.com/Dynatrace/superdump ). Also check out their blogs ( https://www.dynatrace.com/blog/tag/net/ ) to learn more on .NET Core, ASP.NET Core and other .NET relevant performance topics. And, if you're a Dynatrace customer, make sure to up-vote the RFE to allow hot sensor placement for .net core. ( https://answers.dynatrace.com/spaces/151/product-feedback-and-enhancement-requests/idea/183988/hot-sensor-placement-for-net.html )Additional Links:TechEmpower Benchmark ( https://www.techempower.com/benchmarks/ )Blog about performance improvements as a result of community input ( https://blogs.msdn.microsoft.com/dotnet/2017/06/07/performance-improvements-in-net-core/ )Download and try out .Net Core ( http://dot.net )Dynatrace Free Trial ( https://www.dynatrace.com/trial/?vehicle_name=www.spreaker.com )

Visually Complete and Speed Index have been introduced to better measure real end user performance experience. Klaus Enzenhofer @kenzenhofer ( https://twitter.com/kenzenhofer ) gives us a detailed description of these metrics, how they are getting calculated, and which problem they solve. What we also learn in this 101 is why now we finally have these metrics available not just for synthetic monitoring but also for real user monitoring. This can be attributed to the advances in browser technologies as well as to some smart engineering. In our discussion we also cover other recent advances and use cases in Web Performance Optimization – such as the usage of performance markers.If you want to learn more check out the blogs from Google on Speed Index ( https://sites.google.com/a/webpagetest.org/docs/using-webpagetest/metrics/speed-index ) as well as the blog from Klaus on how Speed Index and Visually Complete made it into RUM offerings ( https://www.dynatrace.com/blog/visually-complete-speed-index-for-real-user-monitoring-rum/ ).

Spoiler Alert: Serverless doesn’t mean that we got rid of servers. We just don’t have to think about them anymore as we can focus on coding functions that get executed when triggered through certain events. Daniel Khan (@dkhan) tells us more about use cases of Serverless or as he likes to call it “Function as a Service” (FaaS). We also chat a lot about monitoring and the challenges of actually monitoring and debugging serverless code. It is still a young technology but constantly evolving.