Closed
Bug 909073
Opened 11 years ago
Closed 11 years ago
bagheera ganglia monitoring
Categories
(Infrastructure & Operations :: Infrastructure: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: schintalapani, Assigned: rbryce)
Details
Hi, For bagheera nodes nagios alerts currently we have threshold 0 on bagheera.http.telemetry.requests.1MinuteRate. We only get alerts only if the rate gets to 0. Can we make this to get an alert if the rate gets below 10. Thank you, Harsha
Reporter | ||
Comment 2•11 years ago
|
||
since telemetry data point going away. can we make this alert from bagheera.http.metrics.requests.1MinuteRate and if the request rate goes below 40 have a alert triggered. Thanks, Harsha
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Harsha [:harsha] from comment #2) > since telemetry data point going away. can we make this alert from > bagheera.http.metrics.requests.1MinuteRate and if the request rate goes > below 40 have a alert triggered. > Thanks, > Harsha Sure. Does 40 represent a critical alert, as in action needs to be taken? We prefer to set warning and critical thresholds when we can.
Reporter | ||
Comment 4•11 years ago
|
||
sorry I mean to say if the rate falls below 40 requests per sec not 40% of requests. 40 requests per sec is not critical but its something we as a dev/engineer might need to look into it. So you can put it as warning. Thanks, Harsha
Assignee | ||
Comment 5•11 years ago
|
||
I didn't realize at the time, these alerts only go to the devs. This is configured the same way the other bagheera checks are configured, with one threshold. Alert will now notify @ below 40 qps.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Component: Infrastructure: Monitoring → Infrastructure: Other
You need to log in
before you can comment on or make changes to this bug.
Description
•