Receiver Creator
This receiver can instantiate other receivers at runtime based on whether
observed endpoints match a configured rule. To use the receiver creator, you
must first configure one or more
observers that will discover networked
endpoints that you may be interested in. The configured rules will be
evaluated for each endpoint discovered. If the rule evaluates to true then
the receiver for that rule will be started against the matched endpoint.
Configuration
watch_observers
A list of observers previously defined to be run in the extensions
section.
receiver_creator will watch for endpoints generated by these observers.
receivers
A map of receiver names (e.g. redis/1
) to a template for when and how to
instantiate that receiver.
receivers.<receiver_type/id>.rule
Rule expression using expvar
syntax.
Variables available are detailed below in Rule
Expressions.
receivers.<receiver_type/id>.config
This is configuration that will be used when creating the receiver at
runtime.
This option can use static and dynamic configuration values. Static values
are normal YAML values. However, the value can also be dynamically constructed
from the discovered endpoint object. Dynamic values are surrounded by
backticks (`). If a literal backtick is needed use \` to escape it. Dynamic
values can be used with static values in which case they are concatenated.
For example:
config:
secure_url: https://`pod.labels["secure_host"]`
The value of secure_url
will be https://
concatenated with the value of
the secure_host
label.
This can also be used when the discovered endpoint needs to be changed
dynamically. For instance, suppose the IP 1.2.3.4
is discovered without a
port but the port needs to be set inside endpoint. You could do:
config:
endpoint: '`endpoint`:8080'
receivers.<receiver_type/id>.resource_attributes
This setting controls what resource attributes are set on metrics emitted from the created receiver. These attributes can be set from values in the endpoint that was matched by the rule
. These attributes vary based on the endpoint type. These defaults can be disabled by setting the attribute to be removed to an empty value. Note that the values can be dynamic and processed the same as in config
.
Note that the backticks below are not typos--they indicate the value is set dynamically.
type == "pod"
Resource Attribute |
Default |
k8s.pod.name |
`name` |
k8s.pod.uid |
`uid` |
k8s.namespace.name |
`namespace` |
type == "port"
Resource Attribute |
Default |
k8s.pod.name |
`pod.name` |
k8s.pod.uid |
`pod.uid` |
k8s.namespace.name |
`pod.namespace` |
type == "hostport"
None
See redis/2
in examples.
Rule Expressions
Each rule must start with type == ("pod"|"port"|"hostport") &&
such that the rule matches
only one endpoint type. Depending on the type of endpoint the rule is
targeting it will have different variables available.
Pod
Variable |
Description |
type |
"pod" |
name |
name of the pod |
namespace |
namespace of the pod |
uid |
unique id of the pod |
labels |
map of labels set on the pod |
annotations |
map of annotations set on the pod |
Port
Variable |
Description |
type |
"port" |
name |
container port name |
port |
port number |
protocol |
The transport protocol ("TCP" or "UDP") |
pod.name |
name of the owning pod |
pod.namespace |
namespace of the pod |
pod.uid |
unique id of the pod |
pod.labels |
map of labels of the owning pod |
pod.annotations |
map of annotations of the owning pod |
Host Port
Variable |
Description |
type |
"hostport" |
process_name |
Name of the process |
command |
Command line with the used to invoke the process |
is_ipv6 |
true if endpoint is IPv6, otherwise false |
port |
Port number |
transport |
The transport protocol ("TCP" or "UDP") |
Examples
extensions:
# Configures the Kubernetes observer to watch for pod start and stop events.
k8s_observer:
host_observer:
receivers:
receiver_creator/1:
# Name of the extensions to watch for endpoints to start and stop.
watch_observers: [k8s_observer]
receivers:
prometheus_simple:
# Configure prometheus scraping if standard prometheus annotations are set on the pod.
rule: type == "pod" && annotations["prometheus.io/scrape"] == "true"
config:
metrics_path: '`"prometheus.io/path" in annotations ? annotations["prometheus.io/path"] : "/metrics"`'
endpoint: '`endpoint`:`"prometheus.io/port" in annotations ? annotations["prometheus.io/port"] : 9090`'
redis/1:
# If this rule matches an instance of this receiver will be started.
rule: type == "port" && port == 6379
config:
# Static receiver-specific config.
password: secret
# Dynamic configuration value.
collection_interval: `pod.annotations["collection_interval"]`
resource_attributes:
# Dynamic configuration value.
service.name: `pod.labels["service_name"]`
redis/2:
# Set a resource attribute based on endpoint value.
rule: type == "port" && port == 6379
resource_attributes:
# Dynamic value.
app: `pod.labels["app"]`
# Static value.
source: redis
receiver_creator/2:
# Name of the extensions to watch for endpoints to start and stop.
watch_observers: [host_observer]
receivers:
redis/on_host:
# If this rule matches an instance of this receiver will be started.
rule: type == "port" && port == 6379 && is_ipv6 == true
resource_attributes:
service.name: redis_on_host
processors:
exampleprocessor:
exporters:
exampleexporter:
service:
pipelines:
metrics:
receivers: [receiver_creator/1, receiver_creator/2]
processors: [exampleprocessor]
exporters: [exampleexporter]
extensions: [k8s_observer, host_observer]
The full list of settings exposed for this receiver are documented here
with detailed sample configurations here.