Talking about Icinga and Icinga development
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Subtitle |
| |
| Title of Series | ||
| Number of Parts | 637 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/52768 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Electric currentComputer networkQuicksortPosition operatorPlug-in (computing)Degree (graph theory)Server (computing)WindowCASE <Informatik>Internet forumSoftwareCore dumpUniverse (mathematics)Point cloudVirtual machineLoginAnalytic setProduct (business)Exception handlingFunctional (mathematics)Graph (mathematics)Physical systemDifferent (Kate Ryan album)Web 2.0Similarity (geometry)Time zoneInternetworkingInterface (computing)System callComputer scienceOperator (mathematics)AreaConfiguration spaceOpen sourceBitUser interfaceOcean currentHookingHigh availabilityEnterprise architectureData centerSoftware developerIntegrated development environmentScaling (geometry)Instance (computer science)TouchscreenMereologyNumberSingle-precision floating-point formatINTEGRALRoutingWeb pagePhysical lawPoint (geometry)Mixed realityMoistureService (economics)Metric systemControl flowMultiplication signGrass (card game)View (database)Operating systemTraffic reportingGroup actionEmailJunction (traffic)Chromosomal crossoverComputer animationMeeting/Interview
08:58
Web 2.0Game controllerService (economics)Set (mathematics)Core dumpPatch (Unix)Scaling (geometry)Different (Kate Ryan album)SatelliteData centerBitWeightMaxima and minimaNumberUser interfaceScheduling (computing)System callServer (computing)Structural loadOpen sourceOffice suiteCodeINTEGRALInternet forumMultiplication signComputing platformPoint (geometry)DampingWechselseitige InformationForm (programming)Computer programmingVulnerability (computing)Online helpDemosceneMereologySoftware developerWebsiteSpeech synthesisConnected spaceRight angleString (computer science)Integrated development environmentEnterprise architectureHookingInstallation artSingle-precision floating-point formatVirtual machineComputer configurationArchaeological field surveySoftwareMappingHigh availabilityEmailComplex (psychology)InternetworkingExistenceScalabilityFront and back endsDisk read-and-write headTime zoneSoftware bugLogicLevel (video gaming)Direct numerical simulationMeeting/Interview
17:45
Water vaporGraph coloringSoftware bugCodeShared memoryCoefficient of determination1 (number)Formal languageConfiguration spaceMultiplication signComputer programmingInternet forumLattice (order)Sign (mathematics)MassType theoryEnterprise architectureRow (database)Online helpDirection (geometry)MereologyComa BerenicesModule (mathematics)Single-precision floating-point formatWeb 2.0Projective planeWebsiteProduct (business)Process (computing)Right angleResultantMathematicsSoftware developerDifferent (Kate Ryan album)Network topologyTelecommunicationMoment (mathematics)System callCASE <Informatik>Core dumpGoodness of fitDataflowInformationForestRule of inferenceIntegrated development environmentLatent heatFigurate numberVideoconferencingText editorProgramming languageData typeUser interfaceImplementationBitInternetworkingoutputMeeting/Interview
25:48
Internet forumSheaf (mathematics)Multiplication signRevision controlDirection (geometry)Moment (mathematics)BitTemplate (C++)Product (business)Goodness of fitCodeDemo (music)Parameter (computer programming)Plug-in (computing)Electronic program guideRight angleLibrary (computing)Computing platformHypermediaPoint (geometry)Figurate numberMathematicsModule (mathematics)Projective planeSoftware repositoryMereologyVulnerability (computing)Web 2.0BlogWritingInformationContext awarenessRepository (publishing)Universe (mathematics)QuicksortScalabilityBookmark (World Wide Web)SummierbarkeitForm (programming)WebsiteIntegrated development environmentComa BerenicesCondition numberScaling (geometry)System callDifferent (Kate Ryan album)Wechselseitige InformationMathematical singularityVideo gamePower (physics)Self-organizationWordMatching (graph theory)Online helpOrder (biology)Block (periodic table)Machine visionAdditionWorkstation <Musikinstrument>Meeting/Interview
33:50
Element (mathematics)Repository (publishing)Power (physics)AdditionDemo (music)BitSoftware repositoryStreaming mediaWebsiteTemplate (C++)Formal languageGoodness of fitString (computer science)Software developerMultiplication signMedical imagingGene clusterProduct (business)Data storage devicePoint (geometry)Link (knot theory)Descriptive statisticsVirtual machineModule (mathematics)SoftwareWeb 2.0Integrated development environmentDependent and independent variablesMachine visionBuildingPhysical systemService (economics)Term (mathematics)Default (computer science)MereologyScaling (geometry)Different (Kate Ryan album)Library (computing)Source codeINTEGRALConfiguration spaceBlogNormal (geometry)ECosMiniDiscEndliche ModelltheorieGraph coloringQuicksortArmTelecommunicationPerfect groupTorusComputer programmingCore dumpTouchscreenTable (information)Touch typingCondition numberOcean currentOnline chatRight angleNetwork topologyArithmetic meanGroup actionMathematicsMeeting/InterviewComputer animation
43:21
Element (mathematics)Computer animation
Transcript: English(auto-generated)
00:11
Hello everyone and welcome to FOSTM. We're really happy to bring you our talk talking about Isinga to the Network Monitoring Deaf Room.
00:22
And before we jump into it a little bit about ourselves, so my name is Foy Murek. And I'm Julian Bost. My pronouns are they, them and I'm streaming to you from the Isinga HQ. My pronouns are he, his and I am streaming from my home and we are
00:42
fancily merged together in a green screen. So I've been working with Isinga and been part of Team Isinga for roughly four and a half years now. I did my three-year traineeship as a developer with Isinga and for the past year I've sort of moved over to be more in a community and generally communicative position.
01:09
So I do talks, I supervise our community forum and I try to be in contact with everyone from our Deaf team and the community. And while we're talking about the Deaf team.
01:22
Yeah, I'm from the Isinga core team. I just recently joined this team last year, so I came straight from university where I did my computer science degree and now I work on making Isinga all nicer, better, fancier.
01:43
Okay, so the first question that we wanted to talk about is what is Isinga? When we're talking about Isinga, we're basically talking about Isinga 2 as Isinga 1 is an entirely different product. Isinga 1 is based on Nagios, so it's a fork of Nagios.
02:00
And Isinga 2, the current one that we are talking about is a complete rewrite of Isinga, so it doesn't really have anything to do with the old Nagios fork anymore, except for some similarities. So what are similarities that you can think of Julian?
02:20
So the most prominent one is probably that all the check plugins that we execute basically the same as Nagios, so the interface remained exactly the same. You can use all existing Nagios plugins you have lying around, written in the past, found somewhere on the internet. They all just continue to work with Isinga 2. Yeah, that's right. And on some operating systems, there's also the the plugin
02:44
folder is also still called Nagios plugins. Yeah, or Debian even calls the user Nagios which Isinga runs, so yeah. So Isinga basically spans over all different aspects of monitoring that one can think of. So when it comes to what you can monitor, we have the both
03:05
infrastructure and cloud monitoring, so you can basically connect your entire landscape, be it sensors or servers or yeah, anything that gives a signal basically. What are some cool nifty things that you can think of right now?
03:24
Well, in the midst of a pandemic where a toilet paper was issued, there are of course people who have monitored the availability of toilet paper in a local supermarket, so you can do everything if you can get the data. Yeah, I also recall a case of someone monitoring their potted plant with a moisture sensor in the
03:42
soil, checking whether the plant needs watering as well. So you can get pretty creative, also monitor your home automation and all that and manage it over that. Yeah, so you can monitor anything you can think of. And the next competencies that we value
04:03
are metrics, logs and analytics. So all the data that you collect is stored in logs and you can also visualize that data that you collected properly. So you can have nice graphs that show you what your infrastructure looked like in the past
04:23
and also generate SLA reports, for example, for uptimes. Do you use graphing in EuroSinger? Of course. So with Icinga you can integrate it into, for example, Grafana. So if you know Grafana, it's a fancy tool where you can build all these nice dashboards that you
04:43
may have already seen somewhere. So you can integrate into that and even integrate graphs from there back into Icinga Web 2, so our own web interface. I mean, Icinga Web 2 also has its own little graphs. I mean, it's just donut graphs in the tactical overview.
05:01
Yeah, that's the current data for historical data. You will have to use some integration, like, for example, the Grafana one or, for example, graphite is also supported. And the next competencies would be monitoring automation and notification. So you can basically automate all different areas in the monitoring from the configuration
05:30
to, yeah, checks when they're run. And you can also send out your notifications in all sorts of different ways. So via email,
05:43
you can have Icinga call you, you can have Slack notifications, PagerDuty, Telegram. There are so many integrations. I don't think there are any tools right now that I can think of that don't have an integration. And if you find something that doesn't have an integration,
06:01
you can always write it yourself. I mean, Icinga is open source and you can just hook into it and write your own stuff. So what else is there about Icinga that you can tell? So Icinga also scales very well to large environments that our enterprise customers have.
06:26
So we support large distributed environments. You can run Icinga on all your infrastructure. So we have built in clustering functionality, which allows you to both distribute checks around your data center. For example, if you have huge numbers of checks, you have to execute
06:44
for all your networking equipment and so on, but also all your servers. In case of servers, you can run Icinga directly on them. This is then called an agent setup where you use Icinga to execute the actual monitoring plugins or the old Naios plugins, if you will. And this works on both
07:05
Linux servers as well as on Windows machines. And of course, if you want to have a large cluster, you want to have it to be reliable. So we have a high availability functionality built
07:21
right in. So you can have your core nodes all be a zone with two nodes in it and then the second one will take over if the first one fails. I think that pretty much answers the question, what is Icinga and what can it do?
07:40
Pretty much. Okay, so at this part, we want to talk about our own experiences with Icinga and what kind of systems we've seen. So do you just want to explain your setup, what you run at your home?
08:02
Yeah, well, I personally don't administer my own Icinga. My partner does that. He's the own Icinga. I've got my own user where I just have some checks, checking my Minecraft server, whether it's online or not. But he has our NAS, our router, different switches that we have
08:24
in our apartment and all sorts of different servers that he has in his Icinga. Yeah, that's basically how I set up. So it's a really small one. We don't have a cluster. We don't have much going on there. It's mostly just one Icinga instance that
08:43
sends out notifications. So my setup, yeah, I tend to quite over engineer my network at home. So I have all the dynamic routing and sometimes it breaks. And so there are all lots of ping checks that just check that everything is still connected as it should.
09:01
But apart from that, of course, all the other infrastructure I run. So for example, some websites, my DNS servers and so on, all that get checked and ends up in a folder with mail notifications that I check sometimes. So it doesn't scream at you as much? No.
09:21
That's good. So you do have your own little cluster? Yeah, I have mostly one running at my home right behind me and one running on a server in a data center somewhere and they are connected and I can modify it if my home internet connection dies. Yeah. Okay. That's cool. If you can receive a notification without internet.
09:49
Okay. So here at NetWays, just as a little explanation, NetWays is a partner company of Isinga and it's also kind of, yeah, we share the same offices and they also use Isinga for
10:06
their hosting. So we can always see, like have a look at the production environment here with the developers. So yeah, there's a lot of hosting. I don't know how many machines are on Isinga. I should actually have checked that, but I don't know either. It's a lot of them.
10:27
And in the past, I've also seen other larger environments, even in the scope of a survey that I did with a bunch of colleagues. So we traveled Germany back when that was still a thing
10:43
and checked out different companies and what they do with their Isinga and they've been somewhere that have been thousands of thousands of thousands of hosts and they've all neatly visualized them in maps basically. So there's been for one, the maps module that showed
11:03
where the different data centers are in Germany. And there's also been a logistical map, a logical map basically. So you could see the connections between the data centers was really interesting and also how they use really cool schedules. So I think they have
11:25
at least 20 different time schedules for the different people that work there on call and in office. So it was really interesting to see how different companies use Isinga because there is no Isinga that looks the same. So yeah, in this part, we want to talk a little about our
11:49
strengths and weaknesses. So what would you say is our biggest strength? What can Isinga do really well? So what Isinga can do really well is scale. So it scales at large installations. We already
12:02
briefly talked about this. Huge enterprise customers are no big deal. It works if you design your cluster the same way or the appropriate way for this. But this is also possibly a challenge for a small a few nodes set up because you still have to deal with all
12:21
the distributed features which are maybe a bit complex for such small setups. So maybe you know it from yours. Yeah, I definitely do. I mean, that was kind of the issue I looked at. I was like, there are so many options. So just as a point of reference, I worked in the web team. So I didn't actually do much in the backend. I was just trying to make things look pretty.
12:42
So I was completely overwhelmed with all of the networking features and the whole cluster and scalability things. And I can imagine that's what a lot of others can see as well. So how would you explain, how should you manage a larger scale Isinga? How would you build it up?
13:07
So, well, you typically start from the core. And so you have your master zone in the center, which you will probably build as an high availability setup with two nodes in your setup. If you want to have a reliable monitoring. So and then as we're talking about a larger setup,
13:26
you probably have quite a number of satellite zones around this one to just spread the load out a and then to either schedule checks in the individual satellite zones or even perform the checks on some agents, which are then connected to the satellite zones,
13:44
just to get a bit of load of the master. But of course, for a small setup, this is way more than you actually need. So yeah, you kind of helped me prove my point there as well, because everyone who doesn't know the terminology of Isinga will probably have
14:01
noticed that this is very blown at a certain part. And people that do know something about it might have taken something from from that explanation. Hopefully. So yeah, I mean, a lot of people like me who are overwhelmed often wash up on the forum, which I think is
14:23
pretty cool. And so I would say the the community forum is also a big strength of Isinga. Like the entire forum is based around the idea that the community helps each other. So we host the platform. It's a discourse forum. And everyone can just go there, ask questions and
14:46
answer the question of others. And I think also by answering questions that other community members have asked, you learn a lot about Isinga yourself. So I scan it a lot. I check out what people do make sure that people don't bash each other's heads in. But in general, it's pretty
15:05
cool that you can help each other there. For me, the community also always shows how flexible Isinga is, what people do. Like, even if I look at the community forum, there are things, okay, I've never used this feature. Yeah. Oh, that exists. That works.
15:26
Or some fancy integration that I've never heard of. Yeah, I guess the the integration is also a big strength that we have, like in general, that there are so many integrations, and that you can just write them yourself as well as Isinga is an open source tool,
15:42
as we've mentioned before. So you can just go on GitHub and check out the code and see where you can hook in. So in a single web, for example, you can just write your own controllers that get shown in the web interface. And you can just, you know, add some stuff to the web interface of Isinga that you use. I think in the in the core, you can't actually patch
16:03
anything into the code, can you? The integrations work differently there. No, most integrations are external programs that are executed by the core. So all checks, all notifications just happen this way. Or you can, of course, integrate using the API provided by the core, which is in REST API,
16:22
with your access over HTTPS. So that's one way to integrate into Isinga too. Yeah. And I think while we're on strengths and weaknesses, I think the the open source aspect could also be seen as a weakness as we're an open source company. And we also have enterprise
16:42
customers that, yeah, pay for features. So we do custom development. If a company asks us, hey, we would like this feature and we pay you this much for your for your development time. We also have a hard time prioritizing properly because we do want to take our community at heart
17:02
and make sure that the bugs that have been reported by the community and the features that are requested by community also go into our features, our next release. So I think it's it's difficult time planning wise because we do have paying customers that want their stuff done. But we also want to, you know, honor the community. I think that's
17:24
also a different part. Yeah, sure. And often there's some overlap, like if someone from the community finds it back, of course, we don't want to have our enterprise customers find the same back. So if we can fix it before, it's always great. OK. Yeah, I think that's also a pretty good point to go over to our next question.
17:49
So the next part is how does our Isinga development work at the moment? So you're from the core team, so we're going to mostly talk about the actual Isinga to core.
18:03
So my first question to you would be what happens if a community member finds a bug? So just someone from out there finds a bug, anything that what happens? So the best thing you can do is just go to our GitHub project and open an issue there describing debug, ideally with lots of information that helps us to actually reproduce the back and
18:26
be able to fix it. So logs, configuration examples, all are happily welcome. And then we will see what we can do. Hopefully we can fix it soon. Hopefully it's not too bad.
18:44
And if you're unsure whether what you found is actually a bug or a mistake you made or just something doesn't work and you're not sure if it's broken or if you're just not figuring out how to do it correctly, you can always go to the community forum and ask like hey do you guys also have this thing and is there any single problem or is that a me problem? So
19:05
that works as well I guess. That's a lot of the questions that I see washing up on the forum is like was that me or is that broken? Happens to everyone. Yeah and a lot of the times it's not a bug but just like a typo. It's always a typo.
19:25
What if an enterprise partner requests a feature? What does happen then? So we typically receive these requests in private and we will then take a look at them, see if it fits into your singer, if you can do it in time. And yeah also we take a look at what is exactly
19:44
requested. Maybe we can generalize it a bit to make this a useful feature for even more people like so that everyone can profit from this enhancement. And yeah then it will just take the usual process like we do all our development. It will happen on GitHub where some developer will
20:06
then take on this feature request and implement it, put it into a pull request and later it will then be reviewed by other team members and hopefully it make it in some of the next releases. Okay so on the topic of releases there are different kinds of releases right? Yeah so we
20:25
of course have our major releases which bring all the fancy new features and then four but also bring some changes that might affect your configuration or something like this. So we also support the older release for some longer time. So we have minor releases there which only bring in bug fixes
20:46
which will hopefully make your environment more stable. Okay so there's the bug fix and the feature release split up basically. Yes. Okay cool. And how do you communicate with the community?
21:02
What is your external communication? What does that look like? So most happens on GitHub of course. Sometimes I also take a look at the community forum but really I spend most of my day on GitHub doing stuff there. So apart from in my text editor of course where I write code if I do.
21:25
I'm personally a lot in the forums as I'm kind of the moderator there trying to figure out what happens and when to push people to go to GitHub and when to not do that. And we also have a colleague that takes all contact requests from our website. So on IsingaCom you can also
21:45
get in contact with Isinga when you don't necessarily have anything to talk to the developers on GitHub or the forum where you are looking for help. So those would be the external channels I think. How does internal communication work? So in the Isinga Core team. So well
22:04
currently we are mostly at home so our communication takes place over the internet so we mostly have our internal chat tool and then we do video conferences using Jitsi. Every morning we just talk about what we will do and then if you want to work with someone
22:25
you just meet in a Jitsi call and maybe share your ID or yeah just do whatever you want to do which works surprisingly well and as I just recently joined the company that's I've spent most of my time working that way like I was only in the office for like two
22:42
weeks and from then I was working at home. Yeah I mean I still recall the good old times where we would just meet in a conference room like all of the developers sitting together trying to figure out what to do next and mostly just talk about nonsense for a good 10 minutes before we get started.
23:02
Yeah but yeah I can confirm there's a lot of a lot of Jitsi meetings going on. Like this one we're doing right now. Yeah actually this is also happening in a Jitsi. So in this part we want to talk about in which direction we would like to go with Isinga.
23:26
So both as a project and the product. Product would be as a user trying to use Isinga and project would be as someone who wants to develop on Isinga so both as an actual like Isinga developer but also as someone who just wants to contribute to the code base and I think you're a good person to
23:46
ask for an opinion there because you recently joined the Isinga core code base. So what are experiences? How would you describe it? Yeah so there is the developer introduction in
24:01
the documentation where it says how to get a setup for working on the Isinga code base. This all works but it's heavily based on what people did some years ago and in the meantime people have found different ways so you get all input from everywhere you can do this a bit
24:21
better so this could need some tiny updates here and there to make it just a good workflow we use nowadays but of course the old ones or what's written there still works fine but sometimes things can be easier than that so this could be improved to get started in code base.
24:43
So in general the code base has a lot of Isinga specific code in there so because we have our configuration language which basically is a programming language parts of that are throughout the whole code base and you have to get used to this first and
25:03
I think there one could improve a getting started documentation which points out what this is how it works where you can look at the code if you need to or if you see something that you don't know from Isinga C++ but you will find all kind of custom data types
25:22
from our config language over there how do these work some nice introduction would be worth doing. Yeah I mean I remember doing something on the getting started and how to code your own modules last year so web 2 is written in PHP and we have a little module for Isinga that you can
25:44
look at in the web interface that explains how to write your own module so it's kind of a self-teaching method which is kind of cool so that's out there and what I also remember from joining the Isinga web team back in 2016 was that there were actually quite a lot of
26:04
good code reviews so my mentor back then was very very very into doing good code reviews so sometimes we just sit there for two hours and discuss what I could do better and I still see a lot of code reviews in the pull requests. Yeah sure we do so all pull requests that make into
26:27
it into the Isinga code base are reviewed by someone else and often there are multiple revisions of the pull request before it gets actually merged hopefully making it all nicer work better and avoid introducing problems and yeah. Yeah as much as it felt odd to get corrected
26:46
in every single bit that I did in the in the pull request it was a really good learning experience for me like also getting better at coding in general and I think we do that both for Isinga devs and just community submitted pull requests as well. Yeah they both basically
27:05
take the same path and yeah. Yeah so that was a bit into the direction of how to make the code more approachable so the product Isinga is also in the works of getting more approachable
27:22
user-wise we also mentioned earlier in the strengths and weaknesses that the scalability makes it really complicated for you to set up your own smaller kind of Isinga environment and I feel like that's a bit of an issue with new users coming in just wanting to try it out
27:41
like seeing yeah how does this Isinga work and they can't get a simple thing to work because it's just so complex and on the new Isinga com website that we relaunched last year there's an entire new section dedicated to getting started there's a little live demo that you can look at and yeah in general we're working a lot on how to make Isinga more approachable I
28:07
think that's the main direction we're going towards. So last but not least in the spirit of the Fostum we want to tackle how can someone contribute to the project how can you
28:22
help Isinga and do something. I guess the first place to start would be the documentation because documentation is a thing that you can always improve in every project everywhere. So if you get started with Isinga you struggle at some point in the documentation
28:42
but figure it out in the end it's always welcome if you take your time to actually think a bit can I write this a bit better than it's currently explained and then you can contribute this documentation change to our documentation. So this also uses the our github workflow the
29:03
documentation is just a part of our code repository there and takes all the normal make an issue if you just want to mention it or even better make a pull request that actually improves the documentation in some way that would have helped you if you knew this before
29:20
and submit it we'll take a look at it. Documentation changes are quite easy to review so this should be done fairly quickly. So another thing we get quite often which is also a good way to start is Isinga ships with check command definitions for all
29:44
sorts of plugins that exist around the web so if you found a fancy new plugin that you are using with Isinga and you have written a check command definition for it you are also welcome to contribute that one to the Isinga template library which ships all these definitions or if
30:03
you found a missing parameter for one already existing definition this is all very easy to get started with and helps a lot of users so also a great place to start. Yeah and to like check out what there is out there as well there's the Isinga exchange so exchange.isinga.com
30:22
is a collection of plugins and modules and user written stuff it can be themes as well and you can just have a look at it it's usually linked to the github repos and you can also just look through it and see if you can modify it if you can make your own version of it
30:44
so contributing by adding new modules new check plugins new themes for Isinga web I think I will also count that as a contribution because it it just adds to the universe. Yeah and I also mentioned the the module helper
31:04
in the last section so you can check out our little tutorial on on github as well. How else can you contribute? Well if you have a favorite feature you're missing you're also
31:22
welcome to take a dive into the code base and implement it will take the same workflow as for example check command definitions or documentation fixes just do it on github send a pull request there ideally open an issue first so that we know that someone
31:41
is working on this so that we can discuss first if this makes sense for the project if we want to make it a little bit different so to make it more useful or in general so that not others also know someone who's working there so that not two people spend time doing basically the same thing. And I guess if you don't know where to get started with that the
32:01
forum would also be a good place to go because we have a lot of people that work on Isinga either at the company or from the community just being on the forum so if you have any questions on how do I code this and that how do I implement that you can also go to the forum and just ask. There will be someone who points in the right direction for that.
32:23
Most likely yeah. And I guess you could also write a blog post like both on your own platform I think it's it's also counts a contribution if you talk about Isinga on social media if you write blog posts guides tutorials and just generally spread awareness and teach other
32:44
people things so answer questions in the forum write blog posts write info articles and publish that I think that's that's also a cool way to contribute. And you can also write blog posts on the Isinga blog as well so if you use the contact form on isinga.com you can also
33:06
collaborate with me on writing a blog post there so if you want to you know spread awareness of your own self-written module or your theme that you just made you can also just get in contact with me and we can see if we write a blog post about that together. So I think that
33:27
pretty much sums it up for now looking at the time we're pretty much there so thanks for listening we'll just be over in the questions answer questions and answer section
33:41
um to chat with you about more nonsense yeah you in a moment
34:04
see previous crops actually not okay so time to go live I don't know actually when we are
34:21
online on the stream we don't know yes I think so perfect um then yeah thank you for and Julian for your talk um I think now we can answer your questions there's only uh also the
34:41
the chat room you can still uh ask your questions um the first one from Alain Ginritz um is there a demo of Isinga true or can we view on somewhere yeah um I already mentioned in the talk that we do have a demo um the link to it is rather easy to be found
35:02
it's isinga.com demo I also pasted in the chat so you can just have a look around we installed the most common modules things that you might want to have a look at and it's chat with um yeah demo data so the things that I read aren't actually broken it's just flashy so
35:21
you can see what it might look like or hopefully won't look like in your environment um blair you're responsible for the demo right yeah um so actually um we do have this this online demo um with some some default values that we provide there um you can see lots of things that
35:42
are possible with Isinga some other things that make Isinga so special um are not visible there because they are pretty hard to visualize like scaling and flexibility and different integrations and so on so the demo system that we provide um on our website is it's a very basic
36:02
demo um it's it's nice to just see how it looks like and to get a feeling about it um but still you cannot see the full power of Isinga because um in the end you will have to just use it in your own infrastructure once to just get a feeling about how what actually you
36:21
can do with it um but the demo is a good start yeah and what we yeah I think you'll see a little of how you actually configure it only how it looks in the end or can look in the end uh there yeah and maybe something else worth to mention here is that we're currently working on some docker images for Isinga um that's uh not there's no final release yet for them
36:46
but still I think it would be a good point for someone to just get started with Isinga without having to configure a fully blown machine with everything for production use um but just take a look at it um I think the the docker images we're currently building
37:05
are a good starting point for that and you can find them on github there are two repositories one for Isinga 2 and one for Isinga web and we also do have images for for the upcoming Isinga db as well so you can have a look at the the upcoming things as well all right perfect
37:29
I see there's another question in the chat um about the vision around the future of Isinga I think you're also the best one to talk about this one there
37:40
um yes of course I'm just thinking if so what I could figure out in the meantime is we do have some some blog posts about this around this topic it's difficult sometimes to actually communicate this correctly
38:01
um to do it in quick um how I would answer that is we are aiming to to build modules around Isinga that are able to monitor dedicated technologies in addition to traditional infrastructures that we are able to monitor right now so the world of Isinga 2 is something that is here to stay
38:27
of course and our idea of the whole Isinga ecosystem is to to have an ecosystem where we can add more and more monitoring capabilities to Isinga in addition to traditional infrastructures
38:44
so to be able to monitor Kubernetes systems clusters shared resources storage systems in specific so everything that that is not a host and a service um but still in a good way to to
39:01
be able to visualize everything in a correct manner and to receive alerts for the correct things of course this is like a vision that we are following for the long term it's not something that we're going to achieve within the next couple of months or the next couple of one or two years we we are working on building the foundation to be able to do these things in
39:25
the futures and yeah but basically this is the idea and I'm going to paste maybe one or two articles about this topic in the chat if you're going to stay around for a couple more minutes
39:41
i will provide that all right thank you so uh fire mike mentions he really likes the idea of official docker images um and he's also a question um it's about uh contributing new services and
40:01
command templates of own checks um where can this be done yeah i think i'll answer this so these checks are part of or check command definitions are part of the so-called isinga template link library so that's just a whole bunch of uh config templates that ship with isinga
40:21
and these are part of our normal source code repos so they are on github.com slash isinga slash isinga two that's the repository where they are all living there's the itl isinga template language subfolder in that repository and you can just fork the repository there make your additions and then send a pull request
40:43
yeah i'm also linking a few bits from our documentation that basically deal with how to contribute and where to contribute i'm currently working on an improved development guideline where we can kind of pull those strings together but for now we have those
41:02
in the documentation developer all right perfect so i think on the uh on the official live stream on uh the phostom website you can't i think you can't see the links so if you want to look at them you can just come into the chat.phostom.org live stream and
41:28
just can look at those links yeah maybe we can also add them to the talk description later on for anyone looking at recording probably makes sense all right um are there any
42:06
any more questions i think we have two more minutes or so i don't think there's anything unanswered so far so if i think if there are no more questions right now
42:40
um then again i would thank you for your talk um it was really nice really informative and well i think i will then give it up for david mckay and his talk about network monitoring with influx db2 and telegraph so again thank you and
43:06
maybe see you see you the next time yeah thanks for having us here stick around i'm gonna be in the network monitoring if anything comes up so see you on the chat yes see you