3.2.107 SCPCustomRoamingProxyMaxViaHeaderProcessingCountExceeded
Table 3-111 SCPCustomRoamingProxyMaxViaHeaderProcessingCountExceeded
| Field | Details |
|---|---|
| Description | 'Proxy information count in Via header(s) exceeded the maximum via header proxy processing Limit.' |
| Summary | 'Proxy information count in Via header(s) exceeded the maximum via header proxy processing Limit. max_via_header_processing_limit:{{$labels.max_via_header_processing_limit}}, namespace: {{$labels.labels.kubernetes_namespace}}, podname: {{$labels.kubernetes_pod_name}}, timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }}' |
| Severity | Info |
| Condition |
This alert is raised when the Via header processing count for Custom Roaming Proxy exceeds the configured limit. increase(ocscp_worker_custom_roaming_proxy_via_header_limit_exceeded_total[2m]) > 0 |
| OID |
1.3.6.1.4.1.323.5.3.35.1.2.15044 |
| Metric Used | increase(ocscp_worker_custom_roaming_proxy_via_header_limit_exceeded_total |
| Recommended Action |
Cause: When the Custom Roaming Proxy maximum Via header processing count exceeded the configured limit. Diagnostic Information: Check if the number of Via headers in ingress request is not exceeding the configured limit in configuration for Custom Roaming Proxy. Recovery: This alert is cleared automatically when the request has less Via header than the configured limit per request for Custom Roaming Proxy. For any assistance, contact My Oracle Support. |