Karl
09-15-2008, 10:40 AM
A few suggestions for improvements to the mon appliance:
- Option to convert any counter value to an average i.e. mySQL Selects - currently it shows the total number of selects that have occured, the option to have it convert it to an average based on the sampling period/pace would be much more useful in most circumstances so we'd end up with a value representing the number of selects/inserts/etc. per second over that period.
When a DB server has done 300m queries total in 3 months, the scale is going to be so small that you'd not notice a jump of 125k queries in a 5 minute period etc. wheras with an average, you're far more likely to notice this jump on the small graphs - Just as an example, a jump of 125k queries on a server that's done 300m already is < 1 pixel. Wheras that'd be a mighty big spike as an average (Normally 38 QPS, now 417 QPS).
- Option to combine two values in to one reading i.e. I've got 2 DB servers, I want to graph the total SQL SELECTS over both servers, so I want to say, "graph (DB1 Selects + DB2 Selects)" (again, optionally as an average over the pace time). Or I want to graph total available memory on my web servers etc.
- Option to copy a graph i.e. I have two DB servers, I setup a lot of graphs for DB1, that I want to change also do for DB2 - So I copy the graph for DB1, then edit the copy, and tell it to substitute DB1 for DB2 where there are performance counters that match i.e. Memory, CPU, SELECTS etc.
- Option to not re-arrange graph layout when browser window size changes - I've just spent 5 minutes arranging them how I want them, I don't want the browser window deciding it knows better and re-arranging and overlaping them :)
- Option to convert any counter value to an average i.e. mySQL Selects - currently it shows the total number of selects that have occured, the option to have it convert it to an average based on the sampling period/pace would be much more useful in most circumstances so we'd end up with a value representing the number of selects/inserts/etc. per second over that period.
When a DB server has done 300m queries total in 3 months, the scale is going to be so small that you'd not notice a jump of 125k queries in a 5 minute period etc. wheras with an average, you're far more likely to notice this jump on the small graphs - Just as an example, a jump of 125k queries on a server that's done 300m already is < 1 pixel. Wheras that'd be a mighty big spike as an average (Normally 38 QPS, now 417 QPS).
- Option to combine two values in to one reading i.e. I've got 2 DB servers, I want to graph the total SQL SELECTS over both servers, so I want to say, "graph (DB1 Selects + DB2 Selects)" (again, optionally as an average over the pace time). Or I want to graph total available memory on my web servers etc.
- Option to copy a graph i.e. I have two DB servers, I setup a lot of graphs for DB1, that I want to change also do for DB2 - So I copy the graph for DB1, then edit the copy, and tell it to substitute DB1 for DB2 where there are performance counters that match i.e. Memory, CPU, SELECTS etc.
- Option to not re-arrange graph layout when browser window size changes - I've just spent 5 minutes arranging them how I want them, I don't want the browser window deciding it knows better and re-arranging and overlaping them :)