Video: IBM® OMEGAMON® Virtual Technical Summit, Special Edition | Duration: 3600s | Summary: IBM® OMEGAMON® Virtual Technical Summit, Special Edition

Transcript for "IBM® OMEGAMON® Virtual Technical Summit, Special Edition": Hello, everyone. Thank you for being here today for this IBM OmegaOne Virtual Technical Summit. I am Anna Murray, product management director for Rocket Software. You have not met me before because Steve Solomon was a previous product manager, and he has retired. So here I am taking over working with Ash Mahay and Dan Wigand at IBM. We're excited to be here with you. So for over thirty years, Rocket Software has been a strategic partner for to IBM, collaborating closely on driving innovation and positive business outcomes for our joint IBM z customers. Today, we are doing a technical update presented by product experts from our lab straight to you, our customers. To help you leverage our latest development and capture your inputs, we intend to bring this community of OmegaOne users together on a regular basis. If you're going to be at share if you're going to be at the share conference in Cleveland, I'd love to meet you. So please let us know you're going, and we'd be happy to get together. There's going to be an email sent out afterwards that will include the slides and recording of this session. Okay. So a little bit of housekeeping before we get going. Please use the q and a window in the right hand panel for questions. I see a bunch of you are already chatting. There's a q and a right next to that in another tab. We have a team of OmegaMon experts on standby to address all of your questions. The other thing to know is that we are running a few polls today. So when those polls pop up, they will also be showing up in that chat and q and a area. See, you will see a poll tab show up. Click on that and start participating. With that, we will get going. I think I already did my welcoming remarks. Here we go. Alright. Quick agenda. We're gonna cover an introduction to the OmegaMon communities, then we're gonna talk about the new IBM C OmegaMon UI with Grafana, then an OmegaMon family update with a focus on AI integration and reducing CPU consumption, and then we'll conclude with an update on the z concierge program. Alright. So let's get going. First of all, if you are new to this community or even not new to this community and you haven't joined the, online IBM community for AI ops monitoring and observability, now is the time. I'm gonna post the link to this in the chat as well, but you can click that QR code as well and, join. The important thing to do is first log in, which I didn't do the first time I went here, but I was reading blogs and getting all excited. I just wondered why I wasn't getting notice. So, of course, you need to log in, and then you need to join the group. Once you join, you can set up your notifications. I personally want a daily digest to see all of the goings on for OmegaMon and the family, so you can adjust that once you join. We are posting events out here. We are doing blogs. There are threads of conversation going on, and we really wanna make sure that you are, participating there, and we're hearing your voice through this community. Okay. Without further ado, we want to introduce the new IBM z OmegaMon UI with Grafana. We're gonna do a demo for you today, but I have a few intro slides to help set context for you. With that, the first thing we wanna do is start a poll about whether you are using Grafana in your environment right now or not, okay, or if you even know. So there's a few answers there, and we'll review you review those together, after I give you a little bit of update. So first of all, why are we doing another UI? We already have several. And the reason behind that is that, OmegaMon is a very mature product, and there's been a lot of innovation over the recent years. And these different UIs address different problems, and we wanna help consolidate and simplify your world. We also want to modernize your world and make sure that your observability goes way up so that you can see across your entire ecosystem and you have extremely high performance and low CPU consumption while you do that. Right? So that's the reason behind going this new direction. We needed to start over. And, eventually, you'll have so much wonderful capability in this new UI. You won't need TEP, and you won't need classic for because you'll move to e thirty two seventy. So those will slowly just go away because we're gonna put so much investment in this new UI. But e thirty two seventy and this new UI are the way forward. Let's, put that poll on the screen, please, and see how we're doing. Okay. Very good. That's really interesting to know. Thank you so much for your feedback. We can go ahead and close the poll. It's good for us to know. And we need to put the slides back up on the screen. Didn't realize they would disappear. Disappear. Let's go right here. Alright. Next slide. Here we go. So this is the beginning of our journey, and we're using a train as our analogy for this one because we have several cars we wanna put on that train to make a very nice, long, beautiful train. And our destination is a full new user experience for you. Okay? And what we wanna do is take the experience to the next level, as I already said. We are also integrating this with the other IBM z AI ops technologies as time goes by. We want you to have this seamless experience as you move from one solution to another in this AI ops ecosystem. So it's architected in line with them, and it is a multistage journey. So if you didn't know, we already have a train with a few cars, and those include ITM rest API. And there is ODP, so that's the Omegamon data provider so we can externalize some data. We also introduced the AI insights piece, which gives you interesting information about, outliers and anomalies in your data. And then the latest thing, as of June 20, we released the OmegaMon data requester, which is a plug in to Grafana, so that you can have dashboards in Grafana showing OmegaMon data. Alright. Before we get into the demo, there are a few prerequisites that we wanna talk about. And the first one is not the first one on the slide, but something important. You need to be running hub temps on zOS because it's the one that has our rest API, and that is required for the plug in. So we wanna start another poll so we have a better understanding of our customer's environment. Do you know if you're running hub temps on zOS or on distributed? That information will help us know, who's the best candidates to start adopting this and help you go forward, which is why we'll talk about concierge in a little bit. You will need to update to that June release. So that's Tivoli Management Services six three four. You and part of that is the OmegaMon data requester, and that will be the plug in to Grafana. And there's instructions about how to put that in and how to import some dashboards that we've got that'll get you started. And in this release, you will need your own instance of Grafana, which is why we asked the first poll to may see who is, in combination, has ITM, sorry, HubGems on zOS and also your own Grafana. If you don't have your own Grafana yet, it's actually super easy to install. Todd, who's gonna be doing our demo, did it within a day and started playing with the new user interface. So this is the important information for you. With that, I would like to get into the demo. We can close that poll now too. Yep. There we go. Oh, look. Good half 50%. So let's go ahead and start the demo and get going on the good stuff. So we will start this demo with a look at the enterprise overview. This is going to be probably something you're gonna wanna bookmark and maybe use as your landing page for for monitoring. This particular dashboard and starter set gives you an overview similar to some of your event overview screens in in e thirty two seventy and TEP. There's a lot more information presented than there are in the other UIs just because of the versatility of the the platform. And you can see I've got just the highlights, really all the agents here on display. First use case we're gonna work through is a CICS work case, and we're gonna work it through three different angles. So we have an alert that has fired, and we're gonna take a look and see what this alert does. And so we're gonna go in here, and we're gonna take this is just a little bit of customization that we've added on to the starter dashboard that's gonna link me straight to the CICS region that triggered the situation. And so we can see that we've got a couple of transactions running, kind of a long response time for for the transactions. So let's take a look at the first one, the one that's been running a little longer, and see what it's doing. It's in the SQL call, so it's doing something. And and those were now let's take a look at this other one, the second one that's that doesn't seem to be using very much CPU in spite of being running for quite a while because it it thinks it's in d v two also. Come down here. Looks like it might be the same plan. Let's see here. We're in wait lock for the status. So let's look at the lock conflicts. Okay. So we've got two people listed in conflict. So let's see what we've got. We've got an owner and a waiter. Probably wanna look at the owner and see what he's doing that's holding this other guy up. So look, we've got a whole lot of updates going on here. Right? Lock zones, a 113 locks owned. Lot of activity, a lot of locks held. And look at this, no commits. And so what we're probably gonna wanna do here is we're gonna wanna call the CICS or whoever whichever developer wrote this SQL and you tell them, hey. You're you're not doing any commits. And maybe they'll cancel the process or maybe you're based on your procedures, you may cancel the process. Now let's take this same situation, and let's let's take a look at the some of the other ways that we can cross navigate from this events console, and we can kind of drill down from several angles. Let's assume that we didn't have a situation. Our ability to here and we'll see, wow, our c three c I c x plex is really using a lot more CPU than anybody else. So let's go down and we can look at this as from a CICS point of view. And you see we click on here. We're gonna go to the regions overview. Okay. And it was this guy here. It looks like he's doing most of the work. Let's look at the task details. Okay? And we'll see what we saw on the other screen. Now we've we've made a shortcut for the situation that took us here. But if the situation hadn't occurred, we could still end up in the same place, and we can see the same situation. We don't necessarily have to go through the rest of the navigation, but we'll know that if I look at this this particular plan, we're gonna see that, you know, once again, I have an owner and a waiter, and the owner has not done any commits. Now let's go back to enterprise overview again, and let's take another angle on this. So we have our c three, c I c s plex r c three, which is running pretty high, especially compared to the others. But, I mean, we've I know we're running very high here. And we can notice that, you know, at the top of my top 20 CPU jobs, I've got a CICS region. So let's drill down here and look at it from the zOS point of view. We'll look at the system CPU overhead. Okay. And we can see that this has recently started using a lot of CPU here. Right? And one of the things you can do here if you want to and is is you can narrow this time frame down, and you can do that through the last six hours through the time manipulator. We can go up here. We can do last six hours. We can put an explicit time, or we can drill into a little bit of a a time, and we can kinda see detail. So in in any Grafana dashboard, you can do this quick little drill down and just reset the time, and it will reset every time sensitive visualization on this particular dashboard. But overall, you can see that this guy's using a lot of CPU, and he's spending a fair amount of time in CPU loop index. So what we're gonna do is we're gonna maybe think about running an inspect. Right? And this might be something you're familiar with from d thirty two seventy in TEP, but this is gonna give us detailed information on how the particular task is using CPU, where it's using CPU, what module that's running its CPU in. And then as you can see, it comes back, and it's giving me detailed level information on what load module is doing what you know, where it's spending all its time. Just a big break good breakdown, and you can then, you know perhaps this is a new code release they just put in, and you need to let the development team know that they may have a bad module on their new code update. And so now let's go back to enterprise overview again, and I'm gonna show you how easy it is to to change your data source. So if I come over here to my data source, I can connect to any any one of dozens of data sources or as many as you want. And then every one of these represents another hub TEMS that I can connect to, and I can instantly visualize data based on any system I wanna go to. So the for the next part of the demo, I'm going to go to my demo system r s o one, and we're gonna go through a couple scenarios here, and we're gonna do some general navigation on this other system. Okay. So we've landed on our our other demo system. And what I see right now off the top is there's a old message age MQ alert. It tells me the origin node is CSQ3, and it's on RSO2. So I'm gonna open up my my MQ monitor and see what it tells me is going on here. My queue status has some warnings, has some queue health critical. That's probably gonna be, my issue. Let's take a look at the queue itself and see what we see down here. Okay. Well, you can see definitely see one of the queues is is rapidly approaching full, way out of balance in the puts and the gets in these two in this particular queue. And we're 84% full. So there's something going on here we need to take a closer look at. Let's take a look at the, recent queue statistics here. Okay. Oh, yeah. Something's gone way out of balance here, about 1845. And we are just on track to to blow out the queue here pretty soon. Alright. So if we go back to the queues again, see if there's anything else from the queue perspective we can look at. Historical queue statistics. Oh, yeah. This is definitely way out of way out of bounds with normal. So we need to take a look and see who this is is maybe doing this. Okay. So once again, let's go back and look again at the queues and take a drill down from another perspective here. Same queue, still climbing. Look at the queue status and see what we see here. K. So we have a couple of, applications and we have some users identified. And so I think we need to get in contact with this particular user or one of these users and and see what they're doing. Let's fill up this queue. Maybe they've changed to something in their application. So we're gonna make a phone call. We're gonna tap the owner of that particular application looking into what they've done and whether this is a as a problem or working as expected. But, ultimately, we need to resolve the situation. Let's go back to monitoring. Now I've got a channel retry. So I'm we have problems with the channel. Looks like it's the origin origin node is R S 02 and S C S Q 2. So let's look at the let's go back to the MQL review and see what we got. Oh my gosh. Things are going to crap now. So we'll take a look at CSQ 2 because that's your origin. And let's take a look at the channels because we've got channel health critical over here. CS q two to CS q one, bytes received and sent, all out of whack. Everything's everything's lighting up. CS q two to CS q one, Retrying retrying. Let's go back to CSQ one and see what's going on. Seems like we're trying to get CSQ one. So let's hit channels from the CSQ one perspective. This queue manager on the other l par, and see oh, we've got one stopped. So what we're gonna have to do is we're gonna have to restart that channel, and we're gonna hope this cleans everything up. So let's assume we we've stopped that channel, and we're just going back to regular monitoring here. And we see, something going on with JVM. Deep occupancy, maybe. Let's take a look and see what this is doing. Let's look at heat details and see because it says it's a heat occupancy value. Oh, wow. 98% of your heap value. Right? That's the last five minutes. Let's take this back a little bit and see what this thing's been doing. There's a job that's using a lot of heap here. Oh, that's doing some intermittent, maybe some timer workload. Let's see what we got going on. Let's go back a little bit longer and see. Well, seems like the behavior of the application is relatively consistent. We don't have any evidence that maybe anything's wrong. Maybe we had some problems doing some cleanup here, but, overall, it's been cyclical. So what I think we probably wanna do is, I think we wanna take a look at this this max heap a little bit and set that to a little higher value. But, also, potentially, we need to think about whether this is a threshold we need to set a situation for. And so we'll check-in to that. Maybe we'll set a situation. Maybe we'll follow-up with the application owner, and and we'll take a look at their max heap size and see if maybe that needs to be adjusted. And so we'll contact the application owner here, and we'll we'll go back to monitoring. Let's assume we've we've dealt with that situation. Let's go back and just kind of start with the enterprise overview and do some navigation. Just just kinda get a feel for the navigation of the Grafana UI. Right? We have one job that's that's hogging the top 20 CPU jobs. There's just not a lot of activity is what it's gonna come down to, but let's see what's going on over here in general. If we click here, we get to CPU overview, and it's gonna give us some some information about what's going on system CPU overall. So this is just the, you know, kind of breakdown of CPU that you're gonna see if you if you drill down. Obviously, this job is at the top of the list. It's doing something. We're we'll we'll we'll not worry too much about what it's doing, but we're gonna go through and just kinda talk about how Grafana allows you to navigate some of the stuff and and manipulate the data. So you see, we're looking at last six hours here, and we discussed this earlier in the first segment. But it's just so simple to drill this down and keep drilling this down to a time frame until you can just come up with the list of tasks that we're running at that time. And, again, this guy's at the top. That's just one example of drilling down. We'll go back to the Sysplex overview, and we'll take a look at some of the other monitors. D v two thread approaching max. Let's see where this takes me. With the starter set of dashboards, we are allowing you to drill down in all these applications, and often we're doing cross agent navigation to get information. And then you can see this is where we we can keep drilling down and keep drilling down. And depending on the agent and the application, we can get down pretty low. We'll go back and we'll start with maybe CICS. And anytime you see this this blue, you wanna drag your cursor over it and kinda just see what your options are. This case is gonna take me to the CICS overview. And then on that point, I can get down as low as I wanna go. Task details, storage summary, file data resources, task history, etcetera, LSR pool information. We can drill down, and we can keep drilling down and drilling down as we need to. So it's very easy to navigate user interface, and the start dashboards are a pretty good starter set. Let's talk about the general navigation flow. So everything on the screen, every one of these little boxes is called a visualization. And you can add these visualizations or delete these visualizations. You can edit them individually. You can take view the view option, and you can take this particular visualization and make it full screen. Right? And so this might not be a good choice for that information, but some of these longer lists like the alerts, there's a couple of ways you can we actually have a link for the alerts, which accomplishes the same thing. So we're gonna talk about editing and manipulating dashboards. There's a couple of ways to initiate editing in the dashboard. If you, you know, go to the top right, then you hit edit. That kind of enables sort of an across the board dashboard edit mode, which you can then I can just take these visualizations, and I can do whatever I want to with them. I can drag them around. You know, I can make one bigger or smaller. I wanna make this one bigger. It'll push the others out of the way. So you can kinda move everything around like that. But then there's another level of of adding at the visualization level. Or we'll initiate an edit for this visualization here. And we'll just point out that there's a whole lot of tools, a whole lot of capability in what what you can make the dashboard, the visualization look like and present. You have a a, very intuitive editor that's built made with pull down menus. You can group by filter. There's some system farms you can pass. And, ultimately, what this does is it builds this this formula for SQL that we pass to the API. Also, they have this other function that's called transformations, which allows you to to do some additional manipulation of the data. You can see in this case, we're doing organizing fields by name. We're doing some some field renames as we present them. We're doing some sorting. We're limiting it to 10 the top 10 CICS PS flex. So that's additional transformations that we're doing in addition to the query editor. Also wanna point out here that, when you initiate the query, when you specify the data source, you have the option of of specifying the data source, at the dashboard level, but you also can specify data source at the visualization level. Most cases, you're gonna wanna use this built in variable that's data source because that's basically saying use the same data source as the dashboard. But there's other things you can use as the data source including other dashboards. So that's something that we'll demonstrate here in another, in another segment here. So let's go back to the dashboard. We'll pull up an an example of using the a dashboard as a data source. As we look at this particular visualization here, and you can see that it's using another dashboard as a data source, and that's also an option. And, again, using transformations to manipulate some of that data. So if I wanna add in another transformation to this or any other visualization, you can see there's a whole lot of little widgets for manipulating the data, filtering it, renaming it, sorting it, doing merges at above and beyond what you would have in the call to the API. So there's a lot of tools to present the data any number of ways built into the to the product. So let's exit. Let's go back to main dashboard, and let's take a look at if you've noticed that there are times when, the dashboard is opened or a link is clicked, that sometimes we open a new web tab and sometimes we do not. And so I'm gonna demonstrate where that's specified because that's all customizable. Typically, the higher level dashboards will open a new link, or a new tab. The others often open within the same tab, and there's a little better performance opening within the same tab. But it's certainly it's a 100% up to how you wanna customize it, and it kinda comes down to personal preference sometimes depending on how you just like them out to manage your browser tabs. So I wanna come in here into this particular visualization here. This one actually has several links built into it, and so we're gonna we're gonna go down to where the links are defined here. And we're gonna take a look at one, and we're gonna edit one and show you where you'd make the decision here whether you're gonna open this in a new tab. Again, totally customizable based on preference. I'm interested in feedback from customers on on what they would for the default be for some of these starters, but it's it's totally, totally up to you how you do it. One of the interesting thing about the links that that I wanna sort of point out, and let's go back to the dashboard here, is that these links don't have to be other Grafana dashboards. I mean, I've got a link that I put on here that's gonna take me to my OTP Grafana demo system. It's on a different server. It's Grafana, but it doesn't have to be. It's it's gonna take me to a whole other link, and this is my ODP system that it's linked me to. So, again, they don't have to be links to other dashboards. They are links to pretty much anything you want them to be links to. So, obviously, we can remove a visualization if we want to. Right? Remove just as simple as that, we can remove the visualization. We go to the top. We'll add a visualization back in. And we're gonna demonstrate something that I think is a pretty unique feature in that. I'm gonna go ahead and I'm gonna import a a workspace from e thirty two seventy and build a visualization out of that workspace. Now what I've done is I've I've already cut a a copy of the SQL code. But how to actually do this in greater detail will be covered in a in a short video in the near future. But I've cut and pasted the SQL code directly from the source of an e thirty two seventy workstation that I'd like to import to Kravana. Alright? So I'm gonna paste my I'm gonna paste my formula in here. Right? And you have to clean this up a little bit. The spaces and all that kind of stuff don't always translate great. But you can tell that you've got good SQL when your update query form lights up and it's actually available to be clicked on. So I'm I'm gonna update the query editor. I'm gonna make my visualization a table. By default, you wanna always do this when you import because you don't know if you've got time series data necessarily or not. And I'm going to refresh, and you can see I have now imported a, IMS workspace into Grafana. Now if I don't wanna use a table visualization, I can come up here and I can select anyone I want to. I mean, it will give you suggestions, which is also kind of a nice touch. So if you really think, okay. Let me see how I wanna present this. Kinda gives you a picture of what it might look like. And voila, you have you have imported a a workspace from your e thirty two seventy and made a Grafana visualization out of it. Okay. So there's one last thing that I wanna kinda demonstrate because it's it's something that you're gonna you're gonna need to do as part of your setup and then just give you some background. Go back to my main dashboard, and we're gonna show you how you're going to define a data source because it's very simple. In fact, the installation of this whole product instead of this whole product is very simple. But you're gonna go to your your your little menu here, and I'm gonna go to data sources. And we're gonna discard because we're not gonna save any of those changes we made to the dashboard. And here are the existing data sources, and each one of these represents a a zOS hub tems in our environment that we're using as a data source. But if I wanna add a new one, I'm gonna click add new data source. It's already got o m filtered from from being in here earlier, but let's let me show you the whole list. So I'm gonna type o m as my filter. It's gonna take me to that OmegaMon data sources plug in. This particular plug in is the core of the ODR of the OmegaMon data requester. And I'm really it's a very simple setup. I'm gonna give it the the URL or the IP address of my TEMS, my credentials, and my port number, and I've got a new data source defined. And it's as simple as that. So, hopefully, this has been helpful overview on, kind of a peek into the the capabilities of the new UI, and, you know, more to come. Thanks for listening. Alright. Thank you, Todd, for a great demo. We had tons of questions coming in while you were doing that. The team has been responding. So, if you have more questions, keep sending them in. And we want you to know we did have several beta customers, and we had fantastic feedback from them, where this is really a game changing observability piece for them. And so this is not totally fresh, like, nobody's tested before. We have real customer feedback, and we are also looking for more customer feedback. Speaking of which, we want you to think about coming to Tech Exchange in October. We are going to have a customer advisory council, and we need your input. So as you start to implement these and you start using them, we wanna know what your experience is like and whether you would like to see us tweak them or not. The really cool thing about these dashboards is we're just providing you starter dashboards to get your brain going. You are going to then be able to create your own custom dashboards very easily once you get, involved with Grafana. So please give us feedback. Please come. Let me put the link to the, event page there on our community too. So there's a QR code and the event page. We would love to have you, so please register. And then real quick before we move on to the next section of the content, let's talk about the future of this UI. Somebody asked, does this do everything that TEP does? And, no, it doesn't, but that is part of the road map. Right? We are looking to take it over in the future. Today, it is about real time observability and some near term history debugging that you can do. Right? And very soon, we're gonna be making more changes. There are administrative functions coming by later in time. Right? So coming up soon is administrative functions. We'll also be working on history data long term history coming in, and that's where ODP comes in. I saw a question about, is ODR replacing ODP, which we should not use, those acronyms. So the data requester is just a Grafana plug in. OmegaMod data provider is something else entirely that serves up data. And so don't please try not to confuse the two. And it at the same time, we are growing all of this. Also, some of you, as we asked earlier, are not using HubTams on z. There will be a way in the future if you're not on HubTams on v z to use this UI. So don't fear. That is part of the plan. We are also expecting to run natively in zOS zCX. Okay? So there's a lot more coming. In fact, the road map is so long and so deep. That's why we need a customer advisory council to help us prioritize the order in which we address these things so that you can start really getting the most benefit from this new user interface. Okay. That was super exciting, and I need to hand you off to Dan Wigan and Ash Mahe. They're going to talk to you about other innovations in the IBM IBM z OmegaMon portfolio. Gentlemen? Yeah. Thanks thanks, Anna, and and thanks, Todd. So, obviously, you know, kind of getting started, one of the the biggest innovations that's, we've done, very recently is the new, Grafana UI for OmegaMon. So, you know, it's all about how we continue to to modernize and and keep OmegaMon relevant as really a core building block of everything that we're doing around IBM z AI ops. So it's something that we're really excited about, and it continues that history of some of these great innovations that we've done going back to config manager, and and IBM OmegaMon data provider. So I'll cover a little bit here that we have introduced in the last six months to a year. I'll cover the OmegaMon core and data and then hand it over to Ash Mahay to go into some of the new innovations that we've delivered in all of the different subsystems. And given that we only have about twenty minutes, this will just be a high level overview. So, again, catch us at one of the the conferences like Tech Exchange or Share coming up, or reach out to us and we'll be happy to to go into any of these topics in in more detail. So as as we kind of talked about, I I kind of wanted to level set on some of the the couple of key things that we have. So the first one is OmegaBond data provider, and and hopefully folks are are very familiar with us. This is our way to stream data in near real time. So think of this as a push method for moving data out to different platforms. So we can send this data out in a JSON format. It covers all of the different agents. But one of the great new innovations that we've done and based on a lot of the questions that we've had from previous summits is as of last November, we can also now stream those same OmegaMon metrics in an open telemetry format. So we had a lot of questions about, can we integrate OmegaMon with our observability solution like Dynatrace, like Datadog, like Splunk. And we can now do that in in an open telemetry format. And as this continues to evolve, as the standards get hardened, certainly, IBM is is leading a a core part of that. We'll we'll see this become more and more prevalent across all of our clients' observability solutions. But I I did wanna make sure that, I we mentioned that, we can support OpenTelemetry today. So if OmegaMon data provider is our way to push metrics, we've also talked about, our rest service. And this is why we're asking the questions about, having data, or your hub tems running on on zOS. So this is our way to request or pull data from the system and is what the Grafana dashboards are largely doing today. As we've kind of mentioned and I wanted to reiterate is we do have a statement of direction when when we announced the the new Grafana based UI, is that we do plan on on pushing that REST API into the hub temps for wherever our clients are running it, whether it be distributed or or zOS. In in our first phase, we we only support zOS, but, based on our early findings, this was roughly around 70% of our IBM clients. The other key thing that, we put out in the statement of direction with that latest announce is we do plan on shipping at some point in the future, a version of Grafana that runs on Linux on z and in zCX. So this is for all of our clients that don't want to leverage, their enterprise Grafana and want to run their MegaMon UI, solely on on platform, we'll provide that ability in in the near future. The other thing too is that this also allows us to to run a mix of things. So we know that a lot of clients want to do observability in an enterprise solution and also do their their core monitoring on z. So this really opens up a a mix and and different ways of of doing things. So I I did wanna touch briefly on, our AI and and machine learning. So on the left is the way that we've done this with all of our situations where we've generally created a a static threshold. It allows us to go through and and monitor our environments. These thresholds have largely been set by a couple of different ways. One is that, something bad has happened in your environment in the past, and you want to be alerted as you get close to that. The other is that a lot of our SMEs and and core systems programmers just know their environment so well. They know where they want to set their monitoring thresholds. But we also want to start to ingest more and more AI, into our OmegaMonts. And this is where we started to leverage the, OmegaOne AI versions that we have that we can start using historical data to better understand, those thresholds. And this allows us to do, better anomaly detection for very specific kinds of of use cases, directly within the OmegaOne agents. And we'll see these are bubbling up into those Grafana UIs, in the near future as well. So just an example of one of the cases that we first delivered was into our MegaMon AI for ZOS agent, And it was all about detecting abnormal, MSU consumption. So working with, again, our sponsor clients, we had one of our clients that applied a change to their environment. And for a period of about three weeks, they were consuming an extra 100 or so MSUs. So not detecting this for three weeks ended up costing them about, 60 k euros. So we built directly into the OmegaOne AI for for zOS that specific use case on detecting abnormal MSU consumption. So again, being able to to understand where your environment is normally and historically, and being able to detect deviations from that. Just a couple of other brief use cases that we have across the other agents. Abnormal garbage collection in JVM, abnormal transaction response time or CPU and and CICS, abnormal data movement in in networks. We also have some AI, use cases built for for storage. And other agents that aren't listed here are are coming in the near future as as well. So together, the the AI insights using the historical data can work directly side by side with everything that you're doing with the Omegamon situation. So it really provides that that comprehensive and modernized way of of looking at your IBM z infrastructure and doing all of the great resource monitoring that that we want to do. So look for, again, as as Anna had mentioned, the ability to to look at our situations directly from within that, new web based, UI, as we move forward. So we have a a lot of exciting things to to plan and and do around that space. And with that, I'm gonna go ahead and and turn it over, to ask for, hey. But before I do that, I wanna do mention one one more thing, that's we we can't mention enough, is configuration manager. If you're not using configuration manager today, I'll come back and talk a little bit about the the concierge program. It really allows our clients to really simplify, their updates, their upgrades, their their maintenance for all of the Omega Mons using ConfigMgr. So we've had clients that have gone from, weeks down to hours and even some clients that have fully automated, their updates and configuration using ConfigurationMgr. So, if you're not aware or not using this, pay special attention when we come back and talk about the concierge program here in just a little bit. With that, let me turn it over to, mister Ashmahey to go through some of the other, core updates. Thank you, Dan. Appreciate it. Alright. So as Dan said, we only have a few minutes. Usually, this will take us an hour or so, in fact, more, to present, all of the great updates that our agents have, provided over the last twelve months or so. So quickly, AmigaMon AI for zeros. As mentioned earlier by Anna, one of the key focus areas for our newest agents, the version six one agents, is to try and upload as much of the CPU processing, the heavy lifting heavy processing into onto zipped engines. So the MiGma for a I MiGma one AI for zedos six dot one in fixed back five updates, we've increased considerable amount of, offloading to zipped. And, with RMF currency updates, so RMF three dot one came with some additional, capabilities that we are now pulling into Amiga one for, ZOS. And also navigation. The customers have told us navigating through the ThetaSentry UI can be quite complex, if you're not used to it, of course, because if you prefer the graphical user interface, the Theta 70 UI could be a bit more daunting. So what we've tried to do is simplify the navigation using tabs. And, so we'll give you I I don't think we have time for examples, but, just so that, when you do go to the latest fix packs, you'll notice, some different workspace navigation. And Zenoast container platform. Now you may have heard or not heard that, you can deploy container images using Kubernetes onto zeroes. Zeroes connect API deployments are now available through zeroes connect container platform. So you can distribute, Zebra's Connect image or container image through Kubernetes onto Zebra's. So customers wanted to be able to track, these container images and, ensure that they they can, monitor specific containers and alert on them. And so we need to provide the indicators and identifiers of your container infrastructure, which is the Kubernetes part, the control plane appliance, and obviously, the containers that run-in the UNIX system services as well. So just an example of some of where the some of the areas where we've had actually have contributed to uploading to ZIP processing is, the address based CPU utilization. That collection is done every three two point three seconds. So you can imagine there's a lot of data being collected at a short period of time. So uploading that to ZIP processing has, contributed to a reduced amount of CPU generally used by the agent. And similarly, for the real storage table. If by default, we have enabled, zip offloading to be yes, or if you have the do not have the capacity of, zip engines or you do not have any zip engines, you can switch that off to no. Or otherwise, the end the engine the agent will run as it was in the past or did in the past. The MIGO for d b two, we again, normal pattern, we are looking at areas where we can offload CPU onto ZIP. So CPU for the batch reporter, IO processing has been reduced. And in our development environment or test environment, we noticed roughly about 10% saving with the, with the batch reporter updates. We also delivered nine ideas over the last twelve months. One thing to note, if you are looking to monitor d v two thirteen on zOS, you'd need to meet on Amiga one for d v two five dot five. Previous versions do not tolerate, the newest versions of d v two. So d v two thirteen, you need to be on the one omega one d v two five dot five. We also support, the two functional levels that delivered last year, five zero four and five zero five. And there are some gaps customers have told us that they will not shift over to the page 70 UI until some of the gaps, in the page 70 UI are closed. The classics are preferred. So we have gone through an exercise look, identifying the the enhancements for the face empty UI to close those gaps. Here's our list quick list of the nine, ideas we delivered. As you can see, they're top two. Those are gaps in the face empty UI, so you seem, to be able to see package details and also enabling application trace facility in the face empty UI. That is now available. And AmigaMon AI for kicks, this was released, last year, so six dot one that is. One thing to note here, and this is one of this has been a major update to the portfolio, to the product agent, in fact. We had a limitation on the number of tasks that could be stored in task history. The limit, was down to the dataset size or four gigabytes per region, and that approximately saved around about 4,500,000 transactions per region. Of course, if you've got a very busy environment, and we have many clients who have, hundreds of millions of transactions running per day, The task history was quickly filled up and, the old data was overwritten. So we've removed this limitation. The limit now is potentially up to a dataset size of 16 terabytes. So just imagine four gigabytes was 4,500,000 transactions per region. 16 terabytes, we're looking at billions of transactions per region, or at least, cost of QuickSplex. And another update, we provided is so if you do not have the capacity or task history and, you do not have the ability to increase up to 16 terabytes, we've provided the ability to or the option to pause task history. So if you if there's an issue that's occurred and you want to go back in time in task history and you don't want the task history to be overwritten because you're you're running so many tasks over the time, you can pause the task history, go back in time, have a look at those tasks that you're investigating. You can extract some of the details using p f six. You can extract the tables, from the page sent to UI into a CSV dataset. So you've got that data offloaded, and then you can label the task, history on it and pause it. But, again, as I mentioned, focus areas of reducing CPU. If you look at the bottom, section, performance enhancements, most of the task issue processing is now zip eligible. This is a major update. And so depending on how much task history you have, you will probably see potentially a considerable saving on CPU consumption for that processing. A data collection. And so service level, level analysis is also enabled for Zip engines. So you could see just by the two updates there, we can, reduce the overall CPU consumption of the agent considerably for the Amiga one four Kicks agent. And And then Citrix Pack one was released recently. And these are mostly to address some of the, client requirements. So average response times at the Kicks region level. And, you've got, transaction rates, but customers also want you to be able to see this SIT parameters and the global options in the third semi UI without having to leave the the, the UI. So these are available, in the third semi UI when you update, to fix back one. One thing to note at the bottom bullet, so if you are using the T Mobile enterprise portal server or portal graphical user interface, the job certificates will have expired or will expire in August, my understanding is. So please apply the latest maintenance for all of the unique one agents, not just Kicks, but all of the agents that their Java certificates will expire. And so you would like you probably want to update your certificates prior to August so that you don't, have log on failures to the tip. A middle month for messaging. So fix pack eight was the last fix pack we delivered. And one of the continual updates here is that we now pull in SMF one one five records with the latest MQ on zOS, versions of, I think version nine dot three onwards of MQ on zOS. This has further enhanced the q statistics or q monitoring in in in a middle one. So if you see this workspace, you probably can't drill it, zoom in as much, but we provide a specific, table and workspace where we show the additional metrics that we can obtain from SMF one one five records. All of these metrics are eligible for streaming. So if you have an OmegaMonkey data provider enabled and you would like to push the the data to other platforms like Elastic, Insta, and so on, you can do that through the AmigaMon data provider. One of the great updates for the messaging, agent product, fix back with fix back to eight is the ability to take administration or admin k, updates do some administration, should I say. For if you have a look at these screenshots, the first one on the top left, you can actually alter the MQ manager, server definitions. And to the right of that, you can actually alter the queue definitions or actually create a queue using the base MTUI. In the past, you would have to jump to the TEP to an enterprise portal to modify, objects such as the queues. But now you can do that through the FaceTime UI. So if you have, for example, an MQ as Todd shown shown in the demo, if you have too many messages on the queue, you could go jump to FaceMTO UI and take some admin you could take some you can make some changes or take take some, take actions, should I say? Got tongue confused there. So with the take action, you can delete the message. You can also, in this case, in you can update the queue definitions if the queue max is growing or rather the queue depth is growing and you're quickly touching getting close to the queue max. You can quickly alter the queue definitions and increase the queue max limit and save. And therefore, you have now bought yourself some time to go and see and deep dive into the queue messages and see what their mess where their message is supposed to be going, if they're related to a channel initiated that stopped, or if their application that's supposed to pull them off the queues is not available, then you then you have time to at least resolve that before you have rejected messages on the other side. And on the bottom right, you can edit channels. And bottom left is if you would like to issue MQSC commands, you want to update the MQ definitions on zOS, you can issue those, directly from the third time UI or or equally, you can edit a situation and run that situation periodically, to back up your queue definitions. K. One thing you'll notice with most of our agents, is that we are now issuing messages to syslog when, when the agent starts up. So if there's an error, you'll see a standard error message. If the error if the agent has started successfully, you'll see subsequent messages around the agent started. And so there's some performance updates as well with the MQ messaging agents around it multiple situations that are active at one time and pulling the data sequentially. AmigaMon for JVM six dot one, we've released FixPack three recently. And with FixPack three, yeah, you'll be able to actually go into the resource consumption and the application level of, details of your your traditional WebSphere application server. And we're using PMI to pull these metrics in. So web application statistics, if you've got JSPs or you've got servlets, we can now provide you the response times and the throughput of those, requests. But also the any connections external, For example, JCA or JDBC connection, we give you details about the pool statistics. And if you're running e j EJVs, we have provided you EJVs statistics and so on. And if you're using web services, in some cases, you may be using web services, we provide you those metrics as well through the PMI, interface. And one customer we had several customers actually requested this. They wanted to be able to monitor the APIs that are executed across the Plex. Rather than just the individual looking at individual JBM's per alpha or ZRS connect instances per alpha, you can actually, with the cluster view, look at, have a quick overview of all of your APIs that run across the Plex. And then you can drill down if there are any errors that you want to further analyze. Here is an example of the cluster view. So on the left hand side, you can see the, or truncated the APIs that were called and the methods and how often they were called, but then you've got the request count and the error counts and so on. And you can then drill down into those specific JVMs where these, APIs are called and where the errors are occurring. If it's back end, if it's a CICS region to some system of record, you will have enough details to drill down to do a need mover kicks to analyze and and isolate those issues further. Here are some examples of the, WebSphere application server statistics that we provide. So this is your, application server and JSP details. And and I haven't shown the others because otherwise, we are definitely gonna run out of time. Current life cycle updates. So just for your information, coming soon or or ending soon in August and beyond, some of the agents are going to be end of support. So as listed there, top left, for storage5.4 will soon, reach end of support. And similarly, with some of the ASR the larger suites. So please do take note. And if there if you are an older version of the agents, we urge you to move to the latest agent agents so that you have continued support for those products. And so if you would like to learn more about the, data data provider, Omega one data provider that Dan covered earlier on, we have a QR link here. This is your master of blogs, I would call it, that Jim Perrell creates. So please do, take a note and then register also to the community, as Anna mentioned at the beginning, to be notified when we do publish new blogs and or events, in our community. Closing remarks. Over to you, Dan. Alright. Thanks thanks so much, Ash. We I know we're running a a couple of minutes, over, so I thank everyone for staying, but we have a lot of exciting things to to get through and and touch on. So I I just wanted to close, and and start to a poll, just to see folks' familiarity with the, OmegaMon concierge, program, for IBM z. And if you're not familiar with it, it really is all about helping our clients move up to an upgrade to the latest versions of the software that we have. We have an awful lot of investment in everything that we're we're doing. And we really want to make sure that all of our clients are able to take advantage of the the latest details and and things that they're doing. So the concierge program is is really a great offer from our partners in in Rocket Software that really wants to make our clients successful. So we've seen a number of of clients use concierge to start to adopt configuration manager or move to the the latest versions of the agents. With everything that we're doing, we really stress that clients stay on top of the latest versions if if at all possible. So we want to make sure that, we we really enable our clients to to move forward. So the concierge program again is there to give you access to a a couple of hours of meetings with our deployment experts, really to get you up forward and and moving along with, the OmegaMon solutions. The last thing I do want to mention is we've thrown out a lot of QR codes. So as we go back and and get, the slides, I I strongly recommend that everyone go out and look at all of the information that we have. This last one is really to a set of videos, that we have that help our clients, do everything from configuration manager to a MegaMind data provider, everything that we want to to go and do. I know, when I have questions on how to do things around the house, I always go out and and grab a a video on how to do some of those things. OmegaMon is is no different than that. We have a a great video library that we can go and and leverage to show us everything that we want to do from OmegaMon. And, last but not least, I want to thank, all of our speakers, Anna, Todd, Ash, for for joining us today. We have a lot of exciting information that we're doing with, the Omegabonds. So look out for, some additional summits for new updates. Please join us at share, the the tech exchange, the customer advisory council, everything that we're we're doing, to continue to talk about the solutions that that we have here in in place. And for our folks in the the EU that normally attend, GuideShare, we also have a plan to to be present there as as well. So with that, I wanna thank everyone for attending and and taking some time out of your day.