64 битные счетчики добавлены в 2.0.5 и 2.1-М1.

There is a feature request for this on the dev tracker: https://dev.raden.solutions/issues/874

Hello, Victor and thank you for your reply, you're being very helpful as usual. Regarding "conditions", I'm actually talking about extending an already implemented feature (right click on container,  create condition..., Events and Status/Script). The only thing that is missing IMHO is the possibility to apply "unknown" status to child objects... or more like a mix of "unknown" and "unmanaged", as the idea is to stop all DCI polling until the condition is met again. I'll try to elaborate some more... for some of my coworkers, a container with a big red "critical" status implies that something is wrong with the objects it contains (especially when they all also turn "critical"). It takes ages for them to figure out that the problem is actually due to NetXMS not being able to access its child objects because of a small red "critical" condition on a single, seemingly unrelated node and/or interface.

hi victor, thank you very much

Thank you victor, glad i can contribute to this awesome piece of software

Hi Alex, Tks for reply. With this option we see alot of information in screen. When I think about the kiosk mode, would be something like direct link to dci table or just a direct link to a graph. Tks,

Сейчас нет. Можно зарегистрировать как feature request в нашем трекере.

we are using the JIRA integration to create issues on alarms. But sometimes we allready have created issue via JIRA Would it be possible to link alarm to JIRA ticket? In some cases, we have more then one alarm on same JIRA ticket. In this cases it would be nice to link each alarm to same ticket.. This feature could also add option to update JIRA link in situation where ticket is moved and get another ID (Even if JIRA support forwarding of old ticket-id to new id..)

Hi, a short description of what I'm doing: I create a dump of the netxms_db restore it on a test system and start NetXMS On the test system all nodes are unreachable. After a short time the network map looses allmost every information, as you can see in the pictures below. On each restored database it is different which elements are removed and which remains on the map.  ??? It would be better when elements and links with their actual status remain on the map. Changing "TopologyExpirationTime" seems to make no difference. Best regards. [image: map at start.jpg] [image: map after short time.jpg]

WOW :DDDDD I'ts amazing This is will help alot Tks:)

Hi, When trying to look at previous values in DCI tables, I only see the options "Line chart", "Bar chart" and "Pie chart". For a standard DCI, there is also a "History" option which doesn't seem to exist for tables. Considering the data is already stored in the database, it would be nice to be able to access it using that "History" as well. For example certain values may be strings, which won't really work with any of the charts. So without "History", there is really no way of looking at changes over time. Cheers

Очень хотелось бы, чтобы множители использовались во всех типах графиков, а не только в линейной диаграмме как сейчас. Пример на скриншоте: значения в линейной диаграмме в гигабайтах, во всех остальных - в байтах. [image: Screenshot_1.png] [image: Screenshot_2.png] [image: Screenshot_3.png] [image: Screenshot_4.png]

I second this feature request.

awesome thanks. Any thoughts on the other request about making syslog events clickable?

There is already a feature request for this on the tracker, feel free to monitor its progress here: https://dev.raden.solutions/issues/687

@aleksander said in Templete: Бало бы неплоко привязывать свои Templete. для меню сбора информации по интерефейсу. т.к. тех счетчиков не достаточно. а в ручную набивать допустим на 30-40 интерфесах очень долго .. количество трафик + пакетов .. замечательно.. но допустим. для FC Свитча они не применимы..  там идет своя трансвормация пакетов.. или допустим что нужно .. собирать мультикаст, бродкаст. .1.3.6.1.2.1.31.1.1.1.3.ifindex тоже нужно очень долго настраивать.. Поддерживаю, это также решит эту проблему: https://www.netxms.org/forum/e-eoe-o-koaot-netxms/dci-maximum-value/

Скоро ли будет доступен хотя бы минимальный функционал?

Тоже самое для ppp интерфейсов. Interface "ppp148" changed state to UP (IP Addr: UNSPEC/0, IfIndex: 255) Хотелось бы видеть какой там P-t-P IP, а в посте выше peer IP. ifconfig ppp148 ppp148 Link encap:Point-to-Point Protocol inet addr:10.10.1.1 P-t-P:10.10.1.10 Mask:255.255.255.255 UP POINTOPOINT RUNNING MTU:1480 Metric:1 RX packets:14112596 errors:0 dropped:0 overruns:0 frame:0 TX packets:27474640 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1468984852 (1.3 GiB) TX bytes:34776188499 (32.3 GiB) Создал feature request https://dev.raden.solutions/issues/1165