NetXMS Support Forum

English Support => General Support => Topic started by: Dani@M3T on March 06, 2014, 04:56:41 PM

Title: Naming convention
Post by: Dani@M3T on March 06, 2014, 04:56:41 PM
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?
Title: Re: Naming convention
Post by: Victor Kirhenshtein on March 06, 2014, 05:29:38 PM
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
Title: Re: Naming convention
Post by: Dani@M3T on March 06, 2014, 05:54:40 PM
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