Closed Bug 494003 Opened 15 years ago Closed 13 years ago

Developer profile/dashboard of Socorro Cacti and Nagios monitoring

Categories

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

All
Other
task
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ozten, Assigned: rtucker)

References

Details

Aravind per our discussion during the Postgres work week:

Once cactus and nagios monitoring is setup, you are going to create a view that Socorro developers can use to monitor the production system and diagnose issues.
Depends on: 465687
Summary: Developer profile/dashboard of Socorro Cactus and Nagios monitoring → Developer profile/dashboard of Socorro Cacti and Nagios monitoring
Moving to projects for tracking.
Component: Server Operations → Server Operations: Projects
Assignee: server-ops → nobody
What is this view supposed to look like?  It's it as simple as going to http://nm-dash01.nms.mozilla.org/munin/ or /cacti/ ?
I have a dream of a complete monitoring dashboard.  This could include app-specific and cluster-specific views of statistics, one of which would resolve this bug, but more extensively it would provide views for many groups, devs, and admins.

Not promising anything this Q, but will talk with rtucker and others on this.  Maybe we could get some webdev help for the frontend and framework?
Assignee: nobody → rtucker
http://admin1.socorro.stage.private.sjc1.mozilla.com/ganglia/ (not working yet)

http://sp-admin01.phx1.mozilla.com/ganglia/

and #socorro-alerts on IRC already has pretty much everything. There is a separate effort to unify all the nagios and ganglia dashboards across the infra into a globally ldap-authed web ui. I'm not sure there is a bug for that though.
I think this is fixed per the URLs in comment 4. We are of course always working on improving monitoring, etc. but the scope of this bug is fixed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.