Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
C
Coredns
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Locked Files
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Security & Compliance
Security & Compliance
Dependency List
License Compliance
Packages
Packages
List
Container Registry
Analytics
Analytics
CI / CD
Code Review
Insights
Issues
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Railgun
Coredns
Commits
31fd9328
Commit
31fd9328
authored
Sep 08, 2019
by
Cricket Liu
Committed by
Miek Gieben
Sep 08, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Making README consistent, fixing "meta data" (#3244)
parent
878f9068
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
plugin/metadata/README.md
plugin/metadata/README.md
+6
-6
No files found.
plugin/metadata/README.md
View file @
31fd9328
...
...
@@ -2,25 +2,25 @@
## Name
*metadata*
- enable
a meta
data collector.
*metadata*
- enable
s a meta
data collector.
## Description
By enabling
*metadata*
any plugin that implements [metadata.Provider
interface](https://godoc.org/github.com/coredns/coredns/plugin/metadata#Provider) will be called for
each DNS query, at
beginning of the process for that query, in order to add its own meta
data to
each DNS query, at
the beginning of the process for that query, in order to add its own meta
data to
context.
The meta
data collected will be available for all plugins, via the Context parameter provided in the
The metadata collected will be available for all plugins, via the Context parameter provided in the
ServeDNS function. The package (code) documentation has examples on how to inspect and retrieve
metadata a plugin might be interested in.
The meta
data is added by setting a label with a value in the context. These labels should be named
The metadata is added by setting a label with a value in the context. These labels should be named
`plugin/NAME`
, where
**NAME**
is something descriptive. The only hard requirement the
*metadata*
plugin enforces is that the labels contain
s
a slash. See the documentation for
plugin enforces is that the labels contain a slash. See the documentation for
`metadata.SetValueFunc`
.
The value stored is a string. The empty string signals "no meta
data". See the documentation for
The value stored is a string. The empty string signals "no metadata". See the documentation for
`metadata.ValueFunc`
on how to retrieve this.
## Syntax
...
...
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