linspector/linspector.github.io
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Imported old code.

Browse source
This commit is contained in:
Johannes Findeisen 2023-08-22 03:14:43 +02:00
commit 89d94c38b6
243 changed files with 26457 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
_posts/2013-05-27-v0.2.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: v0.2
metasub: news
---
<p>After a nice hacking session tonight, scheduling of jobs is working now! Rafael wrote some nice code to handle all the execution of jobs using the APScheduler. The next step will be processing the service command execution and parsing the results.</p>

7
_posts/2013-05-30-v0.3.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: v0.3
metasub: news
---
<p>Service command execution is working. It seems to be stable and results are as expected.</p>

7
_posts/2013-06-05-v0.4.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: v0.4
metasub: news
---
<p>We have refactored the configuration file very much today. The code is not working anymore but this is just refactoring too. It's a pain but the new configuration file is much more efficient now and it was a good decision. We will make the code running in the next days.</p>

7
_posts/2013-06-18-new-ide-for-development.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: New IDE for development
metasub: news
---
<p>We got a <a href="http://www.jetbrains.com/pycharm/" class="ext">PyCharm</a> project license today for using the IDE for Linspector development for free! Yeah, thanks to <a href="http://www.jetbrains.com/" class="ext">JetBrains</a> for that! PyCharm is a very nice IDE when doing Python development. It is fast and helpful in many ways...</p>

7
_posts/2013-06-21-services-are-working.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: Services are working
metasub: news
---
<p>Service command execution is working again. We refactored the code to use the new json configuration format. The code looks very nice now. Additionally we added a developer mailinglist. Look at the bottom of this site on how to subscribe.</p>

7
_posts/2013-09-23-v0.6.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: v0.6
metasub: news
---
<p>Linspector is working and the tcpconnect service is stable. Reporting could be done via mail. No real features yet but the core is running fine... ;)</p>

7
_posts/2013-09-26-new-website.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: New Website
metasub: news
---
<p>New website launched! \o/ Since we really would like to add more content like documentation to the website we needed a site structure. We had that not before. Now we have a clean design an structure to add content very easy. The site will be added to github soon so development could go on there.</p>

7
_posts/2013-09-30-installation-guide-added.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: Installation Guide added
metasub: news
---
<p>We added an <a href="/documentation/installation-guide/">Installation Guide</a>. Have fun!</p>

7
_posts/2013-09-30-minimal-configuration-guide-added.html Normal file
View file

@ -0,0 +1,7 @@
---
layout: post
title: Minimal Configuration Guide added
metasub: news
---
<p>We added a <a href="/documentation/minimal-configuration-guide/">Minimal Configuration Guide</a> today to make it easier to setup your first instance of Linspector. Please try Linspector and report issues!</p>

9
_posts/2013-10-09-current-code-broken.html Normal file
View file

@ -0,0 +1,9 @@
---
layout: post
title: Current Code Broken
metasub: news
---
<p>After some refactoring the current code is broken. It executes nice when setting the right environment but not without! We are making the code more Python generic so we have to learn a bit and set all things up the right way. Use commit <a href="https://github.com/linspector/linspector/commit/7ff43ff222367c8ac60a5147c11b128d7a970248" class="ext">7ff43ff222367c8ac60a5147c11b128d7a970248</a> if you want to give Linspector a try.</p>
<p>Current <a href="/documentation/installation-guide.html">Installation Guide</a> is broken too but it will be fixed ASAP!</p>

13
_posts/2013-10-11-v0.7.html Normal file
View file

@ -0,0 +1,13 @@
---
layout: post
title: v0.7
metasub: news
---
<p>Linspector got some more internal structure for Job-Handling today. Lish is able to list all scheduled jobs and all jobs have their unique ID to make handling easier.</p>
<p>Threshold-Handling has two options now. Linspector can reset to 0 on service success or decrement the threshold value.</p>
<p>Logging is still not perfect but we are closer to what we want.</p>
<p>We started writing content to <a href="https://github.com/linspector/linspector/wiki/_pages" class="ext">our Wiki at GitHub</a> so take alook there if you need more information about the configuration of Linspector. Configuration variables will be explained there more and more...</p>

9
_posts/2013-10-12-status.html Normal file
View file

@ -0,0 +1,9 @@
---
layout: post
title: Status
metasub: news
---
<p>Linspector is currently able to probe TCP and UDP ports. An implementation of a PING service is in work but we really would like to build up the core before extending Linspector with new "services". Reporting works too but only via eMail. Jabber and SMS will follow next. Storing the data is not implemented yet.</p>
<p>Take a look at the code to figure out what features are availble at the moment.</p>

11
_posts/2013-10-19-json-to-yaml.html Normal file
View file

@ -0,0 +1,11 @@
---
layout: post
title: JSON to YAML
metasub: news
---
<p>We switched the configuration from JSON to YAML today. YAML is much easier to read and write and has some more features. We will still support JSON based configuration but are focusing on YAML from now on. If some day it will be hard to maintain both file formats we will drop JSON support but for now it seems to be no problem for us.</p>
<p>An example can be found <a href="https://github.com/linspector/linspector/blob/master/examples/linspector.yaml" class="ext">here</a>.</p>
<p>Documentation will be updated soon but we want to change some config structures too so this will happen when it is done. For now everything works fine with the current docs.</p>

16
_posts/2013-10-20-v0.9-introducing-the-lish.html Normal file
View file

