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
a594dcdf
Commit
a594dcdf
authored
May 25, 2016
by
Bjoern Rabenstein
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove leftover from old behavior
parent
db247df0
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
5 deletions
+4
-5
operators.md
content/docs/querying/operators.md
+4
-5
No files found.
content/docs/querying/operators.md
View file @
a594dcdf
...
...
@@ -159,11 +159,10 @@ Example query:
method_code:http_errors:rate5m / ignoring(code) group_left method:http_requests:rate5m
In this case the left vector contains more than one entry per
`method`
label value. Thus,
we indicate this using
`group_left`
. To ensure that the result vector entries are unique, additional
labels have to be provided. Either
`code`
or
`source`
satisfy this requirement, but both
can be added for a more detailed result. The elements from the right side
are now matched with multiple elements with the same
`method`
label on the left:
In this case the left vector contains more than one entry per
`method`
label
value. Thus, we indicate this using
`group_left`
. The elements from the right
side are now matched with multiple elements with the same
`method`
label on the
left:
{method="get", code="500"} 0.04 // 24 / 600
{method="get", code="404"} 0.05 // 30 / 600
...
...
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