Hi all,
I was just switching to Zabbix and am pleased with it at the moment. I haven't checked out triggers or alerts yet, but it'll come...
Since I already have a PostgreSQL up and running, I patched alpha12 to use it. My server is slow and I really want as little stuff running on it as possible. (And I can't stand the lack of useful SQL-statements in MySQL...
This also led me to checking the sources for agentd...
It seems this process is doing /proc-reading once a second, in my case without a reason. I don't care about interface statistics on that server. What I would like is a quiet daemon which does as little as possible. So:
1) Is there a reason these tests (stats.c) are not run like all other parameters, from the agent_command-list.
2) Would it be benificial to use dynamic modules (SO/DLL/perl using embedded perl) for plugins to reduce the number of forks and image size? I realize most people use more UserParameters than built-in tests, so generalizing the agent_command to use dynamic modules is what I'm looking for.
3) Is it a long-term goal to merge the Win32 agent and the Unix agent, or do we have an OpenAFS-situation where the two move further away from each other? Of course, I would like the entire suite converted to MinGW to enable autoconf even on Windows.
These questions are not critics of Zabbix, merely a question whether I should spend time implementing it or not. Minimizing system resources is my major concern (both image size and CPU time) right now.
/Tommie
I was just switching to Zabbix and am pleased with it at the moment. I haven't checked out triggers or alerts yet, but it'll come...
Since I already have a PostgreSQL up and running, I patched alpha12 to use it. My server is slow and I really want as little stuff running on it as possible. (And I can't stand the lack of useful SQL-statements in MySQL...
This also led me to checking the sources for agentd...It seems this process is doing /proc-reading once a second, in my case without a reason. I don't care about interface statistics on that server. What I would like is a quiet daemon which does as little as possible. So:
1) Is there a reason these tests (stats.c) are not run like all other parameters, from the agent_command-list.
2) Would it be benificial to use dynamic modules (SO/DLL/perl using embedded perl) for plugins to reduce the number of forks and image size? I realize most people use more UserParameters than built-in tests, so generalizing the agent_command to use dynamic modules is what I'm looking for.
3) Is it a long-term goal to merge the Win32 agent and the Unix agent, or do we have an OpenAFS-situation where the two move further away from each other? Of course, I would like the entire suite converted to MinGW to enable autoconf even on Windows.
These questions are not critics of Zabbix, merely a question whether I should spend time implementing it or not. Minimizing system resources is my major concern (both image size and CPU time) right now.
/Tommie