Ingresses

An ingress exposes HTTP and HTTPS routes from outside the cluster to the services within the cluster. It routes traffic based on rules defined in the ingress resource.

The Observe page displays the list of all the Kubernetes® Infrastructure entities. You click Ingresses to view the list of ingresses used in the Kubernetes cluster.

You can view the metrics when you connect the Cisco Cloud Observability Kubernetes Collectors to Cisco Cloud Observability through the installation process. See Install Kubernetes and App Service Monitoring.

On the Ingresses page, you can use the k8s.cluster.id attribute in the Filter View field to observe entity details for a cluster that does not have a unique name. In the filter, specify the value of this attribute as the UUID of the kube-system namespace. For example, attributes(k8s.cluster.id) = valueOfClusterId

Ensure that you have configured the ingressControllers parameter in the collectors-values.yaml file.

Currently, the Ingresses page displays only the Nginx type ingress controller that Kubernetes manages. However, if you do not specify the value for ingressControllers within the collectors-values.yaml file, the metrics may not display.
When you have a wildcard domain ingress, no metrics are displayed for that ingress. To get the metrics you need to run the ingress controller with --metrics-per-host=false .
If you are using the AWS or the Azure Load balancer type ingress controller, you can observe the details related to the specific ingress controller on the Load Balancers page. To view Load Balancers related to a specific AWS or Azure ingress controller, from the Ingresses details page go to Relationships > Load Balancers and select the corresponding load balancers.
Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress).

The left pane shows the relationships of Ingresses to the other entities such as cluster, namespace, and so on.

Detail View

To view the details of a specific ingress resource, you can click the name of the ingress resource. The detail view displays metrics, key performance indicators, and properties (attributes) related to the ingress that you select.

Metrics and Key Performance Indicators

Cisco Cloud Observability displays the following metrics and key performance indicators (KPIs) for Kubernetes Ingresses list and detail views:

Metrics	Description
Calls Per Minute	The number of requests sent from ingress to the services in one-minute duration. In detail view, you can click Show Services to view the detailed breakdown of the metrics by using a line graph.	list, detail
Errors Per Minute	The application errors found in the one-minute timeframe, which reports to the ingress resource. In detail view, you can click Show Services to view the detailed breakdown of the metrics by using a line graph.	list, detail
Average Latency per request (ms)	The average time delay in getting the response from the application/service for each request. You can click Show Services to view the detailed breakdown of the metrics by using a line graph.	detail
HTTP XXX Counts	The count of the occurrences of 2xx, 3xx, 4xx, and 5xx status response codes.	detail
HTTP 5XX Errors	The error response code counts for the 5xx error responses.	detail
Health	The health of the entity. For the health status, see Observe Kubernetes Entities.	list
Name	The name of the ingress resource used.	list
Cluster	The name of the cluster that uses the corresponding ingress resource.	list
Namespace	The namespace in which the ingress is deployed.	list
Type	The type of the ingress controller. This can be AWS, Nginx, or Azure. This value is determined based on the ingress class that you have used during the Ingress service creation. Currently, Kubernetes Infrastructure Collector detects the types only for these types of controllers: Nginx controller (maps to Nginx) AWS Load Balancer controller (maps to AWS) Azure gateway ingress controller (maps to Azure) Azure HTTP application routing (maps to Azure)	list
Errors Per Minute	The application errors found in a one-minute timeframe.	list
Latency (ms)	The average time delay in getting the response from the application/service for each request.	list

Properties (Attributes)

Clicking an ingress Name displays the detail view with the Properties panel on the right. The Properties panel displays the following properties (attributes) for ingresses:

Property	Description
Name	The name of the Ingress service.
Cluster	The name of the cluster on which the ingress is running.
Class	The class of the ingress resource that you define during the ingress configuration.
Type	The type of the ingress controller. This can be AWS, Nginx, or Azure. The ingress class that you use during the ingress service creation determines this value. The Kubernetes Infrastructure Collector detects the types only for these types of controllers: Nginx controller (maps to Nginx) AWS Load Balancer controller (maps to AWS) Azure gateway ingress controller (maps to Azure) Azure HTTP application routing (maps to Azure) Currently, the metric details for the Azure ingress controller type do not display. For the AWS ingress controller type, you can observe the details on the related Load Balancers page.

The Properties panel shows limited metadata.

Annotations

The right pane displays the Kubernetes annotations. These can also be the Kubernetes system-generated annotation attributes.

Retention and Purge Time-to-Live (TTL)

See Retention and Purge Time-to-Live (TTL).

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Download PDF