Some key metrics on Solaris "Not supported by Zabbix"?

[tchjts1]

We're very interested in monitoring some Solaris 10 machines. But as I explore what can be monitored by Zabbix, it appears there are several very key metrics which are unsupported such as CPU idle, nice, system, user, wait, I/O traffic, etc.

Is there a way to activate them in Zabbix or to populate them into Zabbix?

I assume zabbix_sender will come into play there, but I haven't figured that one out yet either.

Does anyone have a modified Solaris template which gathers more info than the standard one?

[ldil]

Hi tchjts1,

You can create your own monitoring parameters and put them in your zabbix_agnetd.conf file.

We have created things like this and the work great.

UserParameter=http.users,/bin/netstat -n -a | /bin/grep :80 | /usr/bin/wc -l
UserParameter=http.users.netcon,/bin/netstat -n -a | /bin/grep :80 | /bin/grep "5:80" | /usr/bin/wc -l
UserParameter=http.users.vc,/bin/netstat -n -a | /bin/grep :80 | /bin/grep "245.31" | /usr/bin/wc -l
UserParameter=aspav.mailq,mailq | grep @ | cut -f1 -d ' ' |awk '!/^ *$/' | wc -l

Greetz Leo

[tchjts1]

Thanks Leo. yes, we are figuring that out now. One of my co-workers has written a nice how-to on this. I will ask his permission to post it here to help others who are also new to Zabbix and trying to figure this one out.

[ldil]

If you create a template out of this i am very interrested in that template

Greetz Leo

[email protected]

[maxpower]

WBut as I explore what can be monitored by Zabbix, it appears there are several very key metrics which are unsupported such as CPU idle, nice, system, user, wait, I/O traffic, etc.

I reported that bug already months ago and later even opened a case (ZBX-370) without reaction so far.
The code for it is in Zabbix but it is not working.

[max2xam]

bump .... yeah same problem here it would be nice to have working zabbix_agent monitoring base info on solaris 10 machines, at this time i'm working on workarounds which bring nasty mess into templates and agent configs.

[jamesh]

Until it's fixed I'm using this in my zabbix_agentd.conf to query anything I need to:

UserParameter=sys.cmd[*],VAL=`$1`; if [ "$VAL" = '' ]; then VAL='[null]'; fi; echo $VAL

It returns the string '[null]' if the value is null to make sure zabbix doesn't think the parameter is unsupported. You can use keys like this without having to tweak with UserParameters every time you want to change something:

sys.cmd[netstat -n -a | grep :80 | wc -l]

James

[trikke]

Why not just use system.run[<put your command here>] ????

Greets
Patrick

[jamesh]

Nice...didn't know that was available.

[ngarnier]

Is there a difference between cost's execution time or cost's cpu time for an item "system.run[<COMMAND>]" and an item "<ITEM X>" with an UserParameter=<COMMAND> ?