istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify the definition of a handler. (#3557)

This commit is contained in:
Martin Taillefer 2019-03-07 10:15:33 -08:00 committed by istio-bot
parent eab78670ea
commit 9e1aa817ad
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/docs/concepts/policies-and-telemetry/index.md
View File

@ -190,10 +190,10 @@ A given adapter may support any number of templates.
Adapters encapsulate the logic necessary to interface Mixer with specific external infrastructure Adapters encapsulate the logic necessary to interface Mixer with specific external infrastructure
backends such as [Prometheus](https://prometheus.io) or [Stackdriver](https://cloud.google.com/logging). backends such as [Prometheus](https://prometheus.io) or [Stackdriver](https://cloud.google.com/logging).
Individual adapters generally need operational parameters in order to do their work. For example, a logging adapter may require A _handler_ is a resource responsible for holding the configuration state needed by an adapter. For example, a
the IP address and port of the log collection backend. logging adapter may require the IP address and port of the log collection backend.
Here is an example showing how to configure an adapter of kind = `listchecker`. The `listchecker` adapter checks an input value against a list. Here is an example showing how to create a handler for an adapter of kind = `listchecker`. The `listchecker` adapter checks an input value against a list.
If the adapter is configured for a whitelist, it returns success if the input value is found in the list. If the adapter is configured for a whitelist, it returns success if the input value is found in the list.
{{< text yaml >}} {{< text yaml >}}