You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(11) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ben C. <bcl...@pe...> - 2005-02-15 17:23:01
|
Dear users, A casual release with no new features. Containing fixes to allow total deletion of hosts to work, and several develop bits. Regards, Ben. |
From: Ben C. <bcl...@pe...> - 2005-02-02 16:19:56
|
New version, 0.105.3 New feature: Report of Raw Data Summary. This stores a history of all plugin states. These are stored by the day, and may be quickly reviewed to identify accurate uptime for a large time period for each service. This contains some bug fixes to CGI code for displaying stored graphs and displaying raw data reports. This code should now work. Also fixed is a compilation error for PostgreSQL support. The support for PostgreSQL is still new, please report any problems which this system so that we can fix them fast. Regards, PerfParse Development Team. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2005-01-25 09:11:05
|
Latest version 0.105.2 is delayed due to sourceforge errors. Please try again later to download this excellent release. Ben. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2005-01-25 08:32:25
|
New version 0.105.2 Dear PerfParse Users, We are delighted to release the next version of PerfParse. This version is the first official release containing Friedrich Priewasser's PostgreSQL module. This allows users to choose between MySQL or PostgreSQL for the database component of PerfParse. We have produced a small chart to show you the abilities of each database: http://wiki.perfparse.org/tiki-view_faq.php?faqId=5#q23 To use PostgreSQL simply add to configure: --with-db=postgresql This release also contains fixes to problem reported by users to mailing list. Please report all problems. Regards, PerfParse developers. -- Please visit polls and tell us what you use http://wiki.perfparse.org/tiki-old_polls.php PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2005-01-24 10:55:57
|
You may complete this your self from the URI: http://sourceforge.net/mail/?group_id=109355 Regards, Ben :) dew...@fr... wrote: > > hello, > > is it possible to add me to these mailing lists please? > > thank you > > rémi dewynter > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Perfparse-devel mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel > -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: <dew...@fr...> - 2005-01-24 10:41:16
|
hello, is it possible to add me to these mailing lists please? thank you r=E9mi dewynter |
From: Cook, G. <GW...@ma...> - 2005-01-18 17:16:21
|
Thank you Ben for the kind words. While I was initially able to contribute quite a bit to the = documentation of PP, I have fallen back from the project over the past = few months. This is due to many things, such as moving my office to a = new location, moving my family to a new home, holidays, snowboarding = season, and most recently family issues that require cross country = travel in the next few weeks and quite possibly searching for a new = position outside of my current organization. Additionally, my Nagios/MRTG server was just not beefy enough to also = handle the MySQL DB, so I have not even used some of the newer versions = of PP. At this time I have acquired a new server specifically for MySQL, = and hope to lend a hand to developers again in the future. When? I'm = still not sure, but hopefully sooner rather than later. One thing that I would like to see is the addition of RRD storage of = metrics. I'm not even sure if the current development track will allow = for this, but I intend to investigate this if someone else does not. = Perhaps some folks can add their thoughts on this issue... Thanks to everyone that Ben has mentioned below. I'm sure that when I = get back to work with PP it will be all the more impressive than it was = a few months ago. Many thanks are also due to Yves, who has contributed quite a bit to = make PP the project that it is today. I'm sorry to see that you will not = be able to contribute as much in the future, although it sounds like you = will not fall back completely as I have at this point. Garry W. Cook, CCNA Network Infrastructure Manager MACTEC, Inc. - http://www.mactec.com/ 303.273.5050 (Office) - 720.220.1862 (Mobile) per...@li... wrote: > Dear PerfParse users and developers, >=20 > There are quite a few people working on various parts of the project > today. I think it's time we all introduced our selves, and said a > little about where we would like to take our project. >=20 > To help this, I'll like people who have been involved > recently. I hope > some of you may reply to this and let us know a little more > about your > current activity. >=20 > Starting with our two newest members: >=20 > Benoit and Guillaume. >=20 > They will be working to bring PP to Debian. If they are on these > mailing lists, maybe they can say a little more. >=20 >=20 > Now our oldest members: >=20 > Ben, Garry, Yves. >=20 > My self, I started this project in order to answer a posting on the > nagios-plugin mailing list, around May 2003. The entire project was > then just one line of code. Something like: >=20 > tail -f serviceperf.log | awk | mysql >=20 > I then wrote PP as a demo and for my personal use. This very soon > became PerfParse with the encouragement of many users. >=20 > Garry joined and turned my attempt at a web site into the professional > looking site we now have. He also provides some great documentation. > I am sure most of our users found PP through Garry's documents. I > thank him that the projects early success. >=20 > Yves re-wrote a lot of the code, as well as building the > product into a > GNU automake environment, internationalizing the code, and > making the > code more modular. Without his help the product I am sure > would have > never developed into anything like it's current state. His > needs and > my needs are different, which gives the project the ability > to answer to > many users needs. >=20 > Other members: >=20 > Flo Gleixner. >=20 > Flo described him self as a 'slow coder'. From his workings > so far on > tiki/wiki and perfparse, this can be his only short falling. > His work > is as good as the best coder you are likely to meet. Flo is > working on > a php front end for PerfParse, using similar methods as tiki/wiki. A > suggested goal to merge Nagios PP into a wiki type product, giving to > the user the ability and advantages of all systems. >=20 > Rene Grabner. >=20 > Rene is working to translate the documents into German. >=20 > Tim Wuyts. >=20 > Tim has contributed many ideas, as well as some scripts to > the product. > Most recently he has given us the Raw Data Summary storage. > This will > greatly enhance the product. >=20 > Friedrich Priewasser >=20 > Friedrich is working on a conversion to PostgreSQL, which should be > released sometime very soon. I am sure this will open > PerfParse to many > new users. >=20 > Massimiliano Minniti >=20 > Massimiliano is looking into a conversion to Oracle storage. >=20 > Carsten Franke >=20 > Translation of PerfParse into German. >=20 > Jeff Scott >=20 > Who kindly donated domains including perfparse.org. >=20 > Thanks as well to all the other members who have contributed time, > testing, ideas and code to the project. Including in no order: >=20 > Charles Allred, Chris Donovan, Dirk Beer, Ethan Galstad, James > Greenhalgh, James Ochs, Jon Lyons, Julian Touche, Darren Kemp, > Krzemi=F1ski Krzysztof, Marcos & Marcelo, Norbert Wiedeke, > Philipp Sand, > Sebastien Guilbaud and Ton Voon. >=20 > My personal thanks to you all. >=20 > Regards, Ben. |
From: Ben C. <bcl...@pe...> - 2005-01-18 10:13:34
|
Dear PerfParse users and developers, There are quite a few people working on various parts of the project today. I think it's time we all introduced our selves, and said a little about where we would like to take our project. To help this, I'll like people who have been involved recently. I hope some of you may reply to this and let us know a little more about your current activity. Starting with our two newest members: Benoit and Guillaume. They will be working to bring PP to Debian. If they are on these mailing lists, maybe they can say a little more. Now our oldest members: Ben, Garry, Yves. My self, I started this project in order to answer a posting on the nagios-plugin mailing list, around May 2003. The entire project was then just one line of code. Something like: tail -f serviceperf.log | awk | mysql I then wrote PP as a demo and for my personal use. This very soon became PerfParse with the encouragement of many users. Garry joined and turned my attempt at a web site into the professional looking site we now have. He also provides some great documentation. I am sure most of our users found PP through Garry's documents. I thank him that the projects early success. Yves re-wrote a lot of the code, as well as building the product into a GNU automake environment, internationalizing the code, and making the code more modular. Without his help the product I am sure would have never developed into anything like it's current state. His needs and my needs are different, which gives the project the ability to answer to many users needs. Other members: Flo Gleixner. Flo described him self as a 'slow coder'. From his workings so far on tiki/wiki and perfparse, this can be his only short falling. His work is as good as the best coder you are likely to meet. Flo is working on a php front end for PerfParse, using similar methods as tiki/wiki. A suggested goal to merge Nagios PP into a wiki type product, giving to the user the ability and advantages of all systems. Rene Grabner. Rene is working to translate the documents into German. Tim Wuyts. Tim has contributed many ideas, as well as some scripts to the product. Most recently he has given us the Raw Data Summary storage. This will greatly enhance the product. Friedrich Priewasser Friedrich is working on a conversion to PostgreSQL, which should be released sometime very soon. I am sure this will open PerfParse to many new users. Massimiliano Minniti Massimiliano is looking into a conversion to Oracle storage. Carsten Franke Translation of PerfParse into German. Jeff Scott Who kindly donated domains including perfparse.org. Thanks as well to all the other members who have contributed time, testing, ideas and code to the project. Including in no order: Charles Allred, Chris Donovan, Dirk Beer, Ethan Galstad, James Greenhalgh, James Ochs, Jon Lyons, Julian Touche, Darren Kemp, Krzemiński Krzysztof, Marcos & Marcelo, Norbert Wiedeke, Philipp Sand, Sebastien Guilbaud and Ton Voon. My personal thanks to you all. Regards, Ben. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2005-01-17 20:54:51
|
New version 0.104.9 released. This version contains Summary Data for Raw Nagios Plugin outputs. Kindly provided by Tim Wuyts. This collates a statistical daily summary of the state of plugins for each day. Currently this data is collected only. The Changelog is shown below: Addition of raw summary tables (TW) Minor mistake in db version in a user message in check_perfparse_version (YM) Fixed 2 bugs on the pipe of perfparsed (noticed by Thomas Eriksson and TW) (YM and TW) |
From: Yves <yme...@pe...> - 2005-01-11 10:37:09
|
> New version 0.104.8. > > Includes compilation fixes missed by last version. No new features. Well, I would like to add that there is a minor feature for power users. = I forgot to send this to Ben before he release 0.104.8, so here it is : You can now compile perfparse with no database support: ./configure --with-db=3Dnone Today, only power users should try this because with no database support,= the only thing you can do is to use the file_output storage module in perfparsed, and perfparse-log2gnuplot to generate gnuplot graphs. You also need some basi= c knowledge of gnuplot to use it. Perfparse is not supposed to drop database support. This feature is only = the beginning of an answer to all those who want graphs and can't/don't want to use a d= atabase. Development is needed to make this feature friendly, and contributions ar= e welcome. Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://perfparse.sf.net/ - |
From: Ben C. <bcl...@pe...> - 2005-01-10 22:31:39
|
New version 0.104.8. Includes compilation fixes missed by last version. No new features. Ben / Yves. --- Changelog: Fixes and compilation changes missed from 0.107.7 (YM) Another attempt at fix on perfgraph.c to stop cgi |
From: Ben C. <be...@cl...> - 2005-01-09 16:37:10
|
Dear Users. We are delighted to release next version, 0.104.7. This contains mostly fixes. Including the CGI 'Error 500' to which some of you have reported. A fix to a compilation bug on Solaris and a runtime bug for those who were already using any perfparse-log2* executable reading from a socket connected to perfparsed. Full Changelog is shown at end of posting. -- Please report any problems back to us, we will endeavour to fix your problems before adding new features :) -- An important new feature, explained by Yves: With perfparse-0.104.7 comes a very exciting feature : the new storage module for gnuplot allows you to easily make csv data files that gnuplot understands. With this module, you will be able to make multi-line graphs. Many were dreaming of such a feature! You only need to run perfparsed with the file_output storage module enabled. However, that module is a quick hack to show what perfparse can do with gnuplot and without database support. There are a lot of things to improve here, like for example to run gnuplot from the module instead of you running interactively. If you want to help, the gnuplot module is 150 lines of code only (without the comments). Last thing: nothing is documented on this feature. Yves will try to write things, but there is a lot to do in the documentation. If you think you can help, please drop us a mail ! This option will be available for users using MySQL in the near future. There will be some discussion in the future about whether to use the excellent GnuPlot tool as an extra, or even replacement, for the current graph drawing code. If you have an opinion on this tool, please let us know your feelings. -- Finally a new tool, which at the moment installs into the 'bin' directory: check_perfparse_version This will check your perfparse database version is correct, in Nagios plugin format. Although this version only changes on new installations, forgetting to run the 'upgrade' may result in permanent loss of data. Therefore this is a fail-safe check mechanism. You may consider embedding this as an hourly check in Nagios. -- Changelog: Version 0.104.7 New gnuplot storage module. (YM) Compilation bug fix on solaris platforms (LC_NUMERIC) (YM) Fix to CGI variable bug causing some compilations to crash. (BC) Bug fix for all perfparse-log2* that read from a socket to perfparsed (YM) Addition of Nagios plugin: check_perfparse_verstion. (BC) Fix for CGI code where HTTP server sends environment variables as parameter to code. (BC) Other fix to CGI variable interrogation code which may cause failure on some systems. (BC) Dropping of perfparse_deamon.sh script. -- Regards, Ben & Yves. |
From: Ben C. <bcl...@pe...> - 2005-01-04 17:09:01
|
New version :- 0.104.6 We are happy to announce the first new version for the new year. This contains mostly fixes with a few new features. Note 1 :- A database upgrade must be completed for this version. After installing, please enter: perfparse-db-tools --upgrade Note 2 :- Slight directory restructure. perfparse.sh.example, mysql_create.sql and mysql_delete.sql are in directory scripts. Please draw our attention to any bad documentation. Note 3 :- Previous version 0.104.4 was released too soon. Version 0.104.5 was not announced. This posting therefore covers all three versions. ------------------------------------- Notes on new features in Versions: ------------------------------------- Summary data is now collected. Unfortunately this is not currently used. In the future this will offer an alternate graph allowing the display of very large time scale plots. This may be defined from the Administration Menu. In order to see and edit these options, you will require a new option in your perfparse.cfg file. See last line of this section: # Default user permissions in the CGI. Accepted values are (ro|rw|hide) Default_user_permissions_Policy = "rw" Default_user_permissions_Host_groups = "rw" Default_user_permissions_Summary = "rw" ("rw" is default if no entry is supplied.) Or copy over the given perfparse.cfg.example. ------------------------------------- 'Group' name is now remembered when using the cgi interface. This should make the product nicer to use. Other user options are also remembered. Currently the data storage is keyed by the login name where standard http authentication is used. This is the start of many user settings. Including those asked for on mailing list in the past. Please let us know what user specific options you would like to see. ------------------------------------- The 'Raw Report' may now be filtered by 'state'. This screen will also automatically refresh. Effectively giving an alternate front end to Nagios, if you are interested in only the current state of the plugins. Our version is however a little faster. :) More work will be completed on this screen. Please let us know what you want to see. ------------------------------------- There is a flag respected by all Database programs: --no_transactions This disables MySQL's ability to use transactions. Although we advised not to use this, some users with older database versions do require this. ------------------------------------- You may check you config file or version number by appending variables to the CGI code. Eg: http://localhost/cgi-bin/perfparse.cgi?show_version=1 http://localhost/cgi-bin/perfparse.cgi?show_config=1 This will show just these details in text only. ------------------------------------- Changelog 0.104.4 -> 0.104.6 - New periodic cleanup procedures : remove/compress log files (error log, drop files) (YM) - New storage module function for periodic cleanup procedures (YM) - Storage module file_output removes/compress its log files (YM) - Fix on graph title display. (BC) - Renamed perfparse-log2db to perfparse-log2mysql in perfparse.sh - Addition to perfparse.cgi of special CGI variables: 'show_config=1' and 'version=1' which mirror command program functions. Eg, perfparse.cgi?show_config=1 (BC) - New '--no_transactions' flag to disable database transaction model. Used with perfparse-log2mysql. (BC) - Added Refresh Time flag to graphs so that stored graphs refresh. (BC) - Major bug fixed in periodic cleanup procedure (bug due to too early release by mistake) (YM) - New storage module status file for watchdogs for modules and perfparsed (YM) - New unique integer fields on the hosts, services and metrics. (BC) - Slight change to the dbms interface. (BC) - Drop of the unused summary tables, to be replaced at later version by correct formats. (BC) - Show the number of log lines in reports, with a warning. (BC) - Improve conversion so that users know error has occurred. (BC) - Added no_transaction flag to purge code. (BC) - Floating point numbers locale safe. (Version error, setting to 0.00) (BC) - Ability to define binary summary data. (BC) - Collection of the binary summary data. (BC) - Addition and use of the 'user' object for storing user details. (BC) - Addition of filters and auto-refresh on the raw data report. (BC) - Change to default Storage_Modules_Status_File to "storage_modules.status" (YM) - Location of nagios.pid is moved from perfparse.cfg to perfparse.sh (BC/YM) ------------------------------------- Please enjoy using and report any bugs back to the mailing lists. Regards, Ben Clewett / Yves Mettier. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2004-12-20 13:03:29
|
Further note on version 0.104.4 Please Read! If you use the perfparsed part of PerfParse, used for instance for the Pipe method: Please DO NOT use 0.104.4. Please wait for next version. Regards, Ben. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2004-12-20 08:36:13
|
New version released, 0.104.4. This contains mostly enhancements with some new features: - New periodic cleanup procedures : remove/compress log files (error log, drop files) - New storage module function for periodic cleanup procedures. - Storage module file_output removes/compress its log files. - Fix of graph title display. - Renamed perfparse-log2db to perfparse-log2mysql in perfparse.sh - Addition to perfparse.cgi of special CGI variables: 'show_config=1' and 'version=1' which mirror command program functions. Eg, perfparse.cgi?show_config=1 - New '--no_transactions' flag to disable database transaction model. Used with perfparse-log2mysql. - Added Refresh Time flag to graphs so that stored graphs refresh automatically. Regards, Yves and Ben. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2004-12-16 09:10:58
|
Dear Users, New user polls are available on our interactive support site: http://wiki.perfparse.org/. These polls will give feedback to the developers of PerfParse about what options and features matter to users, and therefore where future programming efforts should be made. As well as offering a good location for honest discussion on the product and any other issues. Regards, Ben -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <bcl...@pe...> - 2004-12-08 17:23:08
|
Dear users, Perfparse 0.104.3 has been released. Thanks to Yves for coding and user for informing us of problems with previous version. This version has no new features. Please enjoy, Regards, PerfParse Development Team -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <Ben...@ro...> - 2004-12-08 17:22:58
|
Dear users, Perfparse 0.104.3 has been released. Thanks to Yves for coding and user for informing us of problems with previous version. This version has no new features. Please enjoy, Regards, PerfParse Development Team |
From: Ben C. <bcl...@pe...> - 2004-12-08 17:11:43
|
Dear PerfParse users, On our excellent support site wiki.perfparse.org you will now find two sister forums, Help and Announce. These will will offer an alternate source of information for user wishing to use a pure HTML interface to problems. Many thanks to Flo for donating this site to us all. Please enjoy! Regards, Ben. -- Ben Clewett bcl...@pe... PerfParse http://www.perfparse.org PP FAQ http://wiki.perfparse.org/tiki-list_faqs.php |
From: Ben C. <BCl...@pe...> - 2004-12-03 16:25:09
|
Dear PerfParse Users: I am delighted to announce the launch of a tiki/wiki site donated from our latest PP developer, Flo Gleixner. Seen from our new domain kindly donated by Jeff Scott: http://wiki.perfparse.com This site offers editable documentation and will be used for an FAQ and development documents to start with. The format and use of this site is entirely up to us, so please enjoy. If you are new to the site, please leave us a comment :) Regards, PP Development Team. |
From: Ben C. <BCl...@pe...> - 2004-12-03 16:17:32
|
Dear Perfparse users, We have a new version, 0.104.2. This is mainly a bug fix. However Perfparsed users should upgrade as soon as possible. Main changes: - Many thanks to Tim Wuyts, a problem on CPU usage was fixed in perfparsed - New German translation (Carsten Franke) - Minor compilation bug fixed Full Changelog an be seen here: http://perfparse.sourceforge.net/changelog.php Sorry if this site appears slow today. Please enjoy this product and report any problems to us. Regards, PP Development Team |
From: Ben C. <BCl...@pe...> - 2004-11-29 11:02:07
|
Dear users, We are happy to release the next version 0.104.1. This has many interesting additions: - dynamic libraries for perfparse-log2* and perfparsed - perfparse-log2any can load more than one storage module; the other perfparse-log2* are links, shortcuts to perfparse-log2any with one module only. - Perfparse is now internationalized, with a first French translation to be improved and others to be done (contributions welcome) - perfgraph.cgi renamed as perfparse.cgi. To avoid confusions, upgrades should remove their old perfparse.cgi. I will repeat the last change: perfgraph.cgi is now renamed to perfparse.cgi. Please delete perfgraph.cgi and change your links. Contributions will be particularly appreciated on: - translations (including improving the French one) - helping Garry on the documentation - porting perfparse on other systems than GNU/Linux and Solaris - making storage modules for other databases or RRD files Regards, PP Development team. |
From: Ben C. <BCl...@pe...> - 2004-11-18 09:23:44
|
Dear Users, New version 0.103.2. This is mainly a bug fix for the following problems. If these problems are still unfixed, please let us know. 1. Compilation problems with libXpm.so sorted for Philipp. 2. printf format for BSD fixed for Julian. Please let me know if this is any better. 3. Fixed bug in tool to reset deletion policies: perfparse-db-tools --reset-host-delete-policy This now correctly accept a host name. Therefore you can use this to reset the deletion policies of all data for a named host. For example: $ perfparse-db-tools --reset-host-delete-policy h% Will reset all data from hosts which start with 'h'. The deletion policy will be set to the binary and raw default. Please check what this is before using. 4. Fixed compilation bugs where variables used before all variables defined. Strict ANSI C compilers will need this. 5. Amended CGI Host Delete Policy to allow faster editing. Please enjoy and report all problems. The next exciting version from Yves will be a language translation into French. We are looking for translators into other languages. Please let us know if you can give some time for this, you will be fully credited for all work. Regards, Yves and Ben. |
From: Ben C. <BCl...@pe...> - 2004-11-02 12:25:07
|
Dear Users, Jeff Scott has very kindly donated to the project the domains perfparse.net, perfparse.org and perfparse.com. As well as hosting and storage of web and email. Many thanks for this kindness. The official domain of the project will now become: http://www.perfparse.org If any users of perfparse would like to make valid use of an email address at this domain, please let me know. Regards, Ben. BCl...@pe... |
From: Ben C. <Be...@cl...> - 2004-11-02 12:17:45
|
Dear Users, New version 0.103.1. This includes new abilities. All existing code from previous version remains the same. The MySQL compilation problem has also been fixed. New version, as explained by the author: Perfparsed, when run as a TCP/IP server (which was already possible with 0.102.1), implements a new command : "history". If the file_output storage module is enabled and working, you can ask perfparsed to get some data from the archives between two dates, with optional filters (host/metric/key). As a hidden flavour, with the "history command", perfparsed can read gzipped files if you decided to compress them :) Perfparse can read perf data from a new source : ">host:port". A source with the first character as ">", followed with the host name and port of a running perfparsed can be asked that way for data thanks to the new "history" feature of perfparsed. New options were added to get the data between two dates, with the optional filters host/metric/key. Those two features open the door of new ways to install perfparse, the choice between storing the data in a mysql database to show graphs and compute statistics, and storing data on the remote host as plain text files for easier manipulation, and retrieve the data only when needed. Yves & Ben. |