Transcript
new webinar series called the Automation Desk Spotlight. The goal of this series is to give a spotlight to one of the amazing projects that people have been created and Jorge, with his Grafana dashboards, will be the first one to kick off. Jorge, for everyone who does not know who you are, do you want to introduce yourself? Yeah, yeah, absolutely. Can you hear me? Yes? Yes. Okay, yeah. Hello, Maurice. Hello, Jonah. Thank you for having me here. Madalina as well. Thank you for organizing this event. My name is Jorge de la Cruz. I'm a senior director here at Veeam. I have been working for Veeam eight years already. Before joining Veeam, I was part of the community. I think I still am because I'm always contributing to the community as much as I can, you know, GitHub and whatnot. I'm trying to go to the Veeam 100 events and whatnot. But yeah, I was part of the inaugural or initial Veeam Vanguard group back in 2015 in Las Vegas. That was quite nice. At Veeam, I manage Veeam One. It's my main product. Veeam Intelligence as well, if you are using Veeam Intelligence. And right now as well, if you have seen Veeam On in New York, I'm contributing to the Data AI Resilience Module, which is really elevating the Veeam backup and replication servers and showing them into the new cloud console that Veeam is building. So that was announced at Veeam One. So I'm heavily contributing there as well. Awesome. Jonah, do you want to introduce yourself? Sure. If you guys don't know me, I'm Jonah May. I am a, geez, what is it now? Four or five year Veeam Vanguard, somewhere in there. And among other things, the user group leader alongside Maurice for the Automation Desk. And don't forget about the co-founder of the Veeam Community Hackathon. Yeah, that too. I said among other things. Yeah, yeah, yeah. I know. The whole resume on. Yeah. And well, my name is Maurice Kevener, VGA leader, VGA and now Automation Desk, Object First Ace, co-founder of the Veeam Community Hackathon. So Jorge, you created a slide deck that I am having here. I think you want to start off with an agenda. Yeah, yeah. Yes. Just move over. Yes. The next slide. Okay. So what you will learn during this session, what we have like 40 minutes more or less, right? Something like that. Yeah. Yeah. Maybe Q&A as well. Right. So let's see. Maybe it will take less time. I don't know. Maybe more. We want to go through the integration. So how the Grafana plugins into a Veeam environment and where the REST API fits. Dashboards. We want to show you all of the Grafana dashboard. Not all of them, but most of them that we have out there. The customization as well or tips. And then as well, the community as well with links. Right. So we move to the next slide, please. Let's take a look here. So the challenge, right? So the challenge is that Veeam protects everything, as you know. And well, that's not a challenge. It's perhaps like a benefit. But at the same time, when you want to really understand how are we doing when you have multiple environments like Veeam Backup and Replication, you will have Veeam One to monitor multiple Veeam Backups and Replications. But then, for example, Veeam One does not cover Veeam Backup for Salesforce in the case that you have that. Right. And so on and so forth. Right. So this is really the challenge that Veeam might have many, many. It has many, many products. And there is no single console, at least not today. Maybe with this new integration in the cloud console, I think this is going to be resolved. But until that is there, I think that is why we're here talking about this community product. Right. So many platforms, many UIs, many reports just try to answer the same question. How are we doing itself? So we move to the next slide. The data is there, which is the beauty of this. And there is multiple ways you can collect the data on this. We have been using the best way possible, which is using REST API. But yeah, the VBR console, then we have the Veeam One, then we have the VSPC 365, again, you name it. Right. They have different logins. They have different terminology, most of the times, regarding what they are protecting sometimes. And it is a bit hard to correlate across the products by looking at the different UIs. And especially sometimes this is even hard to serve outside of the team. Right. If you are a backup admin today, you have a few Veeam solutions, even a few VBRs, and you don't have Veeam One or Enterprise Manager, for example, that can be difficult to really share what are you protecting and what not. So yeah. And the reporting takes manual stitching. Again, in the case that you don't have Veeam One or Enterprise Manager or VSPC, if you don't have any of those doing reporting sometimes, yeah, it can be... I'm sure you have been using PowerShell. Every Monday morning. Yeah. So, okay. Let's go. So, one of the solutions, because this is not kind of like the silver bullet, but I will say that perhaps it's one of my favorites, because it's open source. If we go here, Grafana, right, is not the only option, because you have always Veeam One, with the caveat that it doesn't support all of the Veeam products, talking about the Salesforce and casting and so on. But yeah, or even if you want to do open source, you always have Savix as well, that is like a very solid solution. I will say you have as well OpenMK, you have Prometheus, but in any case, so when you're trying to put everything together, I think Grafana is a good solution. It's open source, it's vendor neutral, so it's not just it's going to show you just your Veeam and that's it. You can just show anything, right? They have many plugins and you can just connect to any database pretty much, right? We tend to usually, or on this project, using Influx database, InfluxDB, but you can connect to Prometheus, you can connect to SQL, you can connect to any of the, to any source really. That's what I said, that is already there. For what I see on customers, when I talk to many of the large customers, they usually have Grafana for many other purposes, you know, they might be for more real-time monitoring for other things that they're having, sometimes they just have it for the networking and whatnot, but Grafana is very widely spread, so that is why it's a good solution in my opinion. For the templating and sharing, this is the beauty. How I do this Grafana is like I build them once, I do the template, so I put variables there on the top and whatnot, so I prepare the queries in a way that they can be reused with anyone, right? I build the dashboard as much as I, you know, I think is going to solve the problem and then I share it with the community and this plug and play, which is one of the beauties of Grafana right now. No customizations whatsoever needed for the plug and play. You can do it later, of course, and customize everything you want and need, but yeah, the plug and play, it's very compelling to me. The massive dashboard library is not that just, you know, you can use the out-of-the-box we put together already. I put many in the Grafana library, but if you search by Veeam Grafana, there is other people doing as well other dashboards, and if they are not Grafana, but you are just curious about, okay, how I can display specific data, you are most likely you're going to find a dashboard that might suit your needs and you can take that widget and, you know, the logic at least. The alerts and automation, that is nice, but that just comes natively with Grafana, right? Depends if you use the open source or the enterprise, you can have more or less functionality on Grafana, but even on the open source, you have a very nice integration for alarms happening based on your queries, right? So if something is failing or you can just create pretty much anything, create alarms. From the Grafana dashboards, I have been using components that complement other things within the Veeam ecosystem, like a Postgres or a Nets database server and create dashboards with that data as well. It's really powerful. Yeah, well, you took it as well, I mean, you did it with InfluxDB in any case, but you expanded with Object-first as well, right? Yeah, I created an object. I wanted to keep that out of the scope, sir, but yeah, I did. I created an Object-first dashboard for the appliances that they created. Yes, so I wanted to mention it because it can always be plugged in together, right? You have all your Veeam monitoring, but you know what? Hey, I have an appliance here, which in this case is Object-first and it happens to have APIs. So let's put it together. So you expand whatever we're building for Veeam plus really deep statistics regarding your storage, because why not, right? Yeah, quickly. It's really powerful. You can switch dashboards and combine dashboards and whatnot. It's really powerful. Let's move to the next slide. Let's see. So let's talk about the plumbing a bit. What's what here? So every Veeam product ships a REST API. That is one of the strengths of Veeam that I like since the beginning, you know. In the beginning of the days, VBR didn't have any API. It was just Enterprise Manager, the first product shipping an API for quite some time. It was a very rudimentary and it's still working, but it's very old. It's not based in the open API specification. It's something very weird, but in any case, it works. And I've been using that, you know, since the beginning. But then after that, products starting to release in with APIs, right? Perhaps Veeam Availability Console was one of the first ones that it really introduced a very compelling API. Then the Veeam Backup for Azure, AWS, and whatnot. Then they were expanding the API Veeam Backup for Microsoft 365 as well. The API was since version perhaps 1.5 or something. But that's the beauty, that every new Veeam product or any Veeam product that you are installing or using today, most likely is going to have a REST API. And that is what you can unlock. All the visibility, you can unlock it thanks to the API, right? And moreover, even if the API doesn't have something that you need, most likely on the API that the web UI you are consuming is using, which is Veeam call it sometimes internal API, you can, with a web browser and the dev tools, you can clearly see the endpoints that they're being called and the response. And you can always take that API endpoint and then put that into Grafana as well. Not recommended by Veeam, but yeah, you can do that. So the picture end-to-end, this is what I have been doing for years. I'm not saying that you should do this, but there may be other ways. But this is what I've been doing in particularly, right? We have Veeam products, you name it. Then I, for years, I've been building like an exporter or a script. So there's two ways. With an exporter, you can use either Telegraph, which is very nice. And then with Telegraph, do a few API calls or even do SQL queries directly to the database, if that's what you want to do. Telegraph has many inputs that you can, you know, customize, or you can use a Basel script or PowerShell script. Most of my stuff is using a Basel script in Linux. But yeah, now with AI, that is because at the beginning, I started building all the Basel script. But now with AI, I'm pretty sure that you can just take any of my Basel scripts and convert that into PowerShell and then do the same, right? It will do the same stuff, collecting the same data from the same endpoints with the same logic and sending to the step number three, which is the time series database. I choose InfluxDB in this case, but you can choose any other database that suits your needs, right? There are many open source, like Prometheus is another one. Then you have as well like QuestDB, Arc as well. Yeah, you have many, many databases. And then finally, the final step is the Grafana, right? The building the dashboards, the alerts, the sharing, the queries. That is where you are most likely, I mean, if you take the plug and play dashboards, then you just land there and you have everything ready. But if you want to expand it on the building the queries, that's where your time is going to be most likely building those queries. Again, now with AI and depending on the time series that you utilize, you might have like a visual builder. For example, InfluxDB has a visual builder on the InfluxDB site. If you pick anything more conventional, like more SQL-based or Prometheus, you have the query builder inside Grafana. So you can just go very manually to select these from here. And it's very clickable and it's very nice, but you can always go into the query itself. And again, now with AI, I've been trying to improve a few of the dashboards that I have. You just put there and say like, hey, change this for that. And you don't need to do the queries anymore. AI does for you. But this is my flow that I've been doing. And if you give it a try, this is what you will install, having the script and having the time series and the Grafana. Yeah. Okay. Yeah. Let's go to the dashboard, the official part for everyone, because this is all theory and let's go to the actual looks. Yes. Yes. Now for the fun part, every dashboard that follows is on grafana.com. There is like a library already. That's one of the beauties that I like from Grafana is that there is all about the community. They have the Grafana dashboards that is all community uploading all of their creations. And yeah, you have there thousands and thousands of them. And you will see them by the IDs later on that the, I don't know, the IDs is 8,000, whatever. There's many, many dashboards in the community. So that is the fun part. I think I've been looking today at the numbers. There is a few like 5,000, perhaps even more downloads combined of multiple dashboards that I've been putting there for Veeam. For Veeam where VSphere, there's like millions, but for Veeam, there are a bit more than 5,000. So I'm going to show you VBR, VSPC, 365, public cloud and so on. So let's take a look. Yeah, but 5,000 is an impressive number. I can say that. Yeah. Thank you. Thank you. Thank you. So you see the numbers here. The numbers are absolutely crazy because the IDs, oh, by the way, these IDs are the IDs. We're going to share the deck later with you. These IDs are the IDs that you can find in grafana.com, right? So you just go to grafana.com slash and you put the ID, then it's the, you're going to see this, the dashboard. And the ID, well, essentially is the ID of the, it's incremental. So every dashboard that you keep uploading, it has an incremental one. So you can see how many dashboards have been people uploading there. And you can even see the time when I upload them, right? So the VBR overview is much older or the enterprise manager, super, super old compared with the VBR doing the direct export approach that I did for the VSA, not that long ago that there was already 24,000, right? So it's double compared with the initial dashboard that I uploaded, I don't know, maybe seven years ago or eight years ago, right? So yeah, it's funny to see this. Let's move to the next because these are just the IDs. Yeah. Click once. Okay. So this is the VBR. This is the dashboard that you can get out of the box for VBR API, native VBR API. So as long as you put my parcel script, connect to your VBR or VBRs, I'm talking with a few customers that they have the same script. They just clone it, you know, as many VBRs as they have because my script does not support the data collection from many. You just clone the parcel script and that's it. And yeah, they have like what, around 50 different VBRs. And the beauty is that all of them go to InfluxDB nicely, blah, blah, blah. And then they have the toggle on the top and they can just filter this view per VBR, which is very nice. And that came out of the box with Grafana and InfluxDB. So that was quite nice. There's lots of things to unpack here. So there is the daily success and warning or errors jobs. Then there will be the tiles with the fail success. Those are the jobs that the big tiles that it says fail, success, success, success. Those are jobs. So you can clearly see the last status by job with a big tile. And if you put it on a monitor, I have a monitor here. Like I'm this geek, you know, I have my own nock here. I have my monitor in vertical here hanging from a bookshelf. And I'm seeing this stuff that you see there, I'm just seeing here on my left, which is pretty nice. And then more information regarding jobs and whatnot. What I like from there as well is the bubble, kind of the second widget from the top right. The bubble thing is, yeah, that one. So the bubble thing, it's regarding time duration of the jobs. And if you see your bubbles within the norm, it's okay. But if some job goes wrong and crazy, you are going to clearly see the bubble out. So it's really stands out from your day-to-day operation. So again, you see your bubbles on the norm, it's okay. If there is a spike, instead of showing lines, I just show in here bubbles or lollipops. I don't know how they even call it different names. I think bullets are fine. Balloon, yeah. Balloon, dot, maybe dot. Okay. So that's VBR. You can get that out of the box. Let's move. This is the enterprise manager. This is as old as the wind. This is the first I did, very, very old. Similar concepts. I really liked the jobs all together. So that is nice. And I included the other tiles that are a bit smaller there, that it has to fail. That is the last status per workload, per VM. So again, that can be quite frankly, a bit crazy, but you can always filter it on the top. I'm talking that you have 1,000 VMs, you need to have a very large screen to show 1,000 VMs there. Yeah, but it can also show you which are not backed up. Yeah, yeah. It clearly shows the one that is no data is the ones that they do not have a restore point shortly. You can filter that on the top. That's the beauty. You do not need to show all of the fail success no data. You can always say, hey, show me just the fail plus no data. That's the beauty of Grafana dashboards. And again, I built this to be very visual and to put it into knock state. You can always change these queries and show them into a table, just to be more reporting wise instead of like, hey, this visual impact with everything in red. So it just depends on the use case. Yeah. OK, let's move to the next one. Oh, OK. It's OK. We cannot see clearly. This last one, maybe I play wrongly with the order. This last one, it is regarding the, we're going to see it on the next one. This one is the Vim software appliance. We cannot see the other one. The Vim software appliance, but I'm going to explain it. The Vim software appliance, it came in version 13 with no monitoring by default. You can install Vim 1 monitor, Vim 1 client, sorry, Vim 1 agent, and then you can get the CPU RAM and whatnot to Vim 1. And that's good. That's beauty. That's perfect. But you cannot monitor it with tools, right? With open source tools. So what I did is just using the Vim credentials, the Vim admin credentials, not using the host manager, just the normal Vim credentials. I created a script that you put on your software appliance that is reading with the low privilege that the Vim account has on the operating system, which is nothing. That account cannot change anything. And it cannot install anything either. So it's just a small VASL script that reads the data that it has access to, and it pulls the data to, it directly pulls the data into your InfluxDB. Non-supported whatsoever, but it was nice and very harmless, I would say, because it doesn't have any logging or whatever. It just collects the data and pushes out. And the other one that you cannot see was about XFS that I built back in the day. Let's move from this fiasco of slides. Don't make, don't call it a fiasco. Things can happen. So then we have for Vim Service Provider Console, these are very old as well as by the ID that you can see, the 9690 and the 91. That was the day that, back a few years ago, where you could take hours or days to upload dashboards. And it will still be the next because there weren't too many people uploading dashboards. But now that's impossible. You upload one dashboard, upload another one in an hour or something, and these are 200 different ones. So this is a good project. This evolved, and I'm happy that someone took it from the community, and not from my GitHub, but from the Vim Hub that we have the Grafanas there as well. Some service provider took my initial dashboards and they elevated to the next level. Let's take a look at my dashboards that they are very, you know, classic. Yeah, you see, this was very classic. This was per tenant, and it was even when it was called Vim Availability Console. This is the tenant view on the next screen. Hopefully it works. Oh, it goes back as well. Oh my goodness, what am I doing here? It's behind. Everything will be broken. It's myself. Yeah, so these were very rudimentary, but then someone took the scripts, and they expanded much better. So that example was very nice to see. Okay, let's go to the next ones. This is for 365. For 365, I created a few because this is a very, you know, great product, Vim Backup for Microsoft 365. It is a product that it does not have much visibility by default, right? We have a few reports that are out of the box in the 365. You have more visibility once you connect it to Vim One, which, by the way, it's for free and included with the Vim One license, and with the 365 license, right? Not in community, but as long as you have 365 license, Vim Backup for Microsoft 365, you can just put your Vim One, and we are going to detect, hey, you don't have anything else. No VMware, no VBR, nothing. Just Vim Backup for Microsoft 365. You open your Vim One, connect to the Vim Backup for Microsoft 365, and then there is a dashboard and reports and whatnot, right? So you can just get a few of these in Vim One. But the dashboards I created is the user audit for the restore portal, the backup health and the SLA style summary, kind of like similar to the VBR. The restore activity view, that I build it first to the Grafana and open source, and then later, as I kind of move to Vim One PM, I just took all of that work and say, guys, this dashboard is very nice. Let's make it real into Vim One. So that was good, and we productized something that it was community-based. We move it into the product, which it was nice. And the final one is about the operational dashboard. So let's take a look. It's going to happen the same, yes? But this initial view, this is for the change drift. So for this specific one, I'm doing something different. I was collecting the logs from the Vim Backup for Microsoft 365 in Windows, the logs that are on the app data folder. And I applied a few grog queries. So I was just getting things like, for example, this specific admin has created one job. This specific other admin has edited one job. This other admin has deleted one job, which shouldn't happen. But when things happen, this was the visibility. You click next. We're not going to see it, right? There's nothing there. No, there's nothing there. There's something popping up behind it, but unfortunately... Yeah, yeah. Maybe, yeah, that's okay. Then for Vim Backup for AWS, Azure, and GCP, there are three that we are protecting today, right? We are protecting the whole, protecting AWS, Azure, GCP. These products in Vim, they have a nice, comprehensive dashboard. If you log in into the appliance itself, some of this data, it's going into Vim 1 as well. But in any case, there's not a single, I don't know, eye catcher dashboard. So if you go to the next slide, probably, I think these are a bit more split into halves. So maybe we're going to see something. So at least this one. So we have Vim Backup for Azure, and all of the other two for Vim Backup for Azure and GCP, they're very similar. So what I build, it's in this case, because it's a bit more cloud and worldwide, right? That we have regions with workloads on the cloud. That's what usually happens. I'm not saying that you have the things to protect in Europe and in the US, most likely, but maybe you do. You can always zoom in. So what the map is showing is the clear regions where you have workloads at risk, right? So it's very simple to understand, hey, okay, I have something in the US, a red dot, and then from there, you can just see what is at risk, actually, with mouse over. So that is the map, playing a bit of the war games, but from back from the 80s on the movie. Then there is the protected VMs overview, which is a pie chart between what's protected and what's not protected. Very simple. The bubble job duration, and finally, yes, very reporting job historical information with the things and more inventory. The other widgets at the bottom, protected VMs and protected, that is really a catalog or an inventory of what you have protected and not protected reports and whatnot. Yeah. If you just move, I think that, okay, well, at least I did this nice. Okay. Yeah. This is the same for AWS, as I mentioned, that's the beauty that the three look very similar. And the other one, if you click, it might be Google, which is, as you can see, very, very similar. That's the beauty of they are or all that. Yeah. Okay. Let's go. AHV and Backup for Cell Phones, I'm not going to show those. They are very similar. I just wanted to show you AHV. I think I built that before when it was kind of like an individual proxy appliance and it has its own API. If I'm not mistaken, from the latest release, you do, you cannot access the AHV proxy API anymore. It's already into the VBR. So if you have something like previous releases, you can use it. If you have something new, then no. Backup for Cell Phones as well. Those ideas, you can take a look. Let's go do this move quickly to the, to the other slides. Vim1. So for Vim1, I have a few dashboards and Vim1 is a massive product, right? So, but we've been investing a lot to expose APIs. So if we go to the next, to the next slide, hopefully we can see something there. Let's see. Yeah, it's going to work. So this is very interesting. This is the same I built for the VSA, but because I wasn't convinced, I was working, you know, on the red line about, you know, being reported to HR and whatnot and to put in something on the VSA, even if I'm community, I say like, okay, well, what about if I get the data from Vim1 for the VSAs or for any other VBR? So what I built is a small, it is a small executable and a small file, you know, .exe that you run on the Vim1 and that .executable, what it's going to do is just, it's going to read the Microsoft SQL server tables from Vim1 regarding the performance metrics for the VBRs. And it's going to expose them into a Node, into a Node.js format. So you can just go into the Vim1 URL slash metrics, and then you are going to collect, you are going to see these metrics. And from once they're exported as Node.js, you can collect them easily and build this, build these nice graphs. The beauty of this is this, this is plug and play. Once again, you download this little file, this little file that is on GitHub, put it on the Vim1, that's already starting to expose data. And then with that, you collect it into, into Grafana easily. All the how-tos are in the, in the GitHub. And you can see this dashboard across VBRs, including VSAs without installing anything on the VSAs, just on the Vim1 server. The VSAs remain hardened. So yeah, you can see this. Okay, let's move next. Oh, okay. It's appearing now. Good. For the Vim1 as well, one view that I wanted as well for myself even is like, I wanted to see all of the jobs that, you know, the latest job status that is been happening. So I just build this view. So you don't need to go to Vim1. If you don't want, you can always just go here into Grafana. And again, if you're using Grafana today, sometimes it's tricky to tell to people, hey, go to Vim1 to check this. So do it the other way around. If you yourself, a customer, you have Grafana already, and you happen to have Vim1, just take that data from Vim1 and put it here. So your flow every day remains unchanged, you know, into, into Grafana. Okay. And the next final slide here, let's see. That works. Okay. And this is the same, this is the same, but for the objects. You can clearly see everything that is protected when it was the last protected date and age. The last protected date is the timestamp. But sometimes, I don't know, if I'm doing a million of stuff and looking at both slides, I see the, I see dates and I can get confused easily. So I added as well with Grafana, I added the last protected age. So it converts, it kind of like a checks the timestamp versus current time. So you can clearly see 10 months ago, two hours ago, yes, the human readable. So you don't need to think much about, okay, when it was the 9th of, you know, July, 2024, that was that Tuesday or what? So, okay. So that's the Vim1 view over there. Let's move to the next. Yeah. Yeah. The reference map. Let's move. Let's go. Let's go there. There is API reference maps. I'm going to only show, thanks, Andre. So every API that you want to dive into it, you know, we have maps for it. For example, for the Vim Backup and Replication, then we have a REST API map. REST API maps are PDFs that are visually showing to you all of all of the endpoints by category. Is this like better for observability? Is this for protected data? Is this for settings? It's very good. And I totally recommend you to navigate and bookmark this API reference maps. Yeah. Especially if you are doing things with API, those reference maps are really helping you finding the things and bits that you need. Yes. Yes. Because you can, you can see the links, you can see the colors. I mean, the API reference that we have is great because it's documented, but before you jump into the API reference, sometimes you just want to even comprehend where you're going to, you know, jump into. So take a look at the maps. We keep them up to date, every version, and I particularly like them. Okay. Some tips. Yeah. There's not many slides left. So start with someone else's dashboard. I will say I have a few. The community has been built other dashboards for Veeam, using Savic sometimes. So it just depends on what you want to do, but start with someone else. Start with Maurice, for example, for object first, if you want to see something about appliances, whatnot. Pick one product as well to start. If you have not been doing anything, just pick one. I have VBR. I'm very curious about getting XYZ, or I have 365, and I really want to see this. Just pick one product. Use variables, not hard coded values. If you use the variables on Grafana, it's going to allow you to, once again, to reuse that query and to put those variables on the top. So you can do dynamic filtering on the top, like, okay, filter by VBR name and whatnot, right? That's perhaps even a technical tip, you know, how you build this. Watch that supported flag. I showed you today a few very unsupported stuff, heavy unsupported, like putting a script in VSA. That's a no-go. Completely unsupported, even if it's harmless, as I said, completely no-go. Using private APIs, you can use them. Nothing's going to break, but that's not supported, once again, and so on and so forth. Just always watch for that. Don't reinvent the metrics. If already it's exposing the metric, you need, I mean, just fork it and clone it and then expand it, I would say, rather than try to come with a very complex query that, I mean, do whatever you want. But if the query's already there, I think I would probably say to reuse it. Don't reinvent the wheel, right? Yeah, yeah. And please share back, right? If you create nice, beautiful dashboards, just let us know on the community.vim.com. Share that with us, with all of us, so we can just, you know, all of us get benefits, as all of the dashboards I've built for years. I never expected anything back. I always put them there for people to hopefully download, but yeah, just share it. It's always nice to share. Okay, yeah, 15 community dashboards. That's the ones I built for Vim. Yeah, three downloads only for the VBR. There is many other downloads on the other one, so it combines there 5,000 or more, as I mentioned. They're covering already 10 Vim products, well, a bit more than 10, right, with the latest dashboards. So if you have a news case, someone has probably already started, so yeah, don't start from scratch. Start from the closest one. Yeah, I don't know if I have something else. What's coming today? Something very brief. I wanted to tell you that NodeExporter is coming in VBR 13.1, so we will not, in VSA, so we will not need to do anything funky to expose the metrics from VBR in 13.1. So keep your eyes open, because we will have very nice dashboard, community dashboard for 13.1, using the native NodeExporter. So yeah, we can just move from there. That's just awesome. Where to go next? Finally, all the Vim Grafana dashboards are here, not just mine. You just search by Vim, then you're going to see anything that the people have created. Help center for the REST API docs, the map for VBR, plugins, if you want to install any more plugins. Do you remember, we did a session here a few years ago with you as well, Maurice. I just put the YouTube link where we did a technical deep dive. I think that was two years ago, maybe three years ago. Yeah, yeah. I just found the link today, and I remember we had a very nice time together doing it by scratch, from scratch. And finally, visit, of course, the community. That is very vibrant, everyday, lots of conversations there. So I think these are my slides, right? You have something else to tell us, right? Yeah, well, that's for Jonah. Yeah, we have the fourth annual Vim Community Hackathon coming up in October. So if you want a chance to maybe work on a team with Jorge, or build a project like what Jorge has done, if you have some awesome idea for automation or innovation in the community, sign up for the Vim Community Hackathon. Registrations are open now through the end of September. And if you want to join, here's this nice QR code with Alfred, of course. I've created a poll for everyone, by the way, in the chat. Probably you will see it, I hope, for you to give an answer on if you're joining this year. So if you're not already signed up, just follow this QR code and sign up. And then we have our upcoming events that we are planning on doing. Oh, maybe I need to start the poll. That works. So for the upcoming events that we are doing, we'll be within the same setup as we've done the last two ones, is the one on one series and the spotlight series. Next one, we are in the one on one, we are going to get started with CI and testing. Then in July, we'll have another spotlight that's still not confirmed at this point. In August, we do another one on one with AI coding tools. And September, we do the spotlight again in October, we have the Vim Community Hackathon. So for everyone, I'm looking for responses in the polls. So please fill in the poll. And if there are no questions, I would like to say thank you very much, everyone. Thanks for joining. Maybe there will be some questions. Let's see. Let's give one minute if someone has any question. Are you guys using any of the Grafana today? Maybe you are already using it. I'm using it. That's for sure. Nice. The VBR, are you using the VBR? Well, you're using object first. Currently, mostly the 365 one. Oh, 365. Great. Yeah. Yeah. Very nice. Including ones for PG Bouncer, Postgres, and the next database. Those you created yourself, yes? No, the community created them. Community. Nice. Cool. Yeah. Like I said, there are awesome templates and dashboards already out of the box. And I only had to tweak just a minor thingy to get them working on our environment. And yeah, using the Prometheus explorators and sending it to Prometheus and then directly into our dashboard. Awesome. So. Okay. I guess no questions. No questions. Well, thank you very much, everyone, for joining today. Thank you. And until the next one. Yeah. Thank you. Bye, guys.
