Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
D
docs
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Administrator
docs
Commits
43ab93fb
Commit
43ab93fb
authored
Mar 02, 2016
by
Patrick Bogen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update docs for k8s pods sd
parent
7ee4c031
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
9 deletions
+17
-9
configuration.md
content/docs/operating/configuration.md
+17
-9
No files found.
content/docs/operating/configuration.md
View file @
43ab93fb
...
...
@@ -309,18 +309,19 @@ feature to replace the special `__address__` label.
CAUTION: Kubernetes SD is in beta: breaking changes to configuration are still
likely in future releases.
Kubernetes SD configurations allow retrieving scrape targets from
[
Kubernetes'
](
http://kubernetes.io/
)
REST API. By default, this discovers
API servers, nodes, and appropriately annotated services so that metrics from both
cluster components and deployed applications can be scraped. This will create
multiple target groups: one for all API servers with each API server as a target, one
for all nodes with each node as a target, and one for each service containing
each service endpoint as a target.
Kubernetes SD configurations allow retrieving scrape targets from
[
Kubernetes'
](
http://kubernetes.io/
)
REST API. By default, this discovers API
servers, nodes, pods, and appropriately annotated services so that metrics from
both cluster components and deployed applications can be scraped. This will
create multiple target groups: one for all API servers with each API server as a
target, one for all nodes with each node as a target, one for each service
containing each service endpoint as a target; and one for all pods with each
(Pod,ContainerPort) tuple as a target, both with and without HTTPS.
The following meta labels are available on targets during relabeling:
*
`__meta_kubernetes_role`
: the role of the target: one of
`apiserver`
,
`node`
or
`service`
*
`__meta_kubernetes_role`
: the role of the target: one of
`apiserver`
,
`endpoint`
,
`node`
,
`pod`
or
`service`
*
`__meta_kubernetes_node_label_<labelname>`
: each node label from the
Kubernetes API
*
`__meta_kubernetes_service_namespace`
: the namespace of the service
...
...
@@ -329,6 +330,13 @@ Kubernetes API
Kubernetes API
*
`__meta_kubernetes_service_annotation_<annotationname>`
: each service
annotation from the Kubernetes API
*
`__meta_kubernetes_pod_name`
: the name of the pod
*
`__meta_kubernetes_pod_namespace`
: the namespace of the service
*
`__meta_kubernetes_pod_address`
: the PodIP of the pod
*
`__meta_kubernetes_pod_label_<labelname>`
: each pod label from the Kubernetes
API
*
`__meta_kubernetes_pod_annotation_<annotationname>`
: each pod annotation from
the Kubernetes API
In addition, the
`instance`
label for node metrics will be set to the node name
as retrieved from the API server.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment