Metrics are indicators that allows you to quantify the performance and the applications status based on the analysis of exposed data from the own application and by the infrastructure tools.
CharlesCD allows you to get the metrics of all your circles, you will be able to see their health analysis and performances.
CharlesCD metrics are:
Metrics name | Description | Type of metric |
---|---|---|
istio_charles_request_total | Total amount of requests | Counter |
istio_charles_request_duration_seconds | Response time for each request | Histogram |
Each metric has a metadata range that allows a variety of filter and analysis types to be created. These metadata are described on the table below:
Metadata | Description | Type | Metrics that are present |
---|---|---|---|
source | POD name from which the request was made or 'unknown' if the request originates outside. | Text | istio_charles_request_total, istio_charles_request_duration_seconds |
destination_pod | POD's name where the targeted request went or unknown if the request was originated outside the mesh | Text | istio_charles_request_total, istio_charles_request_duration_seconds |
destination_host | Address where the request was made | Text | istio_charles_request_total, istio_charles_request_duration_seconds |
destination_component | Value on the label 'app' of the pod that received the request or unknown if there is no information about it. | Text | istio_charles_request_total, istio_charles_request_duration_seconds |
circle_id | 'x-circle-id' header that goes through the request or 'unknown' if the header is not present. | Text | istio_charles_request_total, istio_charles_request_duration_seconds |
circle_source | 'x-circle-source' header that is placed by the Envoy filter at the interception of each request. | Text | istio_charles_request_total, istio_charles_request_duration_seconds |
response_status | HTTP status of the response. | Numeric | istio_charles_request_total, istio_charles_request_duration_seconds |