#This is a sample .csv file for bulk import of monitors.

#1. Header should start with #Header: followed by the Input Field names. It is already coded for you. Note: Do not modify the header.

#2. From the second line onwards, give the input values according to the column names in the header.

#3. You can remove the example entries in this file from the second line onwards and add your own monitor input information. You can add comments by including # symbol in the beginning of the line.

#4. Save the file in any computer but upload it to the Applications Manager webclient using bulk import monitor form.

#5. After uploading, click on Next, the entire monitor input information will be shown in a table format for your reference.

#6. If everything is OK, click on Start Discovery. The monitors will be scheduled for discovery. It would take few minutes to complete the process. When the monitors are scheduled for discovery, simultaneously the uploaded file will be deleted from Applications Manager (as this file contains security information)

#7. If you want to cancel the process in midway, delete the uploaded file from Applications Manager machine.

#8. Fields MonitorGroupID and PollInterval are Optional.If PollInterval is not specified, the default value for it will be 5 minutes.

#9. PollInterval should be given in Minutes.

#10.Field Credential ID :Enter the credentialID, if the credentials given in the Applications Manager's Credential Manager is used.

#11.EnableKerberosAuthentication: By default it will be disabled. If you want to enable Kerberos Authentication provide yes. It is supported only in WMI mode.

#12.EnableEventLogMonitoring: By default it will be disabled. If you want to monitor Windows Events provide yes. It is supported only in WMI mode.

#13.Resolve DNS: By default it will be disabled. If you do not want to resolve your host name and want your hostname to be added as IP address provide FALSE. Provide TRUE if you want your hostname to be resolved and added as domain name.

#14.The existing MonitorGroupID have to be specified and it will not create new Monitor Group if the ID specified is not existing.

#15.ManagedServerID and ManagedServerGroupName must be specified only if bulk import is being performed from the Admin Server in the Enterprise Edition.

#16.SSHKeyAlgorithm possible values are RSA , DSA and DCC

#17.OperatingSystem possible values are Windows 2000/ Windows 2003/ Windows XP/ Windows NT/ Windows Vista/ Windows 7/ Windows 2008/ Windows 8/ Windows 2012/ Windows 10/ Windows 2016/ Windows 2019/ Windows 11/ Windows 2022/ AIX/ Linux/ Sun/ FreeBSD/ HP-UX/ Mac OS/ Novell

#Header:DisplayName,HostName,Port,Timeout,OperatingSystem,SubNetMask,ModeofMonitoring,UserName,Password,credentialID,SSHKeyAlgorithm,SSHPublicKey,passphrase,SNMPCommunityString,TelnetSSHCommandPrompt,MonitorGroupID,PollInterval,EnableEventLogMonitoring,EnableKerberosAuthentication,Resolve DNS

#Example for WMI mode of monitoring
Production,Server1,40,Windows 2003,255.255.255.0,WMI,Administrator,P@s$w0rd,,,,,,,MonitorGroupID,5,yes,yes,FALSE
Staging,Server2,,40,Windows 2003,255.255.255.0,WMI,Administrator,P@s$w0rd,,,,,,,MonitorGroupID,5,no,yes,FALSE
Deployment,Server3,40,Windows 2003,255.255.255.0,WMI,Administrator,P@s$w0rd,,,,,,,MonitorGroupID,5,no,FALSE
#Example for SNMP mode of monitoring
Production,Server4,161,40,Windows XP,255.255.255.0,SNMP,Administrator,P@s$w0rd,,,,,public,,MonitorGroupID,5,,FALSE
#Example for Telnet mode of monitoring
Staging,Server5,23,40,Linux,255.255.255.0,TELNET,Administrator,P@s$w0rd,,,,,,$,MonitorGroupID,5,,FALSE
#Example for SSH password based authentication
Deployment,Server6,22,40,Linux,255.255.255.0,SSH,Administrator,P@s$w0rd,,,,,,$,MonitorGroupID,5,,FALSE
#Example for SSH key based authentication
Production,Server7,22,,40,Linux,255.255.255.0,SSH,Administrator,P@s$w0rd,,DSA,,,,$,,5,,FALSE