Showing posts with label cloud management. Show all posts
Showing posts with label cloud management. Show all posts

Friday, 1 November 2019

vRealize Operations Manager 7.5 - Part9 - Dashboard sharing

Ability to share dashboards using URLs without login requirements is a very useful feature starting from vROps 7.0.

  • Select the dashboard that you want to share and click on the share icon as marked in the screenshot below.



  • Click on "COPY LINK" and provide it to whoever necessary. You can also set link expiry to 1 Day, 1 Week, 1 Month, 3 Months, or Never Expire as per your requirement.

  • To unshare a link, enter the link that you want to unshare as shown below and click "UNSHARE".

Hope it was useful. Cheers!


Related posts


Wednesday, 9 October 2019

vRealize Operations Manager 7.5 - Part8 - Super Metrics

In this article, I will briefly explain about using super metrics in vROps 7.5. For example, I will take the VM NUMA optimization super metric which was released recently. You can download the super metric JSON file from the VMware sample exchange

Once the JSON file is downloaded, login to your vROps instance. Navigate to Administration - Configuration and select Super Metrics. Click on Import Super Metric.


Browse and select the JSON super metric file that you downloaded. Click DONE.


Once it is done, you can see the two super metrics. 


To enable the super metric in a policy:
Select the super metric - Edit Selected Super Metric - Goto Enable in a Policy  - Select vSphere Solution's Default Policy and click FINISH.


Now after the default collection interval, you can see the super metric tab as shown below. 


As you can see in the above screenshot, for this virtual machine "lustre01", recommendations are: 
  • NUMA optimal CPU socket: 1 
  • NUMA optimal CPU cores per socket: 8

Hope it was useful. Cheers!

References


Related posts

Saturday, 20 July 2019

vRealize Operations Manager 7.5 - Part6 - Adding new symptoms and alert definitions

In my previous post, I tried to explain briefly about the alerting aspects in vROps and overall workflow of the alerting process. In this post, I will explain how to create custom symptom definitions and alert definitions based on a scenario. 

Scenario


User is running some latency-sensitive business-critical applications on the vSAN cluster. Below are the symptoms that he would like to define and alerts should be produced for the same and these should affect the "Efficiency" badge of the vSAN cluster object. 

  1. Warning - when vSAN Cluster Read Latency is greater than 1 ms
  2. Critical - when vSAN Cluster Read Latency is greater than 2 ms
  3. Warning - when vSAN Cluster Write Latency is greater than 2 ms
  4. Critical - when vSAN Cluster Write Latency is greater than 3 ms 
Sample screenshot of vSAN environment efficiency badge 

Step1: Add symptom definitions


Go to Alerts - Symptom Definitions - Click Add (+)


Select base object type: vSAN Cluster
Select the metric "Read Latency (ms) - double click on it twice so that you can define both warning and critical symptoms.


Provide symptom definition name, criticality and numeric value as required and click Save.


Now you can see the two symptoms which you have just created.


Similarly, create symptom definitions for vSAN Cluster Write Latency.


All 4 symptom definitions are created now.


Step2: Add alert definitions


Next step is to add alert definitions.

Go to Alerts - Alert Definitions - Click Add (+)

  • Provide a name and description.
  • Click on Base Object Type and select "vSAN Cluster"

  • Click on Alert Impact and select Impact: Efficiency (this means this alert definition will affect the efficiency badge)

  • Click Add Symptom Definitions (here you have to search for the symptom definitions that were created earlier and attach to this alert definition)

  • Drag both symptom definitions to the right-hand side as shown in the screenshot (make sure to choose "Any" as highlighted below)

  • Click Add Recommendations (here I added some sample recommendations) and click save

Similarly, create an alert definition for vSAN Cluster Write Latency alerts.


Now both alert definitions are created.


Let's verify current vSAN cluster Read/ Write latency in the dashboard.


As you can see above, Cluster I/O Write Latency is 2.67 ms which is greater than the warning threshold we defined. This means a warning alert should be produced and also should affect the efficiency badge of the vSAN Cluster object. An alert has already produced for this and can be seen in the second widget. It also shows the efficiency badge color is now yellow. If you click on the alert it will provide more details on the same.


If you browse the environment tab you can also notice that the efficiency badge of vSAN Cluster has turned to yellow.


Please feel free to share if this was useful. Cheers!

Related posts