Analytics1
The Analytics template is used to dispatch runtime telemetry to Apigee.
Mixer templates are used to send data to individual adapters.
The Analytics template is used to dispatch runtime telemetry to Apigee.
A template that represents a single API key.
A template used to represent an access control query.
A template that carries no data, useful for testing.
A template designed to report observed communication edges between workloads.
A template that is used to control the production of Kubernetes-specific attributes.
A template designed to let you perform list checking operations.
A template that represents a single runtime log entry.
A template that represents a single runtime metric.
A template that represents a quota allocation request.
A template that carries no data, useful for testing.
A template that represents an individual span within a distributed trace.
The table below shows the set of adapters13 that implement each supported template.
Template | Adapters |
---|---|
Analytics1 | Apigee14 |
API Key2 | |
Authorization3 | Apigee14, OPA15 |
Check Nothing4 | Denier16 |
Edge5 | |
Kubernetes6 | Kubernetes Env17 |
List Entry7 | Denier16, List18 |
Log Entry8 | Fluentd19, SolarWinds20, Stackdriver21, Stdio22 |
Metric9 | Circonus23, CloudWatch24, Datadog25, Layer526, New Relic27, Prometheus28, SolarWinds20, Stackdriver21, StatsD29, Stdio22, Wavefront by VMware30 |
Quota10 | Denier16, Memory quota31, Redis Quota32 |
Report Nothing11 | |
Trace Span12 | New Relic27, Stackdriver21, Zipkin33 |