Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
d0508c7e
Commit
d0508c7e
authored
Feb 01, 2019
by
wojtekt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Adjust buckets in apiserver request latency metrics
parent
a3c14ecf
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
2 deletions
+5
-2
metrics.go
...ing/src/k8s.io/apiserver/pkg/endpoints/metrics/metrics.go
+5
-2
No files found.
staging/src/k8s.io/apiserver/pkg/endpoints/metrics/metrics.go
View file @
d0508c7e
...
...
@@ -72,8 +72,11 @@ var (
prometheus
.
HistogramOpts
{
Name
:
"apiserver_request_latency_seconds"
,
Help
:
"Response latency distribution in seconds for each verb, group, version, resource, subresource, scope and component."
,
// Use buckets ranging from 125 ms to 8 seconds.
Buckets
:
prometheus
.
ExponentialBuckets
(
0.125
,
2.0
,
7
),
// This metric is used for verifying api call latencies SLO,
// as well as tracking regressions in this aspects.
// Thus we customize buckets significantly, to empower both usecases.
Buckets
:
[]
float64
{
0.05
,
0.1
,
0.15
,
0.2
,
0.25
,
0.3
,
0.35
,
0.4
,
0.45
,
0.5
,
0.6
,
0.7
,
0.8
,
0.9
,
1.0
,
1.25
,
1.5
,
1.75
,
2.0
,
2.5
,
3.0
,
3.5
,
4.0
,
4.5
,
5
,
6
,
7
,
8
,
9
,
10
,
15
,
20
,
25
,
30
,
40
,
50
,
60
},
},
[]
string
{
"verb"
,
"group"
,
"version"
,
"resource"
,
"subresource"
,
"scope"
,
"component"
},
)
...
...
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