NetXMS Support Forum

Hi!

If I understand problem correctly - you want to see on node's performance tab DCIs created on interfaces, right? Then you have to find these DCIs in node's data collection configuration, go to properties, and check "show on performance tab" checkbox.

Best regards,
Victor

Добрый день!

Здесь есть два пути:

1. Разрешить серверу ходить на узлы по SNMP - судя по тому, что интерфейсы называются unknown, сервер не имеет доступа к этим хостам. Тогда сервер получит список интерфейсов и будет знать, что ето одна нода.

2. Создать интерфейсы руками - выбрать ноду, и потом Create interface из контекстного меню.

Не забудьте только вначале удалить "лишние" обьекты хостов.

Hi!

It's not so simple to use command's output in Windows as in UNIX shell. You can achieve this using FOR command:


for /F %x in ('nxget localhost Icmp.Ping(10.194.133.1)') do @nxpush -u admin -P ******** localhost Switch_1:Time=%x


However, there are easier way to achieve what you want using proxy DCI: create DCI on node Switch_1, set origin to "NetXMS Agent", enter Icmp.Ping(10.194.133.1) as name, and set proxy node to your NetXMS server node. This way system will show collected data for node Switch_1, but real data collection will occur from NetXMS server node. You will also need to add Switch_1 to list of trusted nodes in NetXMS server node's properties, or set server configuration variable "CheckTrustedNodes" to 0.

Best regards,
Victor

Hi!

Yes, support for SNMP tables is not finished yet. I have created a new issue in bugtracker so you can follow a progress: https://www.radensolutions.com/chiliproject/issues/198.

Best regards,
Victor

Normally, when alarm's repeat count increases (because new event was matched to existing alarm by alarm's key), alarm's state reset to "outstanding". To prevent this, you can use "sticky acknowledge". In that state, alarm will remain acknowledged event after new matching events.
This can be useful when you know that there will be new matching events, but it will not change the situation. For example, if you have network device which will send new SNMP trap every minute until problem solved, sticky acknowledge will help to eliminate unnecessary outstanding alarms.

Best regards,
Victor

Hi!

Thanks for pointing me on this! The housekeeper code is so wring here... One possible solution could be adding an index on event_log.event_source and replacing

SELECT event_source FROM event_log WHERE event_source=?

with

SELECT COUNT(event_source) FROM event_log WHERE event_source=?

and probably with

IF EXISTS (SELECT event_source FROM event_log WHERE event_source=50220) SELECT 1 ELSE SELECT 0

for MS SQL.

Another option is to remove this check altogether, as it is needed only for one purpose - prevent creation of new object with ID which was used before and still referenced in event log. This can happen, however, only if object(s) with highest IDs deleted, and server restarted before creating new object. It's probably better to just keep track of highest used ID elsewhere.

Best regards,
Victor

Collected DCI data stored in multiple tables - one table per node. These tables are called idata_nodeid, for example, idata_100.

You can also use Java API to access collected data from external application.

Best regards,
Victor

Hi!

You have to manually add network services you want to monitor. Right-click on node object, and select "create network service".

What kind of problem you have with transformation script?

Best regards,
Victor

Нет, не используем. А зачем он она нам может быть нужна (если я правильно понял, что вопрос о системах вроде MS BizTalk или FLink)?

Hi!

You can use transformation script to calculate time difference with NetXMS server. Add parameter System.CurrentTime, and use the following transformation script:


return time() - $1;


You'll got difference in seconds between NetXMS server's local time and remote system time.

Best regards,
Victor

Hi!

There are no bulk load in the console. With API it is possible (Java or C API available).

Best regards,
Victor

Yes, it's the same.

Best regards,
Victor

Hi!

You have to load portcheck subagent on agent running on NetXMS server (it could be any other node as well if you need to monitor your service from another point in the network). Just add


SubAgent = portcheck.nsm


to your nxagentd.conf and restart agent.

To do simple connectivity check, create network service object of type "Custom". For testing this type of service, NetXMS just establish TCP connection.

Best regards,
Victor

Hi!

If I understand correctly you need some kind of automated tool to export dashboard content periodically. Currently it is not possible. Theoretically this can be done, especially if limit set of exportable elements to only charts and labels. I'll think how hard it would be.

Best regards,
Victor

Hi!

We don't have and don't plan to have commercial edition of NetXMS. What we have is a commercial add-ons for the following:

1. ATM hardware monitoring;
2. ATM video surveillance;
3. Card management systems monitoring.

These add-ons have licensing mechanism inside. Currently we don't have plans to expand this list. Potential user base for these add-ons are limited (banks and few other financial institutions), and it should not have impact on NetXMS community, but we have a chance to earn some money to be able to continue core product development.

Best regards,
Victor