| 1 |
>>>> Agreed! Although getting apache, mysql, and nginx plugins fully |
| 2 |
>>>> working is proving to be a little trickier. To get those going it's |
| 3 |
>>>> necessary to edit /etc/munin/plugin-conf.d/munin-node as well as some |
| 4 |
>>>> apache and nginx config. Still working on getting it all 100%. - Grant |
| 5 |
>>> If you have a fairly basic setup, post what you are using to help others |
| 6 |
>>> later on. At least it could give someone a config to go by. |
| 7 |
>> I promise I will do this once I feel good about my config. |
| 8 |
>> |
| 9 |
>> - Grant |
| 10 |
> |
| 11 |
> That's good. Sometimes when I am setting up something, I google for the |
| 12 |
> config file to see if I can find something to go by at least. I did |
| 13 |
> that the other day with my xorg.conf file. I found out that when I |
| 14 |
> logout and leave, my monitor never goes to standby. I found a config |
| 15 |
> file that someone posted that had the info I needed. It was MUCH faster |
| 16 |
> than trying to read man pages and find it. |
| 17 |
> |
| 18 |
> I thought about setting up a site or something and putting different |
| 19 |
> config files there and allowing others to post theirs. Thing is, I'm |
| 20 |
> sort of low income and I don't know how much that would end up costing |
| 21 |
> me. I'd do it for free so I'd pay for whatever it was. I think a |
| 22 |
> central place for this sort of thing would be great. |
| 23 |
> |
| 24 |
> Anyway, it may help the next person if you post what works for you and |
| 25 |
> maybe how you are using it. At least give someone a start. If they |
| 26 |
> google, they will find it. |
| 27 |
|
| 28 |
I used this as a base which is excellent: |
| 29 |
|
| 30 |
http://wiki.gentoo.org/wiki/Munin |
| 31 |
|
| 32 |
Extra config is required if you want to get other plugins working like |
| 33 |
apache, mysql, and nginx The extra config takes place in |
| 34 |
/etc/munin/plugin-conf.d/munin-node and in whatever program you are |
| 35 |
configuring the plugin for. This setup assumes the master and node |
| 36 |
are on the same machine. |
| 37 |
|
| 38 |
apache: |
| 39 |
|
| 40 |
/etc/munin/plugin-conf.d/munin-node: |
| 41 |
[apache_*] |
| 42 |
env.ports 80 |
| 43 |
env.url http://127.0.0.1:80/server-status?auto |
| 44 |
|
| 45 |
/etc/conf.d/apache2: |
| 46 |
add "-D STATUS" to APACHE2_OPTS (apache must be compiled with |
| 47 |
APACHE2_MODULES="status") |
| 48 |
|
| 49 |
mysql: |
| 50 |
|
| 51 |
/etc/munin/plugin-conf.d/munin-node: |
| 52 |
[mysql*] |
| 53 |
env.mysqlopts -u root --password=PASSWORDHERE |
| 54 |
(I'm still having a problem with the myisam and InnoDB graphs.) |
| 55 |
|
| 56 |
nginx: |
| 57 |
|
| 58 |
This should work but it doesn't for me yet: |
| 59 |
http://www.nginxtips.com/nginx-configuration-for-munin/ |
| 60 |
|
| 61 |
It's a good idea to change the following for security as long as the |
| 62 |
master and node are on the same machine: |
| 63 |
|
| 64 |
#host * |
| 65 |
host 127.0.0.1 |
| 66 |
|
| 67 |
It's handy to use 'munin-run PLUGIN_NAME' to test a plugin. |
| 68 |
|
| 69 |
- Grant |
Archives