You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: receiver/vcenterreceiver/README.md
+1-28Lines changed: 1 addition & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -59,31 +59,4 @@ Details about the metrics produced by this receiver can be found in [metadata.ya
59
59
60
60
### Feature gates
61
61
62
-
#### Performance metrics dimensions
63
-
64
-
These metrics were incorrectly dimensioned previously but the desired fix is a breaking change. To avoid breaking existing users, this feature gate is used to control whether the dimensions are fixed or not. This feature gate is planned to removed in two months.
65
-
66
-
- `vcenter.vm.network.throughput`
67
-
- `vcenter.vm.network.usage`
68
-
- `vcenter.vm.network.packet.count`
69
-
- `vcenter.vm.disk.latency.avg`
70
-
- `vcenter.vm.disk.latency.max`
71
-
- `vcenter.host.network.usage`
72
-
- `vcenter.host.network.throughput`
73
-
- `vcenter.host.network.packet.count`
74
-
- `vcenter.host.network.packet.errors`
75
-
- `vcenter.host.disk.latency.avg`
76
-
- `vcenter.host.disk.latency.max`
77
-
- `vcenter.host.disk.throughput`
78
-
79
-
These metrics were improperly dimensioned and needed another metric attribute `object` in order to properly dimension the data.
80
-
81
-
#### v0.93.0, January 2024
82
-
83
-
- The receiver will emit the `object` metric attribute by default
84
-
- `receiver.vcenter.emitPerfMetricsWithObjects`is *enabled* by default.
85
-
86
-
#### v0.95.0, February 2024
87
-
88
-
- The feature gates are removed.
89
-
- Performance metrics will always include the `object` metric attribute.
62
+
The `receiver.vcenter.emitPerfMetricsWithObjects` is now stable and will be removed in v0.97.0.
0 commit comments