MetaMonitor
System Software
Score 82%
Description:

This simple program watches the syslog's or metalog's log file and pops up the window whenever the new message comes. You can specify the file to watch and a regular expression for parsing the log line, so you can watch other than log files too.

Now you can use themes in your popups. See MetaMonitor's homepage for the Themes Howto, a document describing how to create your own themes. Please send me your themes or publish them on KDE Look (in the 'Other theme/style' category).

Thanks to Konstantin Sobolev and his KLogView for inspiration and a few lines of code ;)

See MetaMonitor's homepage for more information.

See README file for source installation instructions.
Last changelog:

11 years ago

0.4.5a:
+ Added Debian "unstable" package (for KDE 3.4.3) (Jérí´me Viscaino)

0.4.5:
+ Added spanish translation (Alejandro Araiza Alvarado)
* Updated other translations files
+ Added themes support (can set the skin, text colors and body layout with the qt richtext)
* Command's button -> Command's anchor
* Complete rebuild of the configuration window
* Fixed popup's positioning. Now it's sensitive on the tray's position and doesn't hide kicker
* Fixed keyboard shortcuts in the advanced config (thanks Florian)
* Changed the text in About-Window to a little less stupid ;)
+ Added ability to clear the log window
* Updated AUTHORS file

kyromaster

11 years ago

I send a bugreport about the permissions issue for /var/log/messages to novell:

https://bugzilla.novell.com/show_bug.cgi?id=134541

the suggestion thex did with /dev/xmessages crashes my KDE if I enter it in metamonitor. It would be great if this would be possible in the next version :)

Report

xis

11 years ago

Well, guys of Novell said you should attach MM to /dev/xconsole, not to /dev/xmessages. If there's problem with reading a pipe (it is not a 'normal' file, but should also work) then you can reconfigure syslog-ng. It can send it's messages to a pipe AND also to the file (see sample syslog-ng file which comes with the package).
However, the xconsole messages are NOT all the messages you would like to see. There will only be messages which are 'safe', that means, syslog-ng won't send the trusted messages there (such as user password changes and so on).

MetaMonitor is an administration tool, it is designed to watch log files and not to care about permission. So I can't guarantee that you will be able to see all the logs. :(

You may want to see last comments in this site, there are some tricks which should help you.
Good luck.

Report

gohanz

11 years ago

A SlackWare 10.2 TGZ Package with SlackBuild script is ready to download!!

http://www.slacky.it


http://www.slacky.it/index.php?option=com_remository&Itemid=1&func=fileinfo&filecatid=760&parent=category

Report

gohanz

11 years ago

A SlackWare 10.2 TGZ Package with SlackBuild script is ready to download!!

http://www.slacky.it


http://www.slacky.it/index.php?option=com_remository&Itemid=1&func=fileinfo&filecatid=760&parent=category

Report

kyromaster

11 years ago

Thank you very much for your help :)
I´ll try what you suggested.

Report

kyromaster

11 years ago

I get an error about MM unable to open /var/log/messages because it has the permissions -rw-r-----.
I´m using SuSE 10.0, can I just change the permissions of is this file deleted and recreated often?

Report

xis

11 years ago

I described this problem in the README file. I think that the best way to set the correct permission is to do:
rw-r----- root admin messages
I mean setting the file owner to 'root' and group to 'admin'. Then make trusted users members of this group (after that the users must logout + login again to work).

However, syslog resets file permission with every restart, so you have to make a way to change this situation. I am not sure but I think there aren't any configuration options responsible for this. In this case one of ways is to edit syslog's init script (/etc/init.d/syslog) and add the following lines to the end of start procedure's body:
chgrp admin /var/log/messages
chmod g+r /var/log/messages

Of course there are other ways such as adding these lines to cron or reconfigure you logrotate daemon (if you use any) and so on... I'm not a Syslog expert so I can't help you more.

Good luck

Report

calr0x

11 years ago

REALLY like this man, thx alot for the work you've put in it. I hope to see it maintained a long time.. :)

I REGISTERED just to tell ya! heh

Report

xis

11 years ago

Wow, I find it as a compliment :) Thanks!

Report

murphy666

11 years ago

Really nice app, I didn't need to have "tail -f ..." anymore!

The previous version was a little annoying but now with triggers tha's so perfect!

This software should definitely be part of KDE.

thanks!

Report

xis

11 years ago

Thank you for your opinion. Comments like this are great motivation to maintain this project :)

About MM as a part of KDE... Well, I'm not sure if it's mature enough yet. Maybe in the future KDE developers will be interested of it. I want to make MM a tool similar to Mac's growl http://growl.info - it is an agent between user and applications. I want to put into MM a mechanism of dcop monitors - this should give you the ability to ask any KDE app for it's state. For example MM asks KMail if there are new mails every second (an popup message with button if there is some new stuff), or MM asks for RSS feeds or MM asks amaroK if there's new song... and so on and so on ;)

Cheers

Report

linux3114a

11 years ago

on SuSE 9.3 with KDE3.4.3

joins the log :

