 Hello, I'm Stefan Grübler. I'm a solution engineer working from Germany, Frankfurt. And I'm going to introduce you to a component, which I consider a hidden gem in our current product, Investigate, which exists there for a long time, but was only available on the Windows console. And now it comes into the TrueSight console. So this provides you additional capabilities, additional value also, looking at the agent data. So let me introduce you to some of the basics regarding what are the requirements, what are the metrics, where do you find the documentation, and how do you work basically in the TrueSight console before I hand over to Karen showing you also a study. Investigate is the component that works with agent-based data collection. So the agent collects many metrics, not just capacity and performance metrics, but also about the configuration. Normally, this data is analyzed and brought into the data warehouse, and you consume it through views and in a workspace, through great reports. But this data is also available on the agent, in a history, and also in a file structure that we call UDR data. The ultimate requirement is, if you want to show the capability to a customer to have the capacity agent installed, and ideally with the history data collection enabled. So in the screenshot on the left side, you see one of the screens in the installer process that allows you to enable the collection of historical data. And this will give you the near real-time capabilities also coming now in the TrueSight console, rather than waiting for a day or two before data comes in. So this will also allow you to see really quickly what the agent collects after you install it. On the right-hand side, you see that at least one gateway server needs to be installed, because this is the proxy that calls the individual agents and streams the data to the TrueSight console. The default retention time in the history data repository is defined in three stages. For the first hour, we provide data and history in 10 seconds granularity. After that, this data is summarized into five minutes intervals, and it is kept in history for eight hours. And the second summarization level is taking data of these five minutes intervals, create 15 minutes interval data for 40 hours. So you can have a history of 49 hours data taken directly from the agent streamed to the TrueSight console. And this is very valuable if you just install the agent would like to see quickly data that came in the last few hours, or if you come in the morning and you would like to see something that happened overnight rather than waiting for the next day before data usually is updated in the data warehouse. In order to work with the investigate, you need to have either operator role assigned or planner role, because the activity investigate section, either view or edit, belongs to operator and planner. Let's talk about metrics. The term of the metric regarding the agent is different from what we understand as a metric in the data warehouse. It gets translated. There is some calculation before it's moved to the data warehouse. The metrics are the raw data collected by and organized by metric groups, primarily for two different platforms, UNIX or Linux and Windows. So if you drill down to a UNIX or Linux system, you see metric groups with different naming than if you drill down to a Windows system. The Universal Data Repository, or UDR for short, organizes these metrics in folders that are named by these metric groups. And you see all this in the documentation by individual metric groups that you can drill down there in the documentation. Once you have added the gateway server in the TrueSight console, you can see two types of systems. Either you created a manager run and you configure the ETL which publishes the data warehouses with new data. Or you have systems not included in an ETL, but you are able to look at both with the investigate. The first managed systems, as we call it, are available. This data is also available in the data repository on the gateway server. Or they are categorized as uncataloged. So for those systems, the gateway server will talk to the agent and stream data directly from the agent, rather than looking at the UDR data. When we turn to the TrueSight console, to the TrueSight UI and presentation server, you basically find a study organized in a way like it is shown in a screenshot. And a study saves the definition of systems, the interval, the metric groups and filters you define, and also the format, whether you define it as a table or as a chart. But we will see this better in the demo that follows this presentation. So today, investigate is only available on Windows. Less people found this hidden gem and never used it. Now with investigate being able in the TrueSight UI, it really provides you more data and better granularity that you will find in the data warehouse, which also helps you with performance analysis. And sometimes we are faced with competitors really providing this capability, having both historical and real-time data in a single UI. So this positions us better, even without TrueSight operations for just the pure capacity and performance and analysis, against some of the competitors who does both. Let's move on to the life environment. Let's have a quick look at the documentation. I said that in the documentation you will find the metric groups and metrics organized by platforms. So when you do drill downs, you're not sure what the individual metric means. Then you can navigate in the documentation. And if you would like to see system statistics, you see all the metric definitions here. This is really the raw data that is collected every day. And it's a much richer data set that you will find in the data warehouse. In the TrueSight administration section, in the TrueSight console, in the administration section, I mentioned the prerequisite is to have Gateway servers added. Once you click on one of the existing Gateway servers, you can see the list of agents that are available, where UDR data is available. And these systems are part of the daily management run. You're able to edit Uncatalog systems here and provide this one system per line or IP address per line. Then the data is streamed directly from those systems even if you have it included in an ETL run. In the TrueSight UI, you will find Investigate on the capacity. From here, you have the opportunity to look at predefined study groups, groups that are defined by other members, by other users. Or you can create your own Investigate study. And when creating a study, you have the choice between the data that's available on the Gateway. These are the systems. And you see that I'm filtered here. Or the Uncatalog systems. These are the systems where only real-time data is available. When you click on one of the entries, you can then select a metric group, press Apply, and real-time data is streamed through the Investigate UI. In this UI, and I don't want to explain too much that Karen is going to cover in the next presentation. But basically, you have the opportunity to save this study here. You can also let this data be actualized in every 10 seconds. So when we enable the Auto Refresh here, just look at the timestamp. It should be updated in a couple of seconds. You notice that every 10 seconds, this table will be updated. So you're able to really show a shot with updated data later on. But Karen is going to cover this when we're going to study.