The world of service meshes and API gateways opens new possibilities for collecting tracing data from your production infrastructure.
While the data from service meshes and API gateways cannot match the level of detail and granularity that can be achieved through code-level instrumentation, it can be a good first step along the observability journey.
Most, if not all, service meshes and API gateways have distributed tracing capabilities baked in, allowing telemetry data to be sent to Honeycomb with relative ease.
Istio supports tracing out of the box using either the Zipkin or Jaeger format.
To send the data to Honeycomb:
global.tracer.zipkin.address setting to point at the OpenTelemetry Collector, using Istio’s distributed tracing documentation.To properly trace all services in your system, ensure that you are forwarding tracing headers from your apps so that Istio can inject the correct tracing information as requests are made and received. For more details, visit the Istio docs on trace context propagation.
Here is an example configuration to update MeshConfig that may be passed in as a separate file with the install command istioctl install --set profile=demo -y -f ./tracing.yaml:
# tracing.yaml
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
name: mesh-default
namespace: istio-system
spec:
meshConfig:
enableTracing: true
defaultConfig:
tracing:
zipkin:
address: otel-collector.default:9411
sampling: 100
---
AWS App Mesh supports tracing out of the box using the Jaeger format.
To send the data to Honeycomb:
tracing.address and tracing.port settings to point at the OpenTelemetry Collector, using App Mesh’s Jaeger documentation. Ambassador supports tracing out of the box using the Zipkin format.
To send the data to Honeycomb:
service setting to point at the OpenTelemetry Collector, using Ambassador’s Zipkin documentation. Kong supports tracing out of the box using the Zipkin format.
To send the data to Honeycomb:
config.http_endpoint setting to point at the OpenTelemetry Collector, using Kong’s Zipkin documentation.config.header_type to w3c for best interoperability with OpenTelemetry.