#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.The existing MonitorGroupID have to be specified and it will not create new Monitor Group if the ID specified is not existing.

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

#Note:NameNode is the master node in the Apache Hadoop HDFS Architecture that maintains and manages the blocks present on the DataNodes (slave nodes).In some Hadoop configurations, a simple authentication user name may be required for running API commands and collecting metrics from the NameNode. When monitoring such Hadoop installations, specify the name of the simple authentication user. If no such user is available/required, then provide 'NoAuth' instead of SimpleAuth.

#Header:DisplayName,Mode Of Monitoring,Version,NameNode Host,NameNode JMX Port,NameNode Web Port,NameNodeSSLEnabled,NameNodeWebAuthType,NameNodeUserName,NameNodePassWord,NameNode JNDIPath,JobTracker/ResourceManager Host,JobTracker/ResourceManager JMX Port,JobTracker/ResourceManager Web Port,JobTrackerSSLEnabled,JobTrackerWebAuthType,JobTrackerUserName,JobTrackerPassWord,JobTracker/ResourceManager JNDIPath,MonitorGroupID,PollInterval

Production,RESTAPI,2.x,Server1,,50070,no,SimpleAuth,Administrator,P@s$w0rd,,Server1,,8088,no,SimpleAuth,Administrator,P@s$w0rd,,,5

Deployment,JMX,1.x,Server2,8004,,,SimpleAuth,Administrator,P@s$w0rd,/jmxrmi,Server2,8005,,,,Administrator,P@s$w0rd,/jmxrmi,,5