Closed Bug 411360 Opened 18 years ago Closed 17 years ago

Add nagios script to monitor Socorro collector

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: samuel.sidler+old, Assigned: aravind)

References

()

Details

Attachments

(2 files)

Reported by bsmedberg, Jul 10, 2007 Provide a method for nagios to monitor the status of the collector. We should attempt to write to the filestore during it, instead of merely returning an "I'm alive" result. Sayrer, can you take this?
dupe of bug 411360 ?
(In reply to comment #1) > dupe of bug 411360 ? > err i mean bug 401810
Not a dupe, they are separate tiers. Aravind -- do you have a monitor already in place for this? If not, how do you want to go about checking the collector?
Assignee: nobody → aravind
You used to be able to GET https://crash-reports.mozilla.com/submit and get back a "405 method not allowed", but I guess we changed that? Looks like you can still HEAD it and get that, so maybe that's sufficient?
Aravind, any update here?
Target Milestone: --- → 0.5
Aravind, is there any nagios check for the collector?
Target Milestone: 0.5 → ---
Target Milestone: --- → 0.6
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
This isn't fixed, monitoring isn't there yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Aravind - can you post an update here and give an ETA for when a check could be put in place?
Aravind - can you post an update here and give an ETA for when a check could be put in place?
I will try and get something going this week.
All we need is a HEAD request on /submit to verify the 405 exists.
-> server-ops so this can get done
Assignee: aravind → server-ops
Component: Socorro → Server Operations
Product: Webtools → mozilla.org
QA Contact: socorro → mrz
Summary: Allow for nagios status monitoring of the collector → Add nagios script to monitor Socorro collector
Target Milestone: 0.6 → ---
Version: Trunk → other
Assignee: server-ops → aravind
This needs some support from webdev: 1) collector configuration to ignore the "nagios" product 2) sample dump file with post parameters to mimic a submission 3) curl command to submit said post to verify that a valid UUID is sent back Lars - could you provide instructions on 1) and I can provide the rest. Thanks.
Attachment #349050 - Attachment is patch: true
Attachment #349050 - Attachment mime type: application/octet-stream → text/plain
So, to run this: 1) unpack the test dump somewhere 2) cron to run the .sh in same cwd as the test dump At some point we can configure the collector to ignore submissions with Product=Nagios. Expected output is easy to parse: macnugget:td morgamic$ ./test.sh CrashID=bp-0b0ec860-85d7-438c-9a54-f8d720081119
to get collector to avoid queuing any submissions with "Nagios" as the product, add the line below to the list of throttle conditions in collectorconfig.py. This will cause the collector to place 100% of entries where Product == "Nagios" into deferred storage. It will still, however, return a uuid for the submission. ("Product", "Nagios", 0), # queue nothing where Product == "Nagios" #BEFORE: throttleConditions.default = [ # other conditions ... (None, True, 10) # queue 10% of what's left ] #AFTER: throttleConditions.default = [ ("Product", "Nagios", 0), # other conditions ... (None, True, 10) # queue 10% of what's left ]
s/Nagios/nagios/
Lars, is this a code change we can make in the default settings? If so it might be easier to deploy.
Morgamic: are you suggesting that I put it into the collectorconfig.py.dist file?
Eh, maybe not a good idea. I guess IT can figure out how to add the new rule. I was just remember we added the non-release version condition last week as well, but that's just another list member so it shouldn't be hard.
Done, now have the test script submitting a crash report and nagios verifying that we get a uuid back.
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
Sweet! Thanks Aravind -- have a good weekend.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: