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
70ae3c95
Commit
70ae3c95
authored
Feb 27, 2019
by
Sebastian Melchior
Committed by
Brian Brazil
Feb 27, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
improve group_by docs (#1298)
Signed-off-by:
Sebastian Melchior
<
sebastian@melchior.me
>
parent
f52efea5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
0 deletions
+10
-0
configuration.md
content/docs/alerting/configuration.md
+10
-0
No files found.
content/docs/alerting/configuration.md
View file @
70ae3c95
...
...
@@ -128,6 +128,16 @@ current node.
```
yaml
[
receiver
:
<string>
]
# The labels by which incoming alerts are grouped together. For example,
# multiple alerts coming in for cluster=A and alertname=LatencyHigh would
# be batched into a single group.
#
# To aggregate by all possible labels use the special value '...' as the sole label name, for example:
# group_by: ['...']
# This effectively disables aggregation entirely, passing through all
# alerts as-is. This is unlikely to be what you want, unless you have
# a very low alert volume or your upstream notification system performs
# its own grouping.
[
group_by
:
'
['
<labelname>
,
... '
]
'
]
#
Whether
an
alert
should
continue
matching
subsequent
sibling
nodes.
...
...
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