search cancel

Azure Probe - Databricks

book

Article ID: 190402

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

My Azure probe is modeling my Databricks Machines but by default this kind of machines is created when the load is high and deleted automatic when the load decrease. 

I don't want to monitor this kind of machines because we have a lot of critical alarms and false incidents being opened. 

Here an example of the databricks VMs:

Environment

Release : 20.1

Component : UIM - AZURE

Resolution

Provided test build v3.16T1 to avoid creating databricks VMs. It is also required to remove the databricks VMs from the USM (so they are removed from the CM_COMPUTER_SYSTEM table).

1. Deploy the newer version of azure probe v3.16T1 to the respective robot.
2. From Infrastructure Manager -> Go to Raw Configure -> Resources -> Select Appropriate Resource -> Properties
   Add New Key "ignoredGroupForVms" and its value as "databricks". Then click OK and Apply. 
3. Restart the probe.
4. In admin console verify the VM's relates to databricks group is visible or not.

 

If still the VM's are visible with new/updates values then need to configure this probe from starting

 

1. Deactivate the probe.
2. Take backup of the entire azure probe directory and keep it to safe place.
3. Delete the probe from Infrastructure Manager.
4. Delete the entire probe directory.
5. Deploy the newer version of azure probe v3.16T1 to the respective robot.
6. Configure the probe again.
7. From Infrastructure Manager -> Go to Raw Configure -> Resources -> Select Appropriate Resource -> Properties
   Add New Key "ignoredGroupForVms" and its value as "databricks". Then click OK and Apply. 
8. Restart the probe.
9. In admin console verify the VM's relates to databricks is visible or not.

Attachments