@ -0,0 +1,16 @@
---
layout: post
title: v0.9 - Introducing the Lish
metasub: news
---
<p>We reached a new milestone last night! Yeah!</p>
<p>Linspector got a terminal management frontend for administrators for doing maintenance tasks like enabling or disabling jobs. This frontend is called "Lish - The Linspector interactive Shell". It will become a full console to do all kind of management like configuration, restarting, reloading the Linspector instance etc. It has colored output and feels very well. If you like
working in text based terminals Linspector and its Lish is the right software for system monitoring. We recommend to give it a try! There is still a lot of work to make it usable in the real world but it is stable and useful though.</p>
<p>We will add a screencast of the Lish until tomorrow where you can see it in action here on linspector.org. Stay tuned!</p>
<p>We added a feature to Lish to view documentation like viewing man pages on a UNIX style system directly in Lish. The command is called "man" and we will add documentation there from now on. Manual pages are written in Markdown and can be <a href="https://github.com/linspector/linspector/tree/master/man" class="ext">viewed online at GitHub</a>.</p>
<p>Have fun with this new version of Linspector!</p>

9
_posts/2013-10-21-v0.10-json-rpc-backend.html Normal file
View file

@ -0,0 +1,9 @@
---
layout: post
title: v0.10 - JSON-RPC Backend
metasub: news
---
<p>We added a new important subsystem to Linspector today. Linspector now has a JSON-RPC backend for connecting to an instance from web applications, desktop applications etc. Currently you can get a list of jobs, detailed information about a single job and you can enable and disable jobs from remote. There is no authentication implemented yet but that will be easy to implement and available in our first release.</p>
<p>Lish was cleaned up a lot and output of commands got some more colors. Additionally Lish got a new command (man) for browsing documentation like man pages on UNIX operating systems. We will add documentation from time to time so this section will grow from now on.</p>

43
_posts/2013-10-21-v0.11-threading-and-benchmark.html Normal file
View file

@ -0,0 +1,43 @@
---
layout: post
title: v0.11 - Threading and Benchmark
metasub: news
---
<p>We have added a Linspector main thread today. The problem was that Linspector was started and had scheduled the Jobs and afterwards enabled the Backends and the Lish interface. Since Linspector currently schedules one Job every 3 seconds we had to wait a long time until Backends and the Lish was available to the user. Now Scheduling is done in a background thread and all interfaces are available after some few seconds. You will have access to all scheduled jobs right after starting Linspector and the list then grows in the background. That was a big improvement so we decided to set the version to 0.11.</p>
<p>We then started a small stress test using a configuration file with a lot of jobs polling many hosts to see if everythng works like expected. Below is a table showing the results. Be sure that these results are in no way reliable because they were made on hanez' notebook running severel other applications like the desktop but it really shows how powerful Linspector actually is. The configuration was using just the "tcpconnect" service with non existent hosts so the load will be much higher when polling existing hosts or more complex services like "httpget" or "snmpget".</p>
<p>The platform used was an Intel quadcore i7 @ 2.67GHz.</p>
<table>
<caption style="text-align:left;font-weight:bold;">Results:</caption>
<tr>
<td>Job Interval:</td>
<td>60 Seconds</td>
</tr>
<tr>
<td>Job Count:</td>
<td>3390</td>
</tr>
<tr>
<td>Time for Scheduling:</td>
<td>(Job Count * 3 Seconds) / 60 = 168.5 Minutes</td>
</tr>
<tr>
<td>Average System Load:</td>
<td>0.85 - 1.0</td>
</tr>
<tr>
<td>Average CPU Usage:</td>
<td>75%</td>
</tr>
<tr>
<td>Failed Job Executions:</td>
<td>Not checked! But there were some of them failing. We will debug this.</td>
</tr>
<tr>
<td>Time to get full Joblist using JSON-RPC backend:</td>
<td>1 Second</td>
</tr>
</table>

13
_posts/2014-06-27-status-update.html Normal file
View file

@ -0,0 +1,13 @@
---
layout: post
title: Status Update
metasub: news
---
<p>Linspector is not dead! I need to say that because there where no updates since about 6 month. I will explain what happend the in the past.</p>
<p>At first, Rafael left the development team some month ago. I, hanez, will go on with development! Contact me if you want to participate... ;)</p>
<p>I moved to Hamburg in the beginning of the year for work so I had a lot of stuff to do for moving and work. I arrived and are feeling home so development will go on from now on...!</p>
<p>I will post some information about the technical status of the project ASAP.</p>

11
_posts/2014-10-08-multiprocessing-support.html Normal file
View file

@ -0,0 +1,11 @@
---
layout: post
title: Multiprocessing Support
metasub: news
---
<p>Currently I am refactoring a lot of stuff since APScheduler since some months support multiprocessing for job execution.</p>
<p>Yesterday I rewrote the scheduling code but there are still some more things to do. Actually I do not know what is wrong. Scheduling works and execution of jobs is working too but the execution of services fails at some point.</p>
<p>I am on it... ;)</p>

16
_posts/2015-02-07-linspector-rewrite.html Normal file
View file

@ -0,0 +1,16 @@
---
layout: post
title: Linspector Rewrite
metasub: news
---
<p>I am working on a Linspector rewrite because of:</p>
<ul>
<li>Big design fails in the configuration parser.</li>
<li>The new APScheduler works quite different and job scheduling needs to be rewritten anyway.</li>
<li>I have designed a completely new shell interface to Linspector which is not compatible with the actual code base.</li>
<li>I want to change the license from AGPL to some BSD or MIT style license and since some code was not written by myself I do not want to replace parts so a rewrite is the best solution.</li>
</ul>
<p>Keep in mind, that it is possible to create a fully working monitoring solution with the current code base but with some limitations. That is why I do not update the current code anymore. A lot of features are missinf but could easily be implemented. For me this makes no sense because the next generation of Linspector could not adopt code because a new design. The interface to services and tasks will not change in this rewrite so these parts could be reused.</p>