Changeset 3232
- Timestamp:
- 12/16/09 15:49:48 (2 years ago)
- Files:
-
- trunk/ChangeLog (modified) (2 diffs)
- trunk/UPGRADING (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/ChangeLog
r3230 r3232 11 11 12 12 13 munin (1.4.2, r3167:..., 2009-12-14) 14 13 munin (1.4.2, r3167:3231, 2009-12-16) 14 15 * Munin::Plugin::Pgslq: Clean the fieldnames before returning them, so 16 we don't generate invalid data with for example a dash in the 17 database name. 18 * jmx_: Add authentication support, fix exceptions in various memory 19 related parts, refactor connection negotiation to one central 20 connection class, add default connection info for jmx_, so we 21 actually are a bit autoconfy 22 * munin_update: Update to work correctly with 1.4, document and enhance a bit 23 * munin_stats: Provide better graph_info and set some warning and 24 critical levels at 4 minutes and 4m45s 25 * Improove colors contrast in jmx plugins which have Max area, to make 26 them more readable + fix some indentation 15 27 * ntp_offset: make info into graph_info 16 28 * Munin-(node|run): Make group name resolution lazy, enhance error … … 33 45 * Switch fonts to DejaVuSans og DejaVuSansMono. Vera is now obsoleted 34 46 by DejaVu in most contexts. 47 48 INSTALLERS: On platforms with RRD 1.3 the fonts need not be removed 49 and no paths need to be installed as long as the DejaVuSans font 50 family is installed. 51 35 52 * Reorder somewhat to get lines on top of areas 36 53 * Patch from blueyed to make munin-*cgi-graph work trunk/UPGRADING
r3089 r3232 75 75 will change names as you upgrade and auto-configure your nodes, not 76 76 when you upgrade the munin-master. 77 78 79 Users of Munin 1.2 in combination with NMSes 80 -------------------------------------------- 81 82 There are two issues that have been reported. 83 84 Users of Munin in combination with Nagios have reported that because 85 some graphs have changed their "graph_title" setting this 86 dis-associates the tests from the right nagios checks. 87 88 Also some plugins do not have default warning and critical levels set 89 any more (e.g. "load") because the opinions on what is "normal" load 90 differs widely. This means that the plugins will not send warning and 91 critical events to contacts any more. The warning and critical levels 92 should be settable for all of these plugins, please use the command 93 "munindoc <plugin>" on the host where the plugin is installed to see 94 how to set these levels. 95 96 Too audit the differences in warning and critical levels you can make 97 a copy of the munin file called "datafile" before upgrading (or get 98 one from backup), and use egrep to get a listing of the settings prior 99 to update: 100 101 egrep '(warning|critical)' datafile.old 102 103 and again on the post-upgrade datafile to compare the lists so you can 104 specify the ones you need.
