NetXMS Forum

Works for me.

My colleague Julius Loman who is a Docker fan/guru created automated (that means always latest version) docker files for NetXMS server, WEB UI and console:

• https://hub.docker.com/r/lomo/netxms-server/
• https://hub.docker.com/r/lomo/netxms-webui/
• https://hub.docker.com/r/lomo/netxms-nxmc/

So you just need to pull the images, create instances and off you go See instructions on hub for WEB UI and console. In case you have questions ask them here.

Victor,

thanx for quick answer. Knowing this is possible and even on your list is great. I'd be willing to dedicate some resources and contribute to this as for me NetXMS can be very versatile tool for broad scenarios' usage from event-oriented telcos to more performance oriented ITs. We as a company (http://www.tempest.sk/service-management--it-/188s) have been long active in monitoring area using HP, IBM and BMC tools but the market pushes for more open and cheaper alternatives. We have committed ourselves to have such in portfolio and this so far seems the best choice with broadest functionality existing and still having clean architecture and extensibility (I miss these qualities in solutions like Zabbix).

I'll have a look at source code even I haven't really programmed for some time (and what I did was Java). I'll see if some of my guys would be able to help to move this forward by contributing code.

My take on providing this functionality would be (apart from core stuff itself):

• Additional types/categories of classes should be manageable - be able to provide new through some administrative interface
• (Sub)Agent API should probably be extended to be able to provide list of nodes and their metrics

I have another idea which I'd like you to ponder about: to me it seems it would be quite beneficial if a kind of agent/plugin would be created that would allow to utilize "monitoring packs" of other (preferably open-source) solutions to quickly broaden supported range of monitored resources. Something like universal adapter for Zabbix/ZenOSS/... packs. What do you think?

To expand on what my colleague wrote: we consider applications running on certain node to be objects on their own. For example Oracle database (and its running instances, listener, ...) is an object that can be monitored via various ways. State of this object has meaning in  context of some Business Service. Itself it partially depends on resources of the host where it's running (enough CPU and disk space for example) but not entirely (some of its state is not affected and is independent from underlying OS - for example number of connections in pool). This leads us to a concept where such thing (Oracle database) should be an object of its own state driven by its monitored attributes (and affected by propagation from underlying nodes that represent OS or for example storage it uses). This concept of having nodes for higher-level application entities is supported by following scenario: imagine a host where you have Oracle database running and also Apache web server running. Oracle is being used by Business Service 1, Apache is being used by different Business Service 2. Currently there is no way (at least I do not see one) how to propagate status of Oracle into Business Service 1 tree and status of Apache into Business Service 2 tree. Metrics of Oracle and Apache should not be mixed together with its underlying node.

So generally there should be an option for (sub)agents to create instances of application entities it monitors. This would also make an easy way to create "proxy" agents that feed information from other management systems. Does this make sense?