Schedule demo

#This is a sample .csv file for the bulk import of monitors.
#1. The 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, enter 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 monitor input information. You can add comments by including the # 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, 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 will take a 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 midway, delete the uploaded file from the Applications Manager installed machine.
#8. Account Type - The Azure cloud the subscription belongs to. Possible values: AzureGlobal / AzureGovCloud / AzureChina. Default: AzureGlobal.
#9. Onboard as - Possible values: Subscription / Tenant. 'Subscription' adds one monitor for the Subscription Id given. 'Tenant' adds one monitor for the whole directory, which then creates a Subscription monitor for each subscription in its scope. Default: Subscription.
#10. Discovery Mode - Possible values: AzureSPApp / AzureOAuth / AzureOrgAccount. 'Tenant' onboarding supports AzureSPApp and AzureOAuth only; AzureOrgAccount is refused.
#11. Directory (tenant) ID, Application (client) ID and Client Secret Value (Application Key) - Required for AzureSPApp.
#12. OAuth Provider - Required for AzureOAuth. Give the Provider ID of an OAuth provider already configured in Applications Manager, not its name.
#13. User Email and Password - Required for AzureOrgAccount only.
#14. Subscription Id - Required when 'Onboard as' is Subscription. Leave it empty for a Tenant monitor.
#15. Subscription Scope - Tenant monitors only. Possible values: AllSubscriptions / SelectSubscriptions. Default: AllSubscriptions.
#16. Subscriptions - Required when 'Subscription Scope' is SelectSubscriptions. Comma separated subscription IDs, entered inside "". A Tenant monitor adds up to 150 Subscription monitors by default.
#17. Auto-add New Subscriptions - Tenant monitors with Subscription Scope 'AllSubscriptions' only. Possible values: true / false. Default: true. When false, only the subscriptions the Tenant monitor has already added stay monitored; its first discovery adds them all.
#18. Apply Tenant Monitor Settings - Leave it empty or false. It applies only to Subscription monitors that a Tenant monitor creates, so a monitor added by bulk import always stores false.
#19. Azure Services - To monitor all the supported services, specify as 'All-Supported-Services' or for monitoring particular services specify the service name by referring the Module Types supported for Microsoft Azure. Refer the Module Type column in the help document (https://www.manageengine.com/products/applications_manager/help/discovery-filters.html#monitortypes)
#20. Child Monitor Discovery - Possible values: 0, 1 and 2. 0 - Discover and unmanage, 1 - Discover and monitor, 2 - Discover and monitor based on Regex. Default: 1.
#21. Discovery Filter Regex - This field is required only if Child Monitor Discovery is set to 2. Syntax: <Module Type>_<Attribute Name>=[Regex]. Attribute Names: Name, ResourceGroupName. Refer to the samples given below and the Microsoft Azure help documentation (https://www.manageengine.com/products/applications_manager/help/discovery-filters.html#monitortypes) to know more about the module and attribute types supported.
#22. Filter by Tags - Possible values: true / false. Default: false. The four tag fields below are considered only when this is true. On a Tenant monitor it decides which subscriptions are added, matching a tag on the subscription, its resource groups or its resources. On a Subscription monitor it decides which resources are discovered, matching the resource's own tags and its resource group's tags. A Tenant monitor whose filter matches no subscription is not added. Not supported for AzureOrgAccount; leave the tag fields empty in that mode.
#23. Include if Tags Match / Exclude if Tags Match - Syntax: <Tag Key>>>><Tag Value>, for example Env>>>Prod. Separate several values of one key with ###, for example Env>>>Prod###Staging, and separate keys with \n, for example Env>>>Prod\nOwner>>>Platform.
#24. Match Include Tags / Match Exclude Tags - Possible values: Or / And. Default: Or. 'Or' matches when any one of the configured tag keys matches (Any Tag Key on the monitor page); 'And' only when all of them match (All Tag Keys).
#25. Advanced Settings - Possible values: true / false. Default: false. The fields from 'Associate to Monitor Group' to 'Retry data collection API' are considered only when this is true.
#26. Associate to Monitor Group - Possible values: true / false. When true, the child monitors discovered are automatically associated into Monitor Groups based on their Azure Resource Group.
#27. Alert on Resources Creation and Deletion - Possible values: true / false.
#28. Set health severity as - Possible values: Warning / Critical. This field is considered only when 'Alert on Resources Creation and Deletion' is set as 'true'.
#29. Raise alerts when Resources are - Possible values: Created / Deleted / Both. This field is considered only when 'Alert on Resources Creation and Deletion' is set as 'true'.
#30. Action on Deleted Resources - Possible values: Alert / Stop / Unmanage / Delete. Default: Alert. It applies to resources deleted in Azure.
#31. Services to Stop Discovery - Leave it empty, as it is ignored in monitor addition. It can be set later from the Edit Monitor page.
#32. Retry data collection API - Possible values: true / false.
#33. Timeout - The time in seconds to wait for an Azure API call. Default: 300.
#34. PollInterval and Discovery Interval should be given in minutes. Discovery Interval is how often child monitors, or a Tenant monitor's subscriptions, are discovered.
#35. Values with embedded commas must be entered inside "".
#36. Field MonitorGroupID is optional.
#37. ManagedServerID and ManagedServerGroupName can be specified only if a bulk import is being performed in the Admin server of the Enterprise Edition. If these field values are not specified then the new monitor will be added to the least loaded Managed Server.

