#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 at the beginning of the line.

#4. Save the file on any computer, but upload it to the Applications Manager web client using the bulk import monitor form.

#5. After uploading, click on Next, and 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 a few minutes to complete the process. When the monitors are scheduled for discovery, the uploaded file will be deleted from Applications Manager (as this file contains security information).

#7. If you want to cancel the process midway, delete the uploaded file from the 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.

#11. Enter the credentialID if you wish to use preconfigured credentials details from the Credentials Manager.

#12.ManagedServerID and ManagedServerGroupName can be specified only if bulk import is being performed from the Central Server in the Enterprise Edition. If these field values are not specified, then the new monitor will be added to the least loaded Probe Server.

#13. The existing MonitorGroupID has to be specified, and it will not create a new Monitor Group if the ID specified does not exist.

#14. The encryption parameter has to be specified as true when the user wants to make an encrypted connection with Applications Manager.

#15. The validateServerCertificate parameter have to be specified as true when user want to make encrypted connection with SSL Certificate validation. This field applies only to "microsoftjdbcdriver".

#16. The authType has to be mentioned to choose the authentication type, such as SQL, NTLM, Kerberos, or Native Authentication

#17. The driver type has to be mentioned as Microsoft JDBC driver or JTDS JDBC driver to choose the required driver for connecting to the database for data collection. This is optional, and the default driver is the Microsoft JDBC Driver.

 

#Header: DisplayName, HostName, SubNetMask, Port, Username, Password, credentialID, Instance Name, MonitorGroupID, PollInterval, encryption validateServerCertificate, EnableKerberosAuthentication,driverType

Production,Server1,255.255.255.0,1433,Administrator\sa,P@s$w0rd,,,10000095,5,true,false,false,microsoftjdbcdriver

Staging,Server2,255.255.255.0,1433,,,1,,10000095,5,true,false,true

 

# If you want to connecto the MSSQL server using a named instance, then specify the Instance Name, or else please leave this field empty like the above example.
testing,Server3,255.255.255.0,1433,Administrator\sa,P@s$w0rd,,SQLINSTANCE,10000095,5,true,false,false,jtdsjdbcdriver