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: api/flowmetrics/v1alpha1/flowmetric_types.go
-4Lines changed: 0 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -76,10 +76,6 @@ type FlowMetricSpec struct {
76
76
// +required
77
77
TypeMetricType`json:"type"`
78
78
79
-
// Help text of the metric, as it appears in Prometheus.
80
-
// +optional
81
-
Helpstring`json:"help,omitempty"`
82
-
83
79
// `valueField` is the flow field that must be used as a value for this metric (for example: `Bytes`). This field must hold numeric values.
84
80
// Leave empty to count flows rather than a specific value per flow.
85
81
// Refer to the documentation for the list of available fields: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/network_observability/json-flows-format-reference.
Copy file name to clipboardExpand all lines: docs/FlowMetric.md
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,13 +152,6 @@ Refer to the documentation for the list of available fields: https://docs.redhat
152
152
For instance, when flattening `Interfaces` on a bytes counter, a flow having Interfaces [br-ex, ens5] increases one counter for `br-ex` and another for `ens5`.<br/>
153
153
</td>
154
154
<td>false</td>
155
-
</tr><tr>
156
-
<td><b>help</b></td>
157
-
<td>string</td>
158
-
<td>
159
-
Help text of the metric, as it appears in Prometheus.<br/>
0 commit comments