RE: Development directions

What about to start with just making Unix agent upgrades as well as to make
service checks to really make checks? :)

We still have .14 on all unix servers, as upgrade is not working for unix'es
yet.

We also don't have reliable service checks. Half of service checks shows
some magical stuff instead of real data: dozens of false alarms, some
servers are "always down" while actually up, and so on.
Currently we had to disable all service checks at all, as noone trusts into
this checks anyway.

So I think it's nice to have all this pretty GUI stuff, but without reliable
monitoring agents it's just useless... Without proper upgrade procedure -
installing new versions with new stuff - this is amount of work that makes
all this stuff useless too.

-----Original Message-----
From: Victor Kirhenshtein [mailto:victor_at_opticom.lv]
Sent: 2 ����� 2005 �. 12:56
To: NetXMS Developers talks
Subject: [netxms-dev] Development directions

Hi all!

Is there any ideas on what direction(s) we should focus for the next
versions? I see the following to choose from:

- GUI improvement. This can include more powerful graphs, simplified
policy editing, sorting in all views.
- Event correlation.
- Agent improvement (more parameters, maybe some optimization).
- Log analyzer subagent.
- Perl subagent (to make possible write parameter handlers in perl
without executing perl interpreter each time).
- Centralized agent management - agent configuration editing from
console, remote agent restart.
- Data collection templates.
- SNMP support improvement (adding support for v3, extensive testing,
adding MIB parser to libnxsnmp).
- Add support for plugins to GUI.
- Network maps.

I'm waiting for your comments.

Regards,
Victor
Received on Wed Mar 02 2005 - 13:08:40 EET