 So, yeah. Good afternoon. Good morning. I will briefly give you an introduction about Isinga, an open source monitoring tool. My name is Bernd. I work as CEO for Isinga for over 10 years now. We are mainly based in Nuremberg, Germany and also have a lot of contributors around the world and of course users. And I try to give you a short interview about, overview about what Isinga is, what it can do, what it's capable of. And of course I'm super happy to follow up discussions afterwards if you would like to have questions into the detail. So, Isinga itself is a stack of multiple components which are responsible for different parts of our Isinga stack, which is infrastructure monitoring automation, all these different pieces which I come to the detail later on. So, we see ourselves as a monitoring platform where you can pick the pieces that you need in your environment and put them together, also with existing tools you have. So, our focus from the early days was that you can use Isinga working great together with the tools you have and not have the need to replace your metrics database or replace your, I don't know, already existing automation processes and use our tools. But again, I will show you a little bit later on in this presentation how that works and how the tools go along. So, to give you a little bit of an overview about our stack and how that works, we have some basic components which work on top of each other to get a monitoring system. So, the basic fundamental stuff is infrastructure monitoring, right, where you see your infrastructure even if it's in your data center, even if it's in the cloud or a hybrid model or different applications. That's one thing you can have a look on to. It's about the connection, so you get all these different components together and get an idea about your whole monitoring landscape. And on top of this, if you get all these monitoring information and get the data about availability, performance and everything, you get an idea of visualizing them and understand the data in the case that you can go with the user. You get all the privileges on top of it. You have your own dashboards and you get your insights and drill down your problems in re-infrastructure. And of course, on top of this is the notification components, which I don't know, send you a text message, go into your Slack or RocketChat or even call your phone and read the error message to get you alerted in some way. And of course, automate the whole process, which is the big part of Isinga, that the monitoring is a part of your life cycle you have in your data center and in infrastructure, and not going to manage your infrastructure on the left-hand side and then like open up a ticket and say, hey, please monitor, serve a virtual machine, container, whatever. So that monitoring is an integrated part of your whole infrastructure life cycle was always an important goal for us. And that's also the reason why it's on top of all the others functionality. So that's kind of the whole Isinga stack we have. And I try to break down our six competencies we saw before and give you a little bit of an idea of what it is, what is behind these competencies like analytics and modification. That you can see what we are capable of. So first thing, and this is where we come from is infrastructure monitoring, that you get everything you have in the data center in one application. So one thing is, and then let's say three main parts, of course server monitoring, which is could be bare metal, but of course it could be virtual machines or whatever kind of server hardware you have. Still even with the cloud, there are real servers out there and often like service providers use our product to monitor the infrastructure. And that's still, it's a fundamental part of your monitoring often that you have to figure out if your server monitoring is okay and the basic availability is given, which is often still the fundamental monitoring aspect. And on top of it, there's applications, whatever this is, Isinga's principle is to outsource the logic about the application to monitor itself in plugins. So the plugin knows how to monitor like a Chebos, a container, a Kubernetes, a load balancer or a database. That logic itself is in a plugin and gives Isinga the ability to use that logic and also is very flexible to use external resources. So there's a large community out there where you get also for, let's say, products which are more placed in a niche get an idea. And get a plugin for them. And network monitoring, if it comes to switches and routers and all that stuff for all the major providers, also like basic SNMP monitoring you can do, which gives kind of a holistic overview about the infrastructure itself on a level of network storage and server. An important part of that, and I told that before is the automation part. And what we see is automation are also kind of three parts. So one thing is the configuration itself, Isinga could be configured using config files, but we tend to tell users using Isinga Director, which is a web UI you can use to configure your Isinga environment. We put a lot of effort in that you can import your data. So even if you have also in hybrid cloud environment have your data at AWS or Azure, or you have like text files you have or you have an CMDB using your company, that we always try to get as many information you have out there in your infrastructure and combine them together to give an Isinga an overview about your infrastructure. You can do that using different merge rules so you can also like a transformation and loading process, use different data sources and combine them together to tell Isinga what's going on and do that in an automatic way as well. So you can use for instance PuppetDB if you use Puppet and take these resources out and put them into monitoring. So whatever resources you have, you can automatically merge them together and use them as a configuration resource for Isinga. And also do that every 10, 5, every hour, whatever amount of time you would like to do so to be in time. And of course on top of this is an API. So it's a REST API which gives you access to all the basic functionalities Isinga has, even like get the status out and query Isinga and what's going on, but also of course using the API to create new monitoring objects. So if your process needs to like add and delete and modify objects in a very volatile way all the time you can use our API and do so. That your monitoring is always up to date with the infrastructure. So whatever is your preferred way and also the website and the documentation give you way more insights how you can do and how you can merge different aspects and resources together is very, very powerful. Also have a look if that's important for you that you can write your own import providers to connect your whatever tool you have. If you don't would like to go and using a CSV expert, for instance, you can do that very easily. Cloud monitoring is of course a topic. Even our things to be honest are on the on-premise environments because this is where we are coming from. More and more companies and our customers having a hybrid strategy or at some point go full cloud and move the infrastructure to the cloud. It's an important part for us to cover that requirements here. So one thing is that of course you can go into your cloud environment and get an overview about the resources you have and get them monitored. An important part which in some way belongs to the automation competency I showed you before is the cloud synchronization. So in our configuration process and a configuration platform, which is Icinga Director, you can use your AWS or your Microsoft Azure credentials and gather your infrastructure information out of these cloud providers into the Icinga Director and use it from there on to apply monitoring rules. So imagine that you, I don't know, connect to an availability zone, for instance, to vary all the infrastructure environments you have in there. Use other data, you have merged it with the sources and enhance it and then afterwards give it to Icinga and then Icinga knows exactly what needs to be online and available in the cloud and can monitor it without any manual process required to add resources. So you are sure you can be sure that always you're up to date and synchronized with your cloud environment. So in some way that leads us to the way you can set up your hybrid monitoring wherever your infrastructure is, you can monitor it and get an overview about what's going on in the state of the infrastructure. Another thing is the metrics and logs part. That's with Icinga, if we check an application or service or a network target, we get metric information out of it. It's usually a part of that availability process that we get the performance metrics with this and can work with it. So what we do in Icinga that we provide different metric database writers where we can use our metrics we collect like every minute, second hour, whatever time intervals you to and forward the metrics to a graphite to an influx to be too elastic. So whatever favorite metrics database you have, we can send the metrics data over there and that gives you the chance to later on perhaps use Grafana or your favorite tool you would like to use to use all the metrics we collect all the time and work with them. Same happens with blocks, so we are very strong in that area of elastic, even as elastic search is used for elastic stack itself or for the open distro or for greater which is using elastic underneath. We can go with that, but of course also we can use an agent based log monitoring and look specific patterns on your firewall or whatever lock metrics would bring on. So that's a little bit up to you what way you would like to go using existing monitoring lock solutions and query the data or put your own thing above. And of course on top of that is that part with visualization. So it only makes sense if you get the basic availability more information on one hand to get that all together visualize it, create kind of a dashboard and visualize your problems and really figure out what's going on. And that part can be done in a single web with the integration of Grafana, for example, or also other tools. The analytics part which is in some way related to the metrics and locks part is important that the web interface itself has a very flexible and there's also a new filter component coming up where you can tackle down your problems. So the idea of a singer always was to in some way collect all the monitoring information we can get also move it forward to other tools you use for analytics but gives you like an umbrella understanding of your infrastructure and therefore it's important that you can work with all the data and analyze it. So one thing is you can filter them all together and root them together and combine different sources. There are add-ons like the business process add-on where you can on top of your infrastructure process and business use cases you can create some rules and say, hey, I would I would love to create like virtual resources which are just the result of other resources, which, for instance, I don't know, make sure that my e-commerce job is running and that e-commerce process itself is not like a container of machine or a cloud environment. It's just a virtual process which consists of a lot of other infrastructure parts. And I think that helps you there that you can create your own rules and get an overview about also complex setups and business process to tackle down what component is responsible for the web shop being not online, because it's, I don't know, database down there, a storage provider, or just, I don't know, a Redis database in between which is not available. So that's very powerful. And with the customization on every part in the iSinger web interface, you have the possibility to create rules and permissions and restrictions on what user or what user group can see and work with specific objects. This is also available on the on the API layer. So these kind of permissions and restrictions are there from day number one that you can filter and grant access on specific data to specific user groups. I know that not everybody needs it. So in some organizations, it's like everybody has access to every service and every metrics and every logs. Other industry work different. So if that's interesting for you and if that's a requirement, and that's definitely something you should look into. Because I think there's very strong in that area where you can finally create these rules, what users are able to see what specific environment. So we come to the to the last competency. That's the notification part. One thing which is important that you can use other data sources and import them into iSinger. So for instance, if you have your contact somewhere outside, if you have your contacts in an active directory or whatever and directory service you're using, you can import all that contacts automatically on a regular basis and use them as a monitoring contact. We have a rule based alerting so you can create notification rules. You can create escalation rules if some notification works and up does not work and and create your custom notifications and custom notification. In that point means you can create custom notifications and the content you like to send out. And of course the channels you would like to use to notify your users, your responsible service engineers and system engineers using email using pager duty or whatever tool out there. So there's the integration website on iSinger.com lists all the existing integrations we have for the major alerting and observability tools out there. And they are usually have the code snippet there which makes it very easy to integrate iSinger in an existing solution there. So how to get started. I know I told a lot about the different competencies we have there's a lot more like modules and all the time but I'm a little bit limited in time of course and also try to cover up with the agenda a little bit. So visit the website we have a get started website on iSinger.com with explains how you go forward with an installation course with components when you there's also a demo you can try out and go in there and see how iSinger Web interface does look like. In the get started you can get an idea about the packages you need to need to be installed. We get packages for all major Linux distributions of course agents for windows and so on. So everything you need also the documentation it's open source and it's there on the website you can use it. The installation course makes it should it make it clear where you have to follow which path you should move on. And of course we have a very lovely community out there which is always happy to help finding them on community dot iSinger dot com. When you have questions when you have troubles when you would like to get an idea or just would like to exchange with other users how they solve specific problems. It's a very very good point to start. Yeah, to do a recap. The goal of iSinger is that you you figure out what's going on in infrastructure so you get an overview about your components your applications your infrastructure your business process. That you are flexible that that of course we want that iSinger is an important part of the infrastructure but we always would like to make sure that. The other components you have a work very well with iSinger so using open standards integrate them even from the iSinger server side from the web. What you'll side it's easy to integrate your applications into iSinger to. To bring your data to iSinger using iSinger director is an configuration source but also using the API. That's very important for us that you as a user always are in the loop and know what's going on and hopefully tackle your monitoring judge. And that's it. Thank you for for listening. And if we have time for questions I think perhaps we have a couple of minutes. If not, of course contact me of one of these channels or using get hash on Twitter. Thank you. Yeah, thank you, Mr Bernard for the interesting sharing. So yeah we do have two questions here. So the first question is beautiful icons at the open source. Can you please repeat it I'm sorry. So this person is saying beautiful icons at the open source. We don't have any specific license created I guess but I have no problem is using I have no problem with them. Another question that is how hard is it to get a hardware report using iSinger like the ones open street map generates from chef and it is a link to the base. Where is the link and I see this. Oh, right, correct. In a second. How to hard is it to get a hardware report using a single. That's pretty easy. So, like hardware monitoring and infrastructure monitoring is one thing we saw from day one. So one thing is, depending on on the level you're asking for you can go deep on hardware using, I don't know, for instance, I PMI or redfish and really get on hardware monitoring infrastructure overview. Like, I don't know if your rate control isn't is okay or your power supplies are okay. That's possible. And also on top of that, you can use a lot of existing plugins and also the fundamental monitoring's plugin is basic you get all the details about a server. And, okay, what you're writing that's a static web page. You can use iSinger web. You can use the API to create a static web. So what you can do with iSinger you can group your service for instance together in a dashboard, export them, or you can also using the API and get a filtered query on the required objects you have and and store them in a way that you can access them using a website. I'm not 100% sure that answers your question correctly, but it's no problem.