Automatic on-boarding of Azure Resources to Monitoring

Ever wanted to run your Azure resources on-boarding to monitoring in a fully automated fashion? Now you can !

The Azure Sensor Pack has a built-in capability to automatically on-board any new Azure resource your IT team has added.

Automatic Azure on-boarding to monitoring

How it Works ?

The Azure Sensor pack service reads the Scheduler.csv file every 10 minutes and acts according the configuration lines. It utilizes the Azure Sensor Pack API to run auto-discovery commands followed by monitoring automation API calls.

It allows users to configure different schedules for discovering their Azure estate

Configuration

The configuration of the automatic scheduler is located at:

C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\AutoMonX\Azure\Scheduler\Scheduler.csv

You can configure the scheduler to auto-discover and add to monitoring:

• The entire Azure Tenant

• A specific subscription

• All the tenants and their subscriptions

Examples

The line below would initiate a daily discovery at 19:00 of tenant labeled as AcmeTenant with our internal id of 1. It will use whitelists (include_mon.csv), discover Azure Resource IDs and discover new resources only. At the end of discovery, new resources would be added to monitoring in PRTG

Daily19:00,Discovery,AcmeTenant,tenant_id=1&resource_id&outmode&whitelist&group_name=AcmeTenant&new_resources

You can add more configuration lines to schedule additional discovery actions

Daily21:00,Discovery,BerlinTenant,tenant_id=2&resource_id&outmode&whitelist&group_name=BerlinTenant&resource_id&new_resources

Discovering a single subscription called "microsoft partner"

Daily09:00,Discovery,AcmeTenant,tenant_id=1&sub=microsoft%20partner&outmode&whitelist&group_name=AcmeTenant

Discovering all tenants and subscriptions

Sat 19:00,Discovery,all,resource_id&outmode&whitelist&add_comments&new_resources

Important:

• The Azure Sensor Pack automatically limit the scheduler activity to run a single discovery command at any given time to avoid system overload

• The command is basically a shorthand for an API call, so any special chars and white spaces in subscription or Tenant names must be properly encoded.