<![CDATA[Naming convention]]>Is there an 'official' naming convention in NetXMS or maybe a good suggestion for naming objects like:

  • DCI
  • Event (I see 'DC_', 'SNMP_', 'SYS_', what is the definition behind this 3?)
  • EventProcessingPolicies
  • Actions

A good system/convention in DCIs and Events would be the most important part.
How do others handle this?

]]>https://forum.netxms.org/topic/2984/naming-conventionRSS for NodeFri, 13 Nov 2026 15:40:24 GMTThu, 06 Mar 2014 14:56:41 GMT60<![CDATA[Reply to Naming convention on Thu, 06 Mar 2014 15:54:40 GMT]]>thanks Victor. So you name the events after the source of the event.
Has anybody a good system for naming the DCI descriptions?
At the moment I handle it as good as possible hirachical from left to right like this:

  • Windows DNS Queries Total/sec
  • Windows DNS Queries PTR/sec
  • Synology Disk Volume5 Size Used
  • Cisco WAN Interface In
  • Windows Service State: Task Scheduler
]]>https://forum.netxms.org/post/13117https://forum.netxms.org/post/13117Thu, 06 Mar 2014 15:54:40 GMT<![CDATA[Reply to Naming convention on Thu, 06 Mar 2014 15:29:38 GMT]]>Predefined events follows this scheme:

SYS_ - all system events, generated inside server. Default events also have SYS_ prefix (like SYS_THRESHOLD_REACHED).
SNMP_ - events generated from SNMP traps.
DC_ - events generated from threshold violation (DC stands for Data Collection).

In addition, I often use prefix SYSLOG_ for events generated by syslog parser, and some times per-product prefixes as well, like ORACLE_ for all Oracle-related thresholds.

Best regards,
Victor

]]>https://forum.netxms.org/post/13116https://forum.netxms.org/post/13116Thu, 06 Mar 2014 15:29:38 GMT