Implement database stats collection

Bug #1666295 reported by Paul Everitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL4
Won't Fix
Low
Jim Fulton

Bug Description

We need to collect time series data on queries in production (I/O, CPU, etc.) We can go back to using DataDog, or we can integrate with whatever FC might offer.

Evaluate the choices based on the measurements you're looking for, and let me know if there's anything I need to do.

Revision history for this message
Jim Fulton (jim-zope) wrote :

FWIW, the stats I suggested the other day were more low-level that this, I was interested in looking at IO statistics, to understand whether SSD would help.

Trying to view this as a time series is awkward, because:

- different queries
- mixing relstorage queries with regular search.

To understand pain points, I think it would be better to do snapshot analysis (iow, look at request stats over some period of time) to identify problem requests and to look at postgres query stats, which we may need to turn on, to understand expensive sql queries.

Revision history for this message
Paul Everitt (paul-agendaless) wrote :

I'll move this to April but make it a low priority.

Changed in karl4:
importance: Medium → Low
milestone: 028 → 030
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Still interested in this? Or do you feel like we know enough that this isn't worth using the hours on?

Revision history for this message
Jim Fulton (jim-zope) wrote :

I don't think we need an issue for this.

Changed in karl4:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.