#Header:DisplayName,Account Type,Onboard as,Discovery Mode,Directory (tenant) ID,Application (client) ID,Client Secret Value (Application Key),OAuth Provider,User Email,Password,Subscription Id,Subscription Scope,Subscriptions,Auto-add New Subscriptions,Apply Tenant Monitor Settings,Azure Services,Child Monitor Discovery,Discovery Filter Regex,Filter by Tags,Include if Tags Match,Match Include Tags,Exclude if Tags Match,Match Exclude Tags,Advanced Settings,Associate to Monitor Group,Alert on Resources Creation and Deletion,Set health severity as,Raise alerts when Resources are,Action on Deleted Resources,Services to Stop Discovery,Retry data collection API,Timeout,Discovery Interval,MonitorGroupID,PollInterval
#AzureTenant1,AzureGlobal,Tenant,AzureSPApp,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,aaaaaaa.bbbbbb~ccccc~ddd-eeeee~fff,-1,,,,AllSubscriptions,,true,,All-Supported-Services,1,,true,Env>>>Prod###Staging\nOwner>>>Platform,Or,Env>>>Dev,Or,true,true,true,Warning,Created,Unmanage,,false,300,60,,30
#AzureTenant2,AzureGlobal,Tenant,AzureSPApp,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,aaaaaaa.bbbbbb~ccccc~ddd-eeeee~fff,-1,,,,SelectSubscriptions,"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,ffffffff-bbbb-cccc-dddd-eeeeeeeeeeee",,,"VirtualMachines,StorageAccounts,AzureAppService",1,,false,,,,,true,false,false,Warning,Created,Delete,,false,300,60,,30
#AzureMonitor1,AzureGovCloud,Subscription,AzureOrgAccount,,,,-1,aaa@bbb.ccc.com,password,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,,,,false,"VirtualMachines,StorageAccounts,PremiumStorageAccount,SQLDatabases,KubernetesServices,LoadBalancer,AzureAppService,AzureVirtualNetwork,AzureMySQLServer,AzureNetworkInterface",2,"VirtualMachines_Name=apm.*,StorageAccounts_Name=^.*diag",,,,,,true,false,true,Critical,Both,Stop,,true,300,30,,30
#AzureMonitor2,AzureChina,Subscription,AzureOAuth,,,,10000000,,,aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,,,,false,"VirtualMachines,StorageAccounts,SQLDatabases,KubernetesServices,ServiceBus,AzurePostgreSQLServer,AzureVirtualNetwork,AzureMySQLServer,AzureNetworkInterface",2,"AzureServices_Name=production && AzureServices_ResourceGroupName=prod-group.*,PremiumStorageAccount_ResourceGroupName=premium.*,KubernetesServices_Name=apm.*",true,Env>>>Prod\nTeam>>>APM,And,,,true,false,false,Critical,Deleted,Unmanage,,false,300,60,,30

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

★★★★★

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by thousands of leading businesses globally