NetXMS Support Forum

Hi,

very weird. Please check server queues and try to run server with debug level 6 fr some time and check messages with prefix DiscoveryPoller.

Best regards,
Victor

So it should be:

<config>
   <core>
      <MasterServers>XX.XX.XX.XX</MasterServers>
      <ConfigIncludeDir>C:\NetXMS\etc\nxagentd.conf.d</ConfigIncludeDir>
      <LogFile>{syslog}</LogFile>
      <FileStore>C:\NetXMS\var</FileStore>
      <SubAgent>winperf.nsm</SubAgent>
   </core>
</config>


<config>
   <core>
      <SubAgent>logwatch.nsm</SubAgent>
   </core>
   <logwatch>
      <Parser>c:\netxms\var\logwatch_win_eventlog_system_parser.xml</Parser>
      <Parser>c:\netxms\var\logwatch_win_eventlog_application_parser.xml</Parser>
   </logwatch>
</config>

Also, it is not necessary to use XML format - you can use key-value format as well.

Best regards,
Victor

Hi,

currently it's not possible. We definitely can fix column sizes not being saved in dashboards. Regarding to column order configuration - it sounds useful, I will check how big efforts it will require to implement.

Best regards,
Victor

Hi,

currently it's not possible. And what do you mean by "current user" - it is current to what?

Best regards,
Victor

Hi,

yes, proxy is not supported.

Best regards,
Victor

Hi,

as seen from output SubAgent entry for logwatch still in "agent" section, but should be in "CORE". Could you show me how your policy looks like now?

Best regards,
Victor

Hi,

it seems that driver cannot handle stacked switches correctly. Is it possible to organize remote SNMP access  to such stack so we can debug and fix driver?

Best regards,
Victor

Hi,

looks like a bug in dashboard layout code. Could you please export your dashboard and send to me?

Best regards,
Victor

Hi,

deleted nodes should be rediscovered unless there is something stuck in the system. Could you try to login with user "system" and check if these nodes still present somewhere, or use nxadm -c "show objects" to list all objects in the system and check?

Best regards,
Victor

Hi,

it seems to be missing in deb packages. We will check and re-package them to include SSH subagent. On Windows SSH subagent is included.

Best regards,
Victor

Please show output of command

nxagentd.exe -C

Best regards,
Victor

Hi,

no, only one group per DCI is possible.

Best regards,
Victor

В версии 2.1 группировку на performance tab изменили - теперь группируются все DCI с одинаковым значением в поле group. Это было сделано для устранения проблем с группировкой при наложении шсблонов и instance discovery. Процедура обновления базы должна была расставить для существующих привязок автоматически сгенерированые названия вида ## и идентификатор основного DCI. Поле должно быть редактируемым. Я перепроверю у себя что его можно менять.

Hi,

grouping was changed in 2.1 - now UI will group all DCIs with same group ID (which is just free form text). This solves various issues with setting up grouping in templates and for instance discovery DCIs. Upgrade procedure expected to replace existing mappings with ## followed by ID of root DCI - so they should be grouped as before. To fix that you can just enter matching group identifiers for all DCIs that should be grouped.

Best regards,
Victor

Hi,

try to change <agent> tag to <core>.

Best regards,
Victor