disk_read and disk_write_metrics_datastrore_powercli

[jvm2016]

Hi Luc,

are threre metrics like disk read and disk write against which we run stats as we did in one of the last posts for network .?

[LucD]

Àll metrics can be found under the PerformanceManager page.

In this case I asusme you want to look at the vDisk metrics, more specifically the virtualDisk.read.average and the virtualDisk,write.average..

[jvm2016]

so we are in process of setting threshold for alert of following descriptions . do yu think we need to put threshold for such metrics or in other words consider them as part of monitoring .

disk read activity is high: 7565 KBps on naa.60a980002d657037693f424e3457734

disk write activity is high: 3465 KBps on naa.60a980002d657037693f345678774733

and iam still thinking how to decide thresholds as the same case with network.

i think vrops with its analytics engine can give us much better result as it will comapre with what is normal over a perios of time .

[LucD · Accepted solution]

In that case you probably should be looking at the datastore.read.average and datastore.write.average metrics.

And yes, vROps will make your life easier, since it comes preloaded with general rules on what to capture and what to watch.

To fine tune it further, you will have to make modifications in vROPs as well.

Again it depends on your environment how well the vROps default settings work out for you.

[jvm2016]

thnaks i am checking this .

are you using postman  client will it be comparable to powercli or any convenience  over powercli or web client.

i was chekcing kyle rudy video where in http based requeset were sent in json format  tp perform many operations as we do in webclient or with powercli.

is it correct to say that postman client for rest api using Jason as data format   and powercli is based on Soap??

sorry little deviated from our original topicbut thinking if postman client can be more convenint for such operations over polwercli.

[LucD]

The vSphere API are based on SOAP, but they are converting to REST API.

See also Kyle's post Getting Started with the vSphere Automation SDK for REST

Currently PowerCLI already uses some of the REST API, the Tag related cmdlet are all based on the REST API.

Further, you can easily access the REST API from PowerCLI for the VAMI by using the Connect-CisServer and Get-CisService cmdlets.

These are in fact wrappers around the raw REST API.

William did a series of posts around that, see Exploring new VCSA VAMI API w/PowerCLI: Part 1

The REST API mostly uses the JSON format to pass parameters to the REST API calls.

And the results of the calls are also mostly returned in the JSON format.

Postman is an interactive tool to compose JSON objects and call REST API.

But there are other REST API clients available as well, in fact several as extensions for the Chrome browser.

And vSphere comes with a builtin API Explorer.

See Getting Started with vSphere’s API Explorer

[jvm2016]

Thanks  iam checking these posts.