NetXMS Support Forum

Добавьте юзера в User management, затем дайте ему права в свойствах объекта (или ветки).
По умолчанию доступа нет. Учтите, что доступ на  дешборд или карту не дает автоматически доступа на все объекты, которые там используются.

https://www.netxms.org/documentation/adminguide/user-management.html
https://www.netxms.org/documentation/adminguide/object-management.html#access-control

Выставить EnableSNMPTraps в 0 и рестартануть netxmsd

Yes, should be possible. If it supports SNMP - you can control it out of the box, just matter of the configuration.
If management is available over any other kind of proprietary protocol - you'll need to create some script for integration.

https://wiki.netxms.org/wiki/NXSL:FindAllDCIs

Как-то так (код не проверял):

total = 0;
dciList = FindAllDCIs($node, "System.CPU.Usage(*)");
foreach (dci : dciList) {
  total += GetDCIValue($node, dci->id);
}
return total;


APT will update installed packages.
Under normal circumstances netxmsd will shutdown properly and remove database lock - and will not require any manual intervention.

добавить еще один DCI с source=Script.
Скрипт примерно такой:
v1=GetDCIValueByName($node, "TrafficDci1");
v2=GetDCIValueByName($node, "TrafficDci2");
v3=GetDCIValueByName($node, "TrafficDci3");
return v1 + v2 + v3;
Или без скрипта в library - source=Internal, DCI=Dummy, скрипт прописать прямо в Transformation script.

Hello.

We had an issue with out build farm; Ubuntu packages will be available in couple of days.

Да, мы обновим документацию в ближашие несколько дней.

Update: %OBJECT_IP_ADDR% больше не поддерживается, вместо них - макросы как в Event Processing (%a). Список: https://wiki.netxms.org/wiki/UM:Event_Processing#Macros_for_Event_Processing

Update: %OBJECT_IP_ADDR% is now deprecated, use EPP macroses instead (%a). More: https://wiki.netxms.org/wiki/UM:Event_Processing#Macros_for_Event_Processing

Макросов вида %OBJECT_IP_ADDR% больше не существует, вместо них можно использовать те же самые макросы, как в event processing (https://wiki.netxms.org/wiki/UM:Event_Processing#Macros_for_Event_Processing).
Используйте "%a".

Все пакеты теперь подписаны MD5..SHA512

Sample report (+ source project for Jasper Studio) attached to this message.
To build resulting jar file you need Java and Apache Maven: "mvn package" will produce resulting jar in target/

1) Download https://www.netxms.org/download/reporting/netxms-reporting-server-2.0.4.zip
2) Unpack to any desired location (I'll use /opt/nxreporting)
3) Create folder for configuration: mkdir /opt/nxreporting.
4) Create configuration file /opt/nxreporting/conf/nxreporting.xml:

<config>
  <workspace>/opt/nxreporting/workspace</workspace>
    <netxmsdConfig>/etc/netxmsd.conf</netxmsdConfig>
    <smtp>
        <server>127.0.0.1</server>
        <from>[email protected]</from>
    </smtp>
    <netxms>
        <server>127.0.0.1</server>
        <login>admin</login>
        <password>netxms</password>
    </netxms>
</config>

Section "<netxms>" required only if you have java-based reports, not sql-based.

5) (optional) Create logger configuration /opt/nxreporting/conf/logback.xml:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
    <file>/opt/nxreporting/log/nxreporting</file>

    <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
      <fileNamePattern>/opt/nxreporting/log/nxreporting.%i.gz</fileNamePattern>
      <minIndex>1</minIndex>
      <maxIndex>5</maxIndex>
    </rollingPolicy>

    <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
      <maxFileSize>16MB</maxFileSize>
    </triggeringPolicy>
    <encoder>
      <pattern>%d %5p | %t | %-55logger{55} | %m %n</pattern>
    </encoder>
  </appender>

    <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>%d %5p | %t | %-55logger{55} | %m %n</pattern>
        </encoder>
    </appender>

    <logger name="com.radensolutions" level="debug" />
    <logger name="com.radensolutions.reporting.infrastructure.impl.TcpConnector" level="error" />

    <root level="DEBUG">
        <appender-ref ref="CONSOLE"/>
        <!--<appender-ref ref="FILE"/>-->
    </root>
</configuration>


More info: http://logback.qos.ch/manual/configuration.html

6) Create folder for workspace and copy some definitions:

mkdir -p /opt/nxreporting/workspace/definitions
cp ldz-alarm-resolution-time-1.0.0.jar /opt/nxreporting/workspace/definitions/

7)  Enable reporting server connector, set EnableReportingServer to 1 (either in GUI - server configuration, or using command line: "nxdbmgr set EnableReportingServer 1"), then restart netxmsd.
8) Create additional tables by executing both scripts from https://git.netxms.org/public/netxms.git/tree/refs/heads/develop:/src/java/nxreporting/sql
9) Start reporting server: cd /opt/nxreporting/ && java -jar nxreporting-2.0.4.jar


In under 10 seconds, netxmsd should connect to reporting server and list of available reports will be visible in "Reporting" perspective.

Final layout of the file system:

/opt/nxreporting/conf/logback.xml
/opt/nxreporting/conf/nxreporting.xml
/opt/nxreporting/lib/*.jar
/opt/nxreporting/reporting-server-2.0.4.jar
/opt/nxreporting/workspace/definitions/ldz-alarm-resolution-time-1.0.0.jar

Please start netxmsd with debuglevel=9 and provide log (you can send it to [email protected]).