<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Henrik Rexed on Medium]]></title>
        <description><![CDATA[Stories by Henrik Rexed on Medium]]></description>
        <link>https://medium.com/@rexed-henrik?source=rss-ee4368dc730f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*myv7muTDSD87B7kztEljyg.png</url>
            <title>Stories by Henrik Rexed on Medium</title>
            <link>https://medium.com/@rexed-henrik?source=rss-ee4368dc730f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:21:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rexed-henrik/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to collect metrics in a Kubernetes cluster]]></title>
            <link>https://medium.com/is-it-observable/how-to-collect-metrics-in-a-kubernetes-cluster-9ad4a69aafb0?source=rss-ee4368dc730f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ad4a69aafb0</guid>
            <category><![CDATA[kube-state-metrics]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[grafana]]></category>
            <category><![CDATA[prometheus]]></category>
            <category><![CDATA[node-exporter]]></category>
            <dc:creator><![CDATA[Henrik Rexed]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 12:01:50 GMT</pubDate>
            <atom:updated>2021-09-02T15:12:02.407Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post is part of a Kubernetes series that will help you initiate Observability within your Kubernetes cluster.</p><p>This blog post also summarizes the content presented on the “Is it observable” episode :<a href="https://youtu.be/JQrk6HwlN78"> how to collect metrics in k8S</a> briefly explaining :</p><ul><li>The core components of Kubernetes</li><li>The architecture of Prometheus</li><li>The default Prometheus exporter that will help you collect relevant metric on k8S</li></ul><p><a href="https://www.youtube.com/watch?v=JQrk6HwlN78">How to collect metrics in K8s — YouTube</a></p><p>If you are working in the cloud-native space, there is a big chance that you are eating k8S for breakfast, lunch and dinner.</p><p>A few years ago, the entire market was looking at the new kid on the block called Kubernetes…but at that time nobody was betting on the current usage and popularity of the technology.</p><p>Basically, Kubernetes has become the standard technology for Cloud-native architecture.</p><p>In reality, it’s an orchestration tool that manages our workload for us by starting, updating and deleting pods.</p><p>But how is Kubernetes able to do magic tricks on our environment?</p><p>Well, to answer this question we need to look at the engine:</p><h3>The core components of Kubernetes</h3><p>Kubernetes runs on nodes. A node is technically a server: physical or virtual.</p><p>Kubernetes has 2 distinct type of nodes :</p><ul><li>Master node</li><li>Worker node</li></ul><p>A master node is the central component managing the entire cluster. If you are using a Kubernetes cluster managed by one of the cloud providers, you probably won’t have access to the master node.</p><p>On the other hand, the worker nodes are the layer that will be used to deploy our pod for our workload.</p><p>Let’s have a look at the core that we find in those 2 types of nodes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*MAbl6c28cKpnxgyTFHjgfg.png" /><figcaption>The different type of Kubernetes nodes</figcaption></figure><h4>Master node:</h4><ul><li>The <strong>scheduler </strong>is the component that is responsible to select the node that will be in charge of hosting our workload. The scheduler will select the node based on resource utilization, taints, quotas, …etc.</li><li>The <strong>Control manager</strong> is responsible for detecting the state changes of our workload. If a pod crashes, it will try to reschedule the pod to make sure we always have the desired number of pods running in our cluster. The control manager doesn’t schedule pods by itself, it will reach out to the scheduler to delegate that task</li><li><strong>Etcd </strong>is a key value pair storage that stores the status of our various Kubernetes components</li><li>The <strong>APi server</strong> is very important layer because it allows us to deploy our workload utilizing the Http request or kubectl ( that is interacting with the api)</li></ul><h4>Worker node</h4><ul><li><strong>Container runtime</strong> : since Kubernetes orchestrates containers within your cluster, the node needs to have a container runtime . Most of us use the docker runtime.</li><li><strong>Kubelet </strong>: Once the scheduler has identified the node to run our workload, kubelet is in charge of allocating resources and running our pods. It is also responsible to validate that our pods are ready and healthy. Kubelet will report any state changes of our pod to the control manager.</li><li><strong>kube-proxy </strong>is the component in charge of the communication between services.</li></ul><p>All those components have specific tasks to make sure that we always have the desired number of pods in our environment. If we want to make sure that Kubernetes is running under good conditions, we will need to make sure to collect information related to:</p><ul><li>The health of the nodes</li><li>The status of the workload</li></ul><p>To collect metrics related to our Kubernetes cluster, we will naturally take advantage of Prometheus that has become standard for this.</p><p>So, let’s have a look at the architecture of Prometheus.</p><h3>Prometheus Operator</h3><p>Prometheus can be installed in various ways in your Kubernetes cluster.</p><p>But keep in mind that Prometheus has several components that will make your manual deployment much more complex:</p><h4>The Prometheus server that is based on 3 components:</h4><ul><li>The retrieval component in charge of collecting metrics from the various Prometheus exporter</li><li>A storage that stores the metrics collected in a time series database.</li><li>An http server that provides a simple UI to build our PromQL and an API endpoint that is used by Grafana to display the metrics</li></ul><h4>The Alert manager in charge of raising alerts based on rules defined in Prometheus.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*LwIF-nAmyEEaxaIp3CRAMw.png" /><figcaption>Prometheus Architecture</figcaption></figure><p>Prometheus core components will only provide the feature to :</p><ul><li>Collect metrics</li><li>Store metrics</li><li>Raise alerts</li></ul><p>How can we expose metrics to Prometheus?</p><p>Prometheus needs to be configured by defining the various endpoints having metrics ( in a Prometheus format).</p><p>The metrics are produced by external solutions exposing data in the Prometheus format. Those solutions are named exporters.</p><p>The popularity of Prometheus is mainly related to the large number of exporters.</p><p>Today you can find exporters for many type of solutions :</p><ul><li>Database</li><li>Hardware</li><li>Messaging</li><li>Storage</li><li>Others ( CICD solutions).</li></ul><p>Prometheus also provide s<a href="https://prometheus.io/docs/instrumenting/clientlibs/">everal clients in various language</a> that allow you to expose custom metrics in a Prometheus format.</p><p>Deploying the the Prometheus operator with the help of the <a href="https://github.com/helm/charts/tree/master/stable/prometheus">helm chart </a>, will also add:</p><h4>Grafana</h4><h4>Several Prometheus exporters:</h4><ul><li>Kube-state metrics</li><li>Node exporter</li><li>Cadvisor</li></ul><p>The other advantage of the Helm chart is that you will have all the various components automatically configured. You only need to focus on:</p><ul><li>Exposing Grafana out of your cluster (by using ingress or a service mesh like Istio)</li><li>Building or using an existing dashboard in Grafana</li></ul><p>If you don’t reuse existing dashboards created by the community, I recommend having a look at :</p><ul><li><a href="https://grafana.com/grafana/dashboards/11074">Node exporter dashboard</a></li><li><a href="https://grafana.com/grafana/dashboards/13105">Kubestate metrics dashboard</a></li></ul><p>Let’s have a look at the type of metrics that you will be able to collect with the default exporters:</p><h3>Default exporters</h3><h4>Kube state metrics will report metrics related to workload scheduling:</h4><ul><li>node status, node capacity (CPU and memory)</li><li>replica-set compliance (desired/available/unavailable/updated status of replicas per deployment)</li><li>pod status (waiting, running, ready, etc)</li><li>resource requests and limits.</li><li>Job &amp; Cronjob Status</li></ul><p>With the help of kube state metrics we would be able to create a Promql that will report :</p><ul><li>The ratio of a pod in a running state</li></ul><blockquote>Sum by (node) (kube_pod_status_phase:{phase =”Running” }) /sum by ( namespace) (kube_pod_status_phase) *(100)</blockquote><ul><li>The ratio of pods having a cpu limit defined</li></ul><blockquote>Count by (namespace) (kube_pod_container_resource_limits: {ressource=”cpu”}) /sum by ( namespace) (kube_pod_status_phase:{phase =”Running” }) *(100)</blockquote><h4>Node exporter</h4><p>The Node exporter will be focused on hardware, Operating system metrics of our nodes.</p><p>You will easily be able to build a Promql Based on the node exporter metrics to report :</p><ul><li>the memory usage in % of our node :</li></ul><blockquote>(sum by (node) (node_memory_MemTotal_bytes — node_memory_MemAvailable_bytes) / sum by (node ) (node_memory_MemTotal_bytes))*100&quot;</blockquote><ul><li>CPU ioWait</li></ul><blockquote>avg(rate(node_cpu_seconds_total{mode=\”iowait\”}[$interval])) * 100</blockquote><h3>Conclusion</h3><p>With the help of the steps described in the Is It Observable <a href="https://www.youtube.com/watch?v=JQrk6HwlN78">episode</a> , you will be able to install Prometheus and build you first dashboard.</p><p>From the moment you are working with Kubernetes, you will be able to take advantage of all the default exporters and dashboards built by our community.</p><p>Metrics is only one angle to properly observe your Kubernetes cluster.</p><p>On the next episode we will cover how to ingest logs and how to consume Kubernetes events</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ad4a69aafb0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/is-it-observable/how-to-collect-metrics-in-a-kubernetes-cluster-9ad4a69aafb0">How to collect metrics in a Kubernetes cluster</a> was originally published in <a href="https://medium.com/is-it-observable">Is it observable?</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Prometheus and where does it fail for enterprises?]]></title>
            <link>https://rexed-henrik.medium.com/what-is-prometheus-and-where-does-it-fail-for-enterprises-5a3219336599?source=rss-ee4368dc730f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a3219336599</guid>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[prometheus-operator]]></category>
            <category><![CDATA[prometheus]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Henrik Rexed]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 12:09:19 GMT</pubDate>
            <atom:updated>2021-06-29T12:09:19.064Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Prometheus and 4 challenges for enterprise adoption!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UpN5YiHMTvQO1S1HVnEh9g.png" /></figure><h3>Prometheus has become a foundation for our cloud native environment.</h3><p>It has become our flying cockpit when starting our journey in the word of Kubernetes.</p><p>But there are few challenges that we need to consider to avoid bad experiences in the Kubernetes world.</p><p>This blog post will explain to you how Prometheus works and why I think these limitations are challenges when leveraging Prometheus in enterprise environments:</p><ul><li>Security: Not secure by default</li><li>Access control: Everyone can see all data by default</li><li>Scalability: Only vertical, not horizontal scaling</li><li>Global visibility: Requires extra components</li></ul><p>Before going into more detail, let’s have a short recap on how Prometheus works:</p><h3>How Prometheus works</h3><p>Prometheus relies on 2 services:</p><p>1. The Prometheus server having:</p><ul><li>A retrieval component in charge of collecting metrics from the various exporters (a solution exposing metrics in a Prometheus format is called an exporter)</li><li>A storage component that will store the metrics collected in a timeseries database</li><li>An Http server that will provide a UI to build our PromQL and API that will be used by Grafana to display the metrics in a dashboard.</li></ul><p>2. The Alert Manager: The alert manager will raise alerts based on the rules defined in Prometheus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozfZgpYdq-OrijIQWk9inA.png" /><figcaption><em>Architecture of Prometheus in K8S</em></figcaption></figure><p>Most Prometheus users are deploying it with <a href="https://github.com/helm/charts/tree/master/stable/prometheus">the help of a Helm Chart</a> that will automatically deploy the following components in your Kubernetes cluster:</p><ol><li>The Prometheus Operator (the Prometheus server)</li><li>The AlertManager</li><li>Several exporters:</li></ol><ul><li>Kube State metrics</li><li>Node exporter</li><li>Cadvisor</li></ul><p>4. Grafana</p><p>Those standard exporters provide the level of detail required to measure the health of our Kubernetes cluster.</p><p>On the one hand, Kube State metrics will report all metrics related to:</p><ul><li>node status, node capacity (CPU and memory)</li><li>replica-set compliance (desired/available/unavailable/updated status of replicas per deployment)</li><li>pod status (waiting, running, ready, etc)</li><li>the resource requests and limits.</li><li>Job &amp; Cronjob Status</li></ul><p>While, on the other hand, the node exporter will report hardware and OS metrics exposed on each node of our cluster.</p><p>So, if you are focused on reporting the health of you cluster, then the node exporter and kube state metrics will report all the desired indicators.</p><p>Prometheus has all the expected features to observe any of your cloud native technology:</p><ol><li>A large number of exporters built by the community and vendors allowing us to collect metrics on</li></ol><ul><li>Hardware ( Netgear, Windows, IBM Z, Etc.)</li><li>Database (Mysql, CouchDb, Oracle, etc.)</li><li>Messaging (MQ, Kafka, MQTT, etc.)</li><li>Storage (NetApp, Hadoop, Tivoli, etc.)</li><li>Others (Gitlab, Jenkins, etc.)</li></ul><p>2. An SDK allowing us to expose our custom metrics in a Prometheus format</p><p>3. Automation. All the configuration of Prometheus and Grafana could be done automatically by:</p><ul><li>Modifying the right configuration files:</li></ul><p>i. Prometheus.yaml to add new scraping endpoints (exporters)</p><p>ii. Alertmanager.yaml to define new alerts in Prometheus</p><ul><li>Build graphs as code using the JSON format of Grafana.</li></ul><p>So, you can easily include the configuration of your dashboard, alerts, and deployment of your new exporters in your continuous delivering processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6lFB3dG2qJH4UBZK50sZQ.png" /></figure><p>The Prometheus Operator also introduces additional resources in Kubernetes to make your scraping and alerting configuration much easier:</p><ul><li>Kubernetes</li><li>ServiceMonitor</li><li>Alertmanager</li></ul><p>The ServiceMonitor will map all the services that expose Prometheus metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2nNxsg3iFeu7Rc2WChkiA.png" /></figure><p>The ServiceMonitor has a label selector to select services and the information required to scrape the metrics from the service:</p><ul><li>Port</li><li>Interval</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pZQYXp0fUk4yc9y7HzQmpQ.png" /></figure><p>But “with great power comes great responsibility.”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FMCZ39lz83o5lC%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FMCZ39lz83o5lC%2Fsource.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FMCZ39lz83o5lC%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="232" frameborder="0" scrolling="no"><a href="https://medium.com/media/b6101fd1ce443641eba3b9b4f7355a67/href">https://medium.com/media/b6101fd1ce443641eba3b9b4f7355a67/href</a></iframe><p>Ok I can take it …. but what type of responsibilities we are talking about?</p><p>Well, Prometheus has few limitations relevant for enterprises. This means the owner of Prometheus has the responsibility to think about how to properly do these things when introducing Prometheus in an organization:</p><ul><li>Security: Not secure by default</li><li>Access control: Everyone can see all data by default</li><li>Scalability: Only vertical, not horizontal scaling</li><li>Global visibility: Requires extra components</li></ul><h3>Prometheus Limitations</h3><p>Let’s briefly look at those limitations one by one:</p><h3>Security: Not secure by default</h3><p>Currently Prometheus doesn’t have any native support for:</p><ul><li>TLS</li><li>Authentication mechanism</li></ul><p>In the digital transformation space, we are all aware that data can be very sensitive. Most organizations have very strict rules when it comes to security.</p><p>The current workaround to implement security in Prometheus is to delegate the SSL handshake and the <a href="https://prometheus.io/docs/guides/basic-auth/">authentication to solutions like Ngnix</a>.</p><h3>Access Control: Everyone can see all data by default</h3><p>The Prometheus operator will collect metrics from all the exporters that has been deployed and configured within your cluster.</p><p>This means mean that anyone can see your data from the Prometheus UI.</p><p>If you want to limit the access to certain metrics, you handle it by applying filters in your Grafana dashboards.</p><p>But there are no features to handle the access to your metrics based on privileges.</p><h3>Scalability: Only vertical not horizontal scaling</h3><p>Prometheus is a great solution, but it has not been designed to scale.</p><p>Once deployed there is big chance that:</p><ol><li>Your organization starts to utilize many exporters to report:</li></ol><ul><li>Health metrics</li><li>Efficiency of you CI/CD process</li><li>Release management data</li><li>Ops metrics to keep track on your operations tasks (I.e., backup)</li></ul><p>2. Your Developers understand the value of adding custom metrics with business information and technical details on the behavior of their application.</p><p>While your organization is finalizing its digital transformation, the number of services in Kubernetes will increase and the metrics collected by Prometheus will rise.</p><p>“Diseases” in Prometheus can be detected by observing issues when refreshing your Grafana dashboard. The memory usage of Prometheus is directly related to the number of time series data stored in Prometheus.</p><p>Keep in mind that 1 million metrics will consume approximately 100 GB of RAM. So, if you don’t pay attention, Prometheus could eat up most of the resources of your Kubernetes cluster.</p><p>The biggest limitation is that Prometheus is not designed to scale horizontally: That means that you cannot add several Prometheus servers to load balance the workload. Prometheus is only able to scale vertically: you need to add more resources to have a bigger Prometheus server.</p><h3>Global visibility: Requires extra components</h3><p>To avoid the technical limitations of Prometheus, we can clearly use the strategy of having several small Kubernetes clusters rather than a few huge clusters to handle our application workload.</p><p>If you are handling several clusters, that would mean having several Prometheus servers and Grafana to manage.</p><p>How can we guarantee that our project owners and operators can see the data from various clusters?</p><p>Well, the short answer is to create one big Grafana server that will be connected to all your Prometheus servers.</p><p>This allows us to provide visibility to our team members, but it also adds extra complexity in the maintenance of our Prometheus architecture.</p><h3>Solutions</h3><p>So, how can we resolve all these constraints without adding extra tasks on the shoulders of our Kubernetes Operators?</p><p>There are several solutions that make Prometheus Stronger, like <a href="https://thanos.io/">Thanos</a>, that will resolve:</p><ul><li>Scalability</li><li>Security</li><li>…and more.</li></ul><p>But there is another challenge that we all want to resolve when we are implementing Observability in our environments: attaching our metrics, logs, traces to a context.<br> The latest version of the Dynatrace k8s operator has the ability to ingest Prometheus metrics directly from the Prometheus exporters.</p><p>The Dynatrace Prometheus OpenMetric ingest has several advantages:</p><p>- Automatically collect metrics exposed by your Prometheus operator</p><p>- Reduce the workload on your Prometheus server</p><p>- Secure the data collected by Dynatrace</p><p>- Attach the metrics collect to a context</p><p>- and more.</p><p>And it doesn’t change the process of your K8s operator team.</p><p>If you want to learn more on how to configure the Dynatrace Prometheus OpenMetric ingest, watch the latest performance clinic on <a href="https://www.youtube.com/watch?v=j-Zc_ck-Orc&amp;t=3068s">K8S monitoring at Scale with Prometheus and Dynatrace.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a3219336599" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I decided to join Dynatrace, the leading company that is continuously innovating]]></title>
            <link>https://medium.com/dynatrace-engineering/why-i-decided-to-join-dynatrace-the-leading-company-that-is-continuously-innovating-e6d97c08624e?source=rss-ee4368dc730f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6d97c08624e</guid>
            <category><![CDATA[change]]></category>
            <category><![CDATA[dynatrace]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Henrik Rexed]]></dc:creator>
            <pubDate>Fri, 30 Apr 2021 08:52:07 GMT</pubDate>
            <atom:updated>2021-06-28T12:57:00.832Z</atom:updated>
            <content:encoded><![CDATA[<p>After 11 years of having fun working at Neotys, the software vendor providing the load testing solution Neoload, I have decided to leave this company to embark on a new adventure at Dynatrace.</p><p>“Why did you decide to make this move?” You may ask. “Especially when you had a brand, an image, a reputation within the Neotys Community?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vOy4cfefGuvp3Mco3UzJng.jpeg" /></figure><p>Well, I must admit that it wasn’t an easy decision to make.</p><p>My decision-making process involved spending a lot of time evaluating all the positive and negative points of leaving a company I was fond of to join a company like Dynatrace.</p><p>After a lot of reflection, I came to the conclusion that the most important points that helped me in making this decision were:</p><p>- Being inspired by smart people</p><p>- Always being on the forefront of innovation</p><p>- Trusting and being proud of the product</p><p>So, let’s cover all those points one at a time:</p><h3>1. Being inspired by smart people</h3><p>Several years ago, I had the chance to attend my first Dynatrace partner event in Faro, Portugal.</p><p>During this event, Bernd Greifeneder (CTO of Dynatrace) introduced the new platform Ruxit and the future of Dynatrace. He also had a session explaining how <a href="https://info.dynatrace.com/global_all_wp_game_changing_zero_to_autonomous_cloud_management_13255_registration.html">Dynatrace had successfully implemented DevOps</a></p><p>I was so impressed by the quality of the content, the way of bringing the audience into his stories. I told myself: wow, Dynatrace’s CTO is clearly a visionary.</p><p>I thought that all Dynatracers were lucky to collaborate with him. Because he will breathe innovation in the company, and continuously rethink and redesign the platform to be able to answers the market’s demands.</p><p>Like most Dynatrace users, I also had the chance to be part of the <a href="https://perform.dynatrace.com/">annual physical conference Perform</a> , that is presented and moderated by Dave Andersson. Every year, Dave always found a funny and crazy way to come on stage and to turn this conference into one of the first-class tech conferences of the world.</p><p>My experience at Perform had clearly established Dynatrace has a one of most creative companies in the tech industry in my mind.</p><p>And being a geek, of course, I’m looking for innovation …. But a culture of having fun is also important to me.</p><p>Lastly, I followed all the work of Andreas Grabner. I have always been impressed by the quality of his blogs, presentations. He was basically everywhere! One Day in a US conference, the next day in Australia.</p><p>When I became a technical evangelist, I clearly wanted to deliver as good content as Andreas. I always asked myself: how is he able to deliver so much?</p><p>Over the years I met Andi in person and he became a friend. Now we are also colleagues.</p><p>In our industry, we all want to work with leaders, and Dynatrace is clearly the good place to find the right mentor for you.</p><h3><strong>2. Being at the forefront of innovation</strong></h3><p>The tech industry moves fast. There are new solutions, frameworks, protocols, architecture concepts appearing almost every week. Following innovation can be a challenge, but it is especially challenging to identify which of the new technologies will be adopted and utilized by the market.</p><p>Since I was a kid, I have always loved to explore new things. Over the years, I started seeing technology as a Lego block. For those who know me …You already know that I have a lot of fun building things with Lego blocks 😉.</p><p>History has also always been an area of interest for me because it helps you understand why things are currently working in certain way. History allows you to understand the problems we are currently facing and why most decisions are made.</p><p>But, when it comes to technology, although I like to understand the background on how things have changed over the years, the reason of a technical limitation…etc., I clearly don’t want to work on technologies that are deprecated.</p><p>For me, Dynatrace is the place where I am able to:</p><ul><li>Work with the technology of tomorrow.</li><li>Play with and share my buildings blocks with our community.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ts8HJmIMmRoJNMtx5UARWA.jpeg" /></figure><p>To stay the leader of the Observability market, Dynatrace needs to invest significantly in researching all the latest technology in order to provide a support to collect data and provide value. I would recommend all the engineers addicted to innovation to join the DynAdventure</p><h3>3. Proud of the solution</h3><p>In 2005 I was in charge of the Performance Center of Excellence at one of the biggest European insurance companies. We were using at that time the Mercury/HP suite including the legacy Loadrunner, performance Center, SiteScope and HP Diagnostics.</p><p>Every time we were using HP Diagnostics for our tests, we had to deal with a lot of configuration to properly instrument the application. And we were having lots of challenges due to the consumption of HP diagnostics agents. So, we naturally explored new solutions and …we came across Dynatrace. We were impressed by the capacity of the solution compared to our experience with HP Diagnostics. From that moment on, I started to follow all the news from Dynatrace: Their growth, their new features, their blogs …. etc.</p><p>In my previous position, I had to work with technology partners to identify Integrations use cases between NeoLoad and other solutions of the market. With my role, I had the chance to explore and dig in many platforms of the market. I had also the opportunity to build the integration with Dynatrace, NewRelic, Appdynamics, Splunk followed the work with Instana…etc</p><p>Dynatrace was clearly the platform that was bringing the most value to the user. It was basically magic to run a test and let Dynatrace Davis AI point out the bottleneck of the application — I was impressed.</p><p>You should have seen my face the first time I saw problems identified by Dynatrace!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl3q2QdPu0G9NEgZJ6%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl3q2QdPu0G9NEgZJ6%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl3q2QdPu0G9NEgZJ6%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="289" frameborder="0" scrolling="no"><a href="https://medium.com/media/8d5e259f4b1401a618aab52f8a93ccbd/href">https://medium.com/media/8d5e259f4b1401a618aab52f8a93ccbd/href</a></iframe><p>Dynatrace had the technology and the API to make it work smoothly and successfully. OMG I was so excited to see the results!</p><p>Even before joining Dynatrace I was clearly a fan of the technical capacity of the product. And now I have the opportunity to contribute, by drawing more fans to this platform! (As soon as I finish my onboarding journey 😉).</p><p>Having worked as a Performance engineer for more than 15 years …. You could clearly be asking yourself what my role within the leader of the Observability market would be.</p><p>Well…as mentioned, I was seeking for innovation and if we look around us there is one technology heavily used by any company embarking on a digital transformation journey: Kubernetes.</p><p>So I will be the Cloud Native Advocate for Dynatrace focusing on any technology running in a Kubernetes Cluster and I will also collaborate closely with our strategic partner: Google.</p><p>In order to help practitioners, I will soon start creating video content that will help our community to instrument, collect, observe a given framework, platform or technology, and eventually blog posts for our <a href="https://engineering.dynatrace.com/blog/">Dynatrace Engineering blog</a>.</p><p>As my first step in the cloud native world, I presented with Andreas Grabner a Performance Clinic on 9th of June 2021. Watch it here: <a href="https://www.youtube.com/watch?v=j-Zc_ck-Orc">K8s monitoring at Scale with Prometheus and Dynatrace</a></p><p>Stay tuned for more stories coming from me in the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6d97c08624e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dynatrace-engineering/why-i-decided-to-join-dynatrace-the-leading-company-that-is-continuously-innovating-e6d97c08624e">Why I decided to join Dynatrace, the leading company that is continuously innovating</a> was originally published in <a href="https://medium.com/dynatrace-engineering">Dynatrace Research and Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>