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
7e6a59da
Commit
7e6a59da
authored
Jun 06, 2017
by
Julius Volz
Committed by
GitHub
Jun 06, 2017
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #763 from cgroschupp/openstack_sd_docu
Added OpenStack service discovery docs.
parents
1a14e6dd
0a62417f
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
66 additions
and
0 deletions
+66
-0
configuration.md
content/docs/operating/configuration.md
+66
-0
No files found.
content/docs/operating/configuration.md
View file @
7e6a59da
...
@@ -176,6 +176,10 @@ dns_sd_configs:
...
@@ -176,6 +176,10 @@ dns_sd_configs:
ec2_sd_configs:
ec2_sd_configs:
[ - <ec2_sd_config> ... ]
[ - <ec2_sd_config> ... ]
# List of OpenStack service discovery configurations.
openstack_sd_configs:
[ - <openstack_sd_config> ... ]
# List of file service discovery configurations.
# List of file service discovery configurations.
file_sd_configs:
file_sd_configs:
[ - <file_sd_config> ... ]
[ - <file_sd_config> ... ]
...
@@ -399,6 +403,68 @@ region: <string>
...
@@ -399,6 +403,68 @@ region: <string>
[ port: <int> | default = 80 ]
[ port: <int> | default = 80 ]
```
```
### `<openstack_sd_config>`
CAUTION: OpenStack SD is in beta: breaking changes to configuration are still
likely in future releases.
OpenStack SD configurations allow retrieving scrape targets from OpenStack Nova
instances.
The following meta labels are available on targets during
[
relabeling
](
#relabel_config
)
:
*
`__meta_openstack_instance_id`
: the OpenStack instance ID
*
`__meta_openstack_instance_name`
: the OpenStack instance name
*
`__meta_openstack_instance_status`
: the status of the OpenStack instance
*
`__meta_openstack_instance_flavor`
: the flavor of the OpenStack instance
*
`__meta_openstack_public_ip`
: the public IP of the OpenStack instance
*
`__meta_openstack_private_ip`
: the private IP of the OpenStack instance
*
`__meta_openstack_tag_<tagkey>`
: each tag value of the instance
See below for the configuration options for OpenStack discovery:
```
# The information to access the OpenStack API.
# The OpenStack Region.
region: <string>
# identity_endpoint specifies the HTTP endpoint that is required to work with
# the Identity API of the appropriate version. While it's ultimately needed by
# all of the identity services, it will often be populated by a provider-level
# function.
[ identity_endpoint: <string> ]
# username is required if using Identity V2 API. Consult with your provider's
# control panel to discover your account's username. In Identity V3, either
# userid or a combination of username and domain_id or domain_name are needed.
[ username: <string> ]
[ userid: <string> ]
# password for the Identity V2 and V3 APIs. Consult with your provider's
# control panel to discover your account's preferred method of authentication.
[ password: <string> ]
# At most one of domain_id and domain_name must be provided if using username
# with Identity V3. Otherwise, either are optional.
[ domain_name: <string> ]
[ domain_id: <string> ]
# The project_id and project_name fields are optional for the Identity V2 API.
# Some providers allow you to specify a project_name instead of the project_id.
# Some require both. Your provider's authentication policies will determine
# how these fields influence authentication.
[ project_name: <string> ]
[ project_id: <string> ]
# Refresh interval to re-read the instance list.
[ refresh_interval: <duration> | default = 60s ]
# The port to scrape metrics from. If using the public IP address, this must
# instead be specified in the relabeling rule.
[ port: <int> | default = 80 ]
```
### `<file_sd_config>`
### `<file_sd_config>`
File-based service discovery provides a more generic way to configure static targets
File-based service discovery provides a more generic way to configure static targets
...
...
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