Istio

if you use istio as a service mesh and/or for ingress, opsverse's agents are pre configured to easily pull metrics from the istio components the observability section https //istio io/latest/docs/concepts/observability/ of the official istio documentation provides a good overview metrics metrics are automatically collected by the opsverse metrics agent this document https //istio io/latest/docs/examples/microservices istio/logs istio/ has info about some common metrics generated by istio components logs use the meshconfig options to enable and configure access logs you can also choose between json and text by setting accesslogencoding to json or text you can customize the format of the access log by setting accesslogformat istio uses envoy as the proxy component this document https //www envoyproxy io/docs/envoy/latest/configuration/observability/access log/usage#format rules has details of envoy access logs traces istio can be configured to generate apm traces this document https //istio io/latest/docs/tasks/observability/distributed tracing/ has all the necessary info note that the opsverse otel collector is available in your k8s cluster at http //otel collector devopsnow\ svc cluster local 9411 visualization once the required telemetry is enabled, the istio ingress gateway dashboard that is pre packaged with your observenow stack can be used to visualize incoming traffic