Ambassador (Emissary-ingress)

opsverse's telemetry agents are pre configured to collect telemetry from ambassador components this document provides info about configuring your amabassador installation to emit metrics, logs and traces additionally, https //www getambassador io/docs/edge stack/latest/howtos/prometheus/ offers a general overview metrics include the following annotations in your ambassador pod if you are making use of the official ambassador helm chart, you can achieve this by setting the following in the vaules yaml file podannotations prometheus io/scrape 'true' prometheus io/port '8877' logs the recommended format for logging is json logging related customizations can be set using the following configurations apiversion getambassador io/v3alpha1 kind module metadata name ambassador spec config envoy log type json envoy log format { "upstream service time" "%resp(x envoy upstream service time)%", "method" "%req(\ method)%", "request id" "%req(x request id)%", "downstream local address" "%downstream local address%", "x forwarded for" "%req(x forwarded for)%", "path" "%req(x envoy original path?\ path)%", "downstream remote address" "%downstream remote address%", "upstream cluster" "%upstream cluster%", "authority" "%req(\ authority)%", "start time" "%start time%", "bytes received" "%bytes received%", "response flags" "%response flags%", "requested server name" "%requested server name%", "response code" "%response code%", "upstream host" "%upstream host%", "protocol" "%protocol%", "bytes sent" "%bytes sent%", "upstream transport failure reason" "%upstream transport failure reason%", "upstream local address" "%upstream local address%", "user agent" "%req(user agent)%", "duration" "%duration%", "x b3 traceid" "%req(x b3 traceid)%", "trace id" "%req(x b3 traceid)%", "x b3 parentspanid" "%req(x b3 parentspanid)%", "x b3 spanid" "%req(x b3 spanid)%", "x b3 sampled" "%req(x b3 sampled)%" } tracing ambassador components can be configured to emit apm traces with the following configuration apiversion getambassador io/v3alpha1 kind tracingservice metadata name tracing spec service "http //otel collector devopsnow\ svc cluster local 9411" driver zipkin config {} \# tag headers \# "\ authority" \# "\ path" \# sampling \# overall 100 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 ambassador dashboard that is pre packaged with your observenow stack can be used to visualize incoming traffic