WARNING: `automake-1.6' is missing on your system. You should only need it if
you modified `Makefile.am', `acinclude.m4' or `configure.in'.
You might want to install the `Automake' and `Perl' packages.
Grab them from any GNU archive site.
make[1]: Entering directory `/usr/src/packages/BUILD/metamonitor-0.4beta1'
cd . && perl admin/am_edit -padmin Makefile.in
configure.in:39: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:44: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:47: error: possibly undefined macro: AC_CHECK_COMPILERS
configure.in:48: error: possibly undefined macro: AC_ENABLE_SHARED
configure.in:49: error: possibly undefined macro: AC_ENABLE_STATIC
configure.in:54: error: possibly undefined macro: AM_KDE_WITH_NLS
configure.in:57: error: possibly undefined macro: AC_PATH_KDE
configure.in:62: error: possibly undefined macro: AC_CHECK_KDEMAXPATHLEN
make[1]: *** [configure] Erreur 1
make[1]: Leaving directory `/usr/src/packages/BUILD/metamonitor-0.4beta1'


RPM build errors:
make: *** [configure] Erreur 2
error: Bad exit status from /var/tmp/rpm-tmp.26213 (%build)
Bad exit status from /var/tmp/rpm-tmp.26213 (%build)

Report

xis

11 years ago

This is because you don't have automake-1.6 installed (you probably have the 1.9 version). I know that there is a problem with that on Suse. I'll try to disable automake version checking (hope it will work) when the official 0.4 version will be released.

Report

dzamboun

11 years ago

I like last version, and this more better. I like it very much! Triggers are very good idea, it will be fine if program have some default triggers.

Report

xis

11 years ago

I'm very glad you like it :)
I thought about default triggers but I didn't have an idea about what should be by default, so I decided to not do any.
I also plan to make 0.5 release be plugin based (every plugin will have it's own triggers group) and then I'll make two default plugins: Metalog' log file and Syslog' log file (then I'll try to make few default triggers such as for warnings and errors - maybe you have some ideas?). You will be also able to monitor more than one file, and not only files (also commands outputs and dcop commands).
How about that?

Report

smart2128

11 years ago

I placed the ebuild in /usr/local/portage/app-admin/metamonitor and when i run "ebuild metamonitor-0.4beta1.ebuild digest" I receive:
!!! Name error in 0.4beta1
!!! Error: PF is null 'metamonitor-0.4beta1'; exiting.

The problem is the filename structure:
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1#doc_chap2
If i change it in metamonitor-0.4_beta1.ebuild I solve this problem but then the ebuild can't find the source file on SRC_URI=ftp://... , of course.
Can you check this problem?

Thanks.

Report

xis

11 years ago

Yes, It is fixed now and should work :)

Report

smart2128

11 years ago

Yes, now it works. :)
Thanks.

Report

arti

11 years ago

Hi xis,

could you please implement a horizontal scrollbar in the message window? Some of the kernel messages are longer than what my display shows at 1024x768 and I can just read the beginning of the message. Besides from that, I like your app! :-)

Regards
arti

Report

xis

11 years ago

Hi,
I've just added it to my TODO list, so it should be done in official 0.4 release :)

Report

DexterMagnific

11 years ago

There is a missing feature : when a new message is added to an existing popup, the timer is not reset.
So the popup may disappear immediately after new messages arrived.

This is the fault of KPassivePopup that doesn't implement this feature.

One other thing : have you tried your app with XCompMgr activated ? when messages are removed from there are trails of the old popup

sorry for my english

Report

xis

11 years ago

Hi,
It was intentional to let every message to live its own time. When the message's lifetime ends it dissapears regardless of other messages, and if there's no messages in the popup, then the whole popup is being hidden (this is because it is not a popup who has timer, but a single message). I think I can add an option to reset the other messages' timers whenever the new message pops up, there is no problem to do that I think.
Thanks for that tip.

About the XCompMgr, I did't know that (I don't use this feature often). I'll try to check it out and maybe find a way to destroy this bug :)
Thanks once again.

Regards

Report

Enso

11 years ago

Great app! The only think it's really missing is a filter on messages... for example i've got the firewall on and it shows me Inbound IN=etc.. messages all the time. I wish it to not show those messages..

Report

xis

11 years ago

Hi,
This feature will be implemented in next (0.4) release. You will be able to block any popups you want. And many more! :)

Report

Shelton

11 years ago

I am on Mandrake 10.1 and when I run it I get a message in a window saying

Cannot open a file

var/log/everything/current

No such file or directory



Regards
Shelton.

Report

11 years ago

0.4.5a:
+ Added Debian "unstable" package (for KDE 3.4.3) (Jérí´me Viscaino)

0.4.5:
+ Added spanish translation (Alejandro Araiza Alvarado)
* Updated other translations files
+ Added themes support (can set the skin, text colors and body layout with the qt richtext)
* Command's button -> Command's anchor
* Complete rebuild of the configuration window
* Fixed popup's positioning. Now it's sensitive on the tray's position and doesn't hide kicker
* Fixed keyboard shortcuts in the advanced config (thanks Florian)
* Changed the text in About-Window to a little less stupid ;)
+ Added ability to clear the log window
* Updated AUTHORS file

product-maker 61 304

File (click to download) Version Description Filetype Packagetype License Downloads Date Filesize OCS-Install DL
Details
version
0.4.5
updated Dec 21 2005
added Oct 24 2005
downloads today
0
page views today 1