Skip to content

Conversation

@koushikcgit
Copy link

Signed-off-by: Koushik Chakravarty koushik.chakravarty@citrix.com

@koushikcgit
Copy link
Author

Adding @johnelse as reviewer

@johnelse
Copy link
Contributor

johnelse commented Nov 4, 2015

This change looks fine. However the ticket mentions two issues:

Observed:
1. Alert description says "ratio of memory demand to physical memory is beyond 0.0%" which is not clear to understand
2. Alert priority reduced when it is generated after repeat interval

This looks like it only fixes #1 - do we need a separate ticket for #2?

@jonludlam
Copy link
Contributor

I don't think the message should contain the text 'Dom0' - that's not Approved Vocabulary :-)

Perhaps we could get someone used to writing user-facing docs to write the text?

@robhoes
Copy link
Member

robhoes commented Nov 4, 2015

"Dom0" -> "The Control Domain"?

@stephen-turner
Copy link
Contributor

I've created CA-187949 for the other issue.

@johnelse
Copy link
Contributor

johnelse commented Nov 5, 2015

Actually yes I agree with @robhoes, "the control domain" would be better than "dom0".

@stephen-turner
Copy link
Contributor

I'm actually still confused what the message means, and what is being compared. What is the "control domain memory demand" and what is the "domain physical memory"? (Or should it be host memory?)

@koushikcgit
Copy link
Author

This is actually calculated as (res_mem + swap_in_use) / phy_mem (using /proc/meminfo as data source).

So yes, I think its better to use "Control domain memory usage" with respect to "Control domain physical memory".

@johnelse : The issue #2 is not reproducible and this PR is to fix the issue #1 mail-alarm bit.

@stephen-turner
Copy link
Contributor

So would it be accurate to say it's the amount of RAM actually in use in dom0 compared with the total amount of dom0 RAM?

@koushikcgit
Copy link
Author

@stephen-turner Yes.

@stephen-turner
Copy link
Contributor

Re issue 2, if it's really not reproducible, we should close CA-187949. However, there is a screenshot there, so it clearly happened somehow!

@stephen-turner
Copy link
Contributor

OK, so next question: why does it say the "ratio ... is beyond 0%". It's always beyond 0%! Does it mean 100%, or is the number not getting passed around and defaults to zero?

@koushikcgit
Copy link
Author

Updated.

@koushikcgit koushikcgit force-pushed the CA-183272 branch 2 times, most recently from 91e4ded to 7f6f0e6 Compare November 9, 2015 08:17
@johnelse
Copy link
Contributor

I've asked the docs team to have a look at the wording of this message.

@thomassa
Copy link
Contributor

At that rate, I think we should assign the "CA" bug-ticket to the docs people and close this pull-request for the time being, until we have wording from the official word-wranglers.

@stephen-turner
Copy link
Contributor

Wait a bit, I was hoping to come up with a wording we could use in the GUI.

@stephen-turner
Copy link
Contributor

How about something like: "The memory required by the control domain is above x% of its allocated memory". Is that accurate?

@koushikcgit
Copy link
Author

@stephen-turner : Makes sense to me. Do you want me to update the PR in accordance to this?

Signed-off-by: Koushik Chakravarty <koushik.chakravarty@citrix.com>
@stephen-turner
Copy link
Contributor

Yes, please do.

@thomassa
Copy link
Contributor

Looks good. Merging.

thomassa added a commit that referenced this pull request Nov 20, 2015
CA-183272: Improving Dom0 mem usage alert mail text
@thomassa thomassa merged commit 38e33b5 into xapi-project:master Nov 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants