Home

Jvakt is a simple reactive monitoring toolbox. It's not proactive.

It will react after or during a detected problem by the means of the console gui, console web page, mail and/or SMS.

It monitors http and https, including an optional text in the html stream and the remaining age of the https certificates.
It monitors IP ports and IP addresses. Like a FTP server, print server or anything with an open port to check.
It monitors mail servers, databases, file folders and log files using specialized monitoring programs.
It monitors an IBM AS400 servers message queues. You will probably at least monitor QSYSOPR and QSYSMSG message queses.
( Thanks to PUB400.COM for providing a great AS400 for testing! )
It monitors your Pingdom objects.

By use of the RptToJv program ( java or c# version ) you can monitor almost everything you can do from a script or program of you own, everywhere where you call the RptToJv pgm.

It's a passive system where the the "agents" and "monitors" are active and are updating the server side.

The server monitor that the agents makes a positive update during the expected interval.
Jvakt issues warnings to the console and sends SMS and Mail where appropriate.

The monitors and agents are simple command line programs configured by text files easily updated by a text editor like notepad.

Because the RptToJv.exe program is all you need to update the server. It is easily used in your scripts or anything that can execute a command line program.

The various programs are mainly started by an OS scheduler. The windows task scheduler which never has failed us so far and the linux cron scheduler also works fine.

The main goal is to keep track of the status of servers, applications, jobs and so on while in or out of office by the use of SMS and mail.

While in the office the console app will make it easy to keep track of the status.

A problem will show up in the console and maybe trigger a mail or SMS text message depending on the rules.

The Jvakt server job receives status updates from the monitors and agents. The server then updates its tables in the database.

The CheckStatus pgm is started on regular intervals by the scheduler to check the tables and trigger mails and/or SMS texts if necessary.

Monitoring jobs can be started at regular intervals to check access to resources like IP-addresses, IP-ports, mail and web servers.

Status jobs can be started at regular intervals to send status mails or SMS.

From release 2.3 the Java Compliance level is 1.8, previous releases support the Java Compiler Complience level 1.6.
Newer versions of java are working too. Java 8 is most tested and used so far.