More host status essentials

As a DBA I'm monitoring mysql status, processlist, e.t.c.
Would be extremely useful to have at least these two:

SHOW SLAVE STATUS - can be run as a Query now, but horizontal scrolling is really annoying, vertical formatting would help

SHOW ENGINE INNODB STATUS - can't even see now in data grid :(

You mean these both should get additional sub tabs on the "Host" tabs, somewhere between "Status" and "Processes"?

Sure, would work for me.

Hm, why not. Only the results are such inconveniant to handle, also for me when I'm trying to display these in a tab/grid. For moving columns to rows for SHOW SLAVE STATUS I'll probably find some way, but the long text in SHOW ENGINE INNODB STATUS is so messy, I can't display that in a tree or list. Any idea?

For slave status - it's always 1 record only, looks natural for datagrid (have you tried running in mysql "show slave status\G"?).

Yes, for engine status it's like a "text" column - the easiest way probably would be to use the "text editor" window (the one which pops up for editing a long text cell)...
In a somewhat smarter way it should be possible to gather same info from innodb tables (information_schema database) - I can try to compile a list of queries, if you're interested.

Another idea - a multilevel tree out of status variables list by parsing their names using "_" as a separator. If there is more then 1 it becomes a sublist/subtree, for example:

- Com_ [+/-]
-- Com_admin_commands | 12345
-- Com_alter_ [+/-]
--- Com_alter_db | 1
...
--- Com_alter_tablespace | 0
-- Com_analyze | 1

This would group innodb status variables nicely.

Which of the Com_* status variables are InnoDB related?

Did you notice the "Command statistics" tab? I'm asking because that nearly does what you ask for. This tab/grid fetches variables beginning with "Com_", and displays these in the order of their hits

SHOW /*!50002 GLOBAL */ STATUS LIKE 'Com\_%';

NoneI was talking about the whole server status thing.
But the Innodb_* status variables do show the current status of InnoDB engine...
Yes, I did notice, I have two other monitoring systems for that :)
Ok, another idea - is it possible to make a filter? A text input where I could specify for example "%buffer_pool_pages%","%pending%" and only those ones would be shown and retrieved again by F5?

Yes, a filter is also there - click Edit > Filter panel, or press Ctrl+Alt+F, and put something into the displayed input field below the list.

Got it! However, even if I specify 1 variable only it still requests full global status each time upon refresh, and I can't set more than one filter: "pending, pool_pages" doesn't work.

Hm, well, full and filtered status is a very minor difference of about 5KB moreorless sent from the server to the client. So I'm going to ignore that :)

And yes, the filter does not allow more than one string. It could be a regular expression which it is not currently for performance reasons on huge data sets.

No problem
Any hope for a "innodb status" button which would open new window with results inside in some textarea, so it could be scrolled/selected&copied?

Since
a) e.g. SLAVE STATUS is not of interest to the many users which do not operate a replicating server, and
b) ENGINE INNODB STATUS is not of interest to many users (even many of those that do use this engine), but
c) I do assume that there will be further special-interest requests for more server type stati in the future,

I would boldly suggest a .dll-based plugin architecture for such.

glitch repair: plugin architecture

no glitch repair. Editor´s "Link to bug or feature request" returns a 404 URL; manually: the feature request.

Linking a ticket does not require some <url> stuff, just type

issue #2856

Do I really need to invent some plugin architecture just because someone wants to see SLAVE STATUS or some other stuff in a GUI way? I prefer simple solutions, and not to have much work with stuff that only a minor group of users will ever use. HTTP tunneling is probably more important... or maybe not.

eh, I meant issue #1405.

URL (re: forum mechanics): the small text editor used to enter posts like this one has a button (4th from left) called "Link to bug or feature request"; when pressed, a small dialog asks for the issue number nnnn to refer to.
However, the URL generated by this button is http://changes.heidisql.com/nnnn, which produces a 404.

The idea behind the plugin interface is exactly that you dont have much work with stuff that few people want, without making it impossible by plainly rejecting their proposal.

If you implement the plugin interface as sketched in ##2865, which IMHO is not too difficult or time-consuming, everybody who wants special server status can have it by building a simple .dll, without you having any work at all from it.

"few people want" - hm, that's really surprising to me, probably I misunderstood the target audience of this (a very good!) product :)
'cause every mysql production environment has a replication running, for redundancy at least, and for doing some heavy stuff on the slave, and I'm not mentioning reads/writes split... that's why I gave such subject to this thread in a first place ;)
So, yes, if it's strictly for students and home page users, sure, they don't need all of that, although it could be somewhat educating for some.
However, if there are any plans to target more professional auditory, it will become essential to have such stuff, plus, it can always be split into two versions - free and simple, and a commercial one.