From: Andrew Cooper <andrew.cooper3@citrix.com>
To: sparvu@systemdatarecorder.org
Cc: xen-devel@lists.xen.org
Subject: Re: domains being migrated state message improvements
Date: Fri, 2 May 2014 16:55:03 +0100 [thread overview]
Message-ID: <5363BFD7.2040600@citrix.com> (raw)
In-Reply-To: <1399045669.3861.25.camel@nereid>
On 02/05/14 16:47, Stefan Parvu wrote:
>>> However, the information is stale by the time it is displayed. It is
>>> not really appropriate to be consumed by anything other than an eyeball.
>> Agreed. And even if someone disagrees I think it is up to those tools to
>> accept whatever the output is, even if that includes "nonsensical"
>> results.
> So why do we have xentop then ?
So a human can take a look at a system and see if anything looks
obviously wrong.
> Or other tools ? To consume your
> internal data, and more or less to ensure it is legit.
>
> Remember, that we might have cases where people *are* consuming xentop
> results.
How? it uses ncurses to be interactive on the terminal. Collecting this
output with automated tools is impractical.
> Or other tool(s), based on results coming from Xen kernel.
This is a bigger issue. The values are exposed in libxc and somewhat
more statically to the shell via xl
>
> So if I want to store 1 year statistics of all guests, as time series, I
> expect to see more or less reliable data. Right ? Analyzing data will
> turn in a mess.
>
What are you looking to collect? It surely isn't direct scheduling data.
~Andrew
next prev parent reply other threads:[~2014-05-02 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:16 domains being migrated state message improvements Stefan Parvu
2014-05-02 13:23 ` Ian Campbell
2014-05-02 13:31 ` Stefan Parvu
2014-05-02 14:15 ` Ian Campbell
2014-05-03 7:41 ` Stefan Parvu
2014-05-02 13:24 ` Andrew Cooper
2014-05-02 13:29 ` Ian Campbell
2014-05-02 13:40 ` Andrew Cooper
2014-05-02 14:15 ` Ian Campbell
2014-05-02 15:47 ` Stefan Parvu
2014-05-02 15:55 ` Andrew Cooper [this message]
2014-05-02 16:46 ` Stefan Parvu
2014-05-02 17:37 ` Andrew Cooper
2014-05-02 17:59 ` Stefan Parvu
2014-05-02 20:22 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5363BFD7.2040600@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=sparvu@systemdatarecorder.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.