FILES directory test not graphing
list Patrick Nixon
Hey all, I did a search, but these are rather generic terms, so I'm hoping someone has seen this. When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image. Any suggestions on what to tweak, how to troubleshoot this? Thanks! --Patrick
list Greg Hubbard
What do you want to graph, and what is wrong with the current graphs? It helps if you provide more detail. GLH
▸
On Mon, Oct 19, 2009 at 10:40 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:
Hey all, I did a search, but these are rather generic terms, so I'm hoping someone has seen this. When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image. Any suggestions on what to tweak, how to troubleshoot this? Thanks! --Patrick
--
Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my
advice is worth at least as much as what you are paying for it, or your
money cheerfully refunded.
list Patrick Nixon
The Files test provides a mechanism to graph the size of the object being monitored through the TRACK option. For the file, it graphs the size of the file. I'm assuming that it's supposed to do that for the directory as well, but it's showing a flatline at 0 instead of the value show in the footer of the graph, which at the time of this email is 121161.9.
▸
On Mon, Oct 19, 2009 at 11:43 AM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid> wrote:What do you want to graph, and what is wrong with the current graphs? It helps if you provide more detail. GLH On Mon, Oct 19, 2009 at 10:40 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:Hey all, I did a search, but these are rather generic terms, so I'm hoping someone has seen this. When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image. Any suggestions on what to tweak, how to troubleshoot this? Thanks! --Patrick-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.
list Greg Hubbard
Hmm. A directory looks like a file, too, and it has a size. Are you interested in the size of the directory itself (as a file) or are you interested in the total size of all files contained within the directory? What are the units in the graph that you are looking at, and is the directory by itself or is it combined with other items? One problem with RRD graphs is that everything in a graph gets the same scale factor, so if you combine something small with something large the small item can appear to be near zero because other items are much larger.
▸
GLH
On Mon, Oct 19, 2009 at 11:03 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:
The Files test provides a mechanism to graph the size of the object being monitored through the TRACK option. For the file, it graphs the size of the file. I'm assuming that it's supposed to do that for the directory as well, but it's showing a flatline at 0 instead of the value show in the footer of the graph, which at the time of this email is 121161.9. On Mon, Oct 19, 2009 at 11:43 AM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid> wrote:What do you want to graph, and what is wrong with the current graphs? It helps if you provide more detail. GLH On Mon, Oct 19, 2009 at 10:40 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:Hey all, I did a search, but these are rather generic terms, so I'm hoping someone has seen this. When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image. Any suggestions on what to tweak, how to troubleshoot this? Thanks! --Patrick-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.
-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.
list Patrick Nixon
Thanks for the follow up Greg. There were two issues I found. 1.) The du command was reporting in 512k blocks, not bytes as I was expecting it to. I fixed it by adding DU="/usr/bin/du -b" into the hobbitclient.cfg file 2.) because of the above, you were right, the data was being graphed next to a file, that was already being reported in bytes, so it was disappearing. --Patrick
▸
On Mon, Oct 19, 2009 at 12:10 PM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid> wrote:Hmm. A directory looks like a file, too, and it has a size. Are you interested in the size of the directory itself (as a file) or are you interested in the total size of all files contained within the directory? What are the units in the graph that you are looking at, and is the directory by itself or is it combined with other items? One problem with RRD graphs is that everything in a graph gets the same scale factor, so if you combine something small with something large the small item can appear to be near zero because other items are much larger. GLH On Mon, Oct 19, 2009 at 11:03 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:The Files test provides a mechanism to graph the size of the object being monitored through the TRACK option. For the file, it graphs the size of the file. I'm assuming that it's supposed to do that for the directory as well, but it's showing a flatline at 0 instead of the value show in the footer of the graph, which at the time of this email is 121161.9. On Mon, Oct 19, 2009 at 11:43 AM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid> wrote:What do you want to graph, and what is wrong with the current graphs? It helps if you provide more detail. GLH On Mon, Oct 19, 2009 at 10:40 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:Hey all, I did a search, but these are rather generic terms, so I'm hoping someone has seen this. When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image. Any suggestions on what to tweak, how to troubleshoot this? Thanks! --Patrick-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.-- Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3) my advice is worth at least as much as what you are paying for it, or your money cheerfully refunded.
list Henrik Størner
▸
In <user-8a388fbbc915@xymon.invalid> Patrick Nixon <user-1f2406f832af@xymon.invalid> writes:
I did a search, but these are rather generic terms, so I'm hoping someone has seen this.
When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image.
Any suggestions on what to tweak, how to troubleshoot this?
Did you add a "DIR" setting to hobbit-clients.cfg ?
Regards,
Henrik
list Patrick Nixon
Henrik, I did. It appears that the DIR directive doesn't honor the 200M for the size option instead, it requires 204800000 (the number I'm using to approximate 200M). Have you seen this behavior before? Working: DIR /opt/app/oracle/diag/tnslsnr/mmsdb2/listener/alert/ RED SIZE<204800000 TRACK Not Working: DIR /opt/app/oracle/diag/tnslsnr/mmsdb2/listener/alert/ RED SIZE<200M TRACK --Patrick
▸
On Wed, Oct 21, 2009 at 4:23 PM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:In <user-8a388fbbc915@xymon.invalid> Patrick Nixon <user-1f2406f832af@xymon.invalid> writes:I did a search, but these are rather generic terms, so I'm hoping someone has seen this.When a directory is added to the FILES test, it doesn't graph properly, even though the data is appearing at the bottom of the graph image.Any suggestions on what to tweak, how to troubleshoot this?Did you add a "DIR" setting to hobbit-clients.cfg ? Regards, Henrik
list Henrik Størner
▸
In <user-6a8a14f8f1b3@xymon.invalid> Patrick Nixon <user-1f2406f832af@xymon.invalid> writes:
I did. It appears that the DIR directive doesn't honor the 200M for the size option instead, it requires 204800000 (the number I'm using to approximate 200M).
Have you seen this behavior before?
Working: DIR /opt/app/oracle/diag/tnslsnr/mmsdb2/listener/alert/ RED SIZE<204800000 TRACK
Not Working:
DIR /opt/app/oracle/diag/tnslsnr/mmsdb2/listener/alert/ RED SIZE<200M TRA=
CKYes, it is intentional - the various "du" commands use different metrics: Some report kB, some report disk blocks (usually 512 bytes)... To avoid having to know about the intricacies of each system, Xymon just compares the number it gets from the client with the number from hobbit-clients.cfg, withouth doing any kind of math to convert numbers. Regards, Henrik
list Patrick Nixon
Thank you for the clarification.
▸
On Fri, Oct 23, 2009 at 1:02 PM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:In <user-6a8a14f8f1b3@xymon.invalid> Patrick Nixon <user-1f2406f832af@xymon.invalid> writes:I did. It appears that the DIR directive doesn't honor the 200M for the size option instead, it requires 204800000 (the number I'm using to approximate 200M).Have you seen this behavior before?Working: DIR /opt/app/oracle/diag/tnslsnr/mmsdb2/listener/alert/ RED SIZE<204800000 TRACKNot Working: DIR /opt/app/oracle/diag/tnslsnr/mmsdb2/listener/alert/ RED SIZE<200M TRA= CKYes, it is intentional - the various "du" commands use different metrics: Some report kB, some report disk blocks (usually 512 bytes)... To avoid having to know about the intricacies of each system, Xymon just compares the number it gets from the client with the number from hobbit-clients.cfg, withouth doing any kind of math to convert numbers. Regards, Henrik