bagheera ganglia monitoring

RESOLVED FIXED

Status

Infrastructure & Operations
Infrastructure: Other
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: harsha, Assigned: rbryce)

Tracking

Details

(Reporter)

Description

5 years ago
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

Comment 1

5 years ago
Rick: is this something you can set up? Thanks!
Assignee: infra → rbryce
(Reporter)

Comment 2

5 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

5 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

5 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

5 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
Last Resolved: 5 years ago
Resolution: --- → FIXED
Component: Infrastructure: Monitoring → Infrastructure: Other
Product: Infrastructure & Operations → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.