Performance Manager Update Perf Interval
Modifies VirtualCenter Server's built-in historical intervals, within certain limits.
Supported Modifications
| key | samplingPeriod | length | name | level \[1\] | enabled \[2\] |
|---|---|---|---|---|---|
| 1 | 300 \[3\] | 86400 \[4\] | Past day | 1 | true |
| 2 | 1800 | 604800 | Past week | 1 | true |
| 3 | 7200 | 2592000 | Past month | 1 | true |
| 4 | 86400 | 31536000 \[5\] | Past year | 1 | true |
[1] The collection level for the historical intervals can be changed. However,
the level specified for a lower-numbered interval cannot be smaller
than that of a larger interval.
[2] An interval can be disabled. By default, all four
intervals are enabled. Disabling an interval disables all higher
intervals. For example, disabling interval 3 (“Past month”)
also disables interval 4 (“Past year”).
[3] Can reduce this interval’s samplingPeriod from 5 minutes to 1, 2, or 3
minutes.
[4] Can increase this interval’s length from 1 day to 2 or 3 days.
[5] Can increase interval’s length from 1 year to 2 or 3 years.
See PerfInterval for information about the four default intervals for VirtualCenter Server.
Required privileges: Performance.ModifyIntervals
The unique identifier for the managed object to which the method attaches; the serialized managed object reference for a request has the form moType/moId, in this case PerformanceManager/{moId}.
The vSphere release schema. The current specification covers vSphere 9.0.0.0 APIs.
"UpdatePerfIntervalRequestType Object"The historical interval being modified, a complete data object comprising values for PerfInterval.enabled, interval ID, PerfInterval.length of time to maintain statistics for this interval in the database, PerfInterval.level, PerfInterval.name, and PerfInterval.samplingPeriod properties.
No Content
curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '[{}]' https://{api_host}/sdk/vim25/{release}/PerformanceManager/{moId}/UpdatePerfInterval