[mythtv-users] Monitoring frontend activities

[David Whyte]

On Thu, Feb 18, 2010 at 6:13 PM, Raymond Wagner <raymond at wagnerrp.com> wrote:
> On 2/17/2010 22:47, David Whyte wrote:
>>
>>
>
> Information from the backend is available through the XML status server on
> 'http://mybackend:6544/xml'.  Contained are the status of all recorders, The
> upcoming schedule, jobs in the queue, recording disk stats, load averages,
> basic guide data information.  If you check out 'MythXMLTest' in contrib,
> you'll find a number of additional pages with other accessible information.
>  Alternatively, you can access the backend directly through mythprotocol on
> port 6543.
>
> Information from the frontend will only be available from the telnet socket.
>
> The perl and python bindings provide access to these interfaces to varying
> degrees. Below is an example of retrieving some of that information through
> the python bindings (in trunk).
>

Hi Ray,

Thanks for the reply and the helpful examples.  I have used both the
XML status page before
(http://sites.google.com/a/thewhytehouse.org/mythtv/modification/googlegadgets)
and also the python bindings
(http://sites.google.com/a/thewhytehouse.org/mythtv/modification/balancingstoragegroupusage)
but none of those options seem to give any kind of detailed auditing
of activity performed by a frontend.

I even just turned the frontend logging to verbose for 'all' and
didn't seem to see any logging of an attempt to delete recordings.
This rules out the monitoring of log files.

And the problem with both the python bindings and the frontend socket
is that you would have to poll for any changes rather than be
notified.  This could lead to problems if I am polling quite
vigorously trying to ensure that all events are captured.

It looks like there is some potential to improve the auditing of
activities in a more explicit way.  Maybe this is an area that I can
try and look at in the not too distant future...hopefully.
Unfortunately, I seem to say that too often, for too many things.

Anyways, thanks again.

Regards,
Whytey