If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to REGISTER before you can post. To start viewing messages, select the forum that you want to visit from the selection below.
Thanks for the pointer to vfs.dev.[read][write]. T'is good they return actual numbers, but the values that are returned are allegedly avg[1][5][15], so i'm guessing the agent side is using something like sar? Q: how (exactly) are these agent params obtaining and calculating disk data averages? I've compared sar and iostat output against data returned by agent and they don't correlate. Is there a relationship between agent polling/reporting frequency and the averaging period of returned data?
The vfs.dev. items weren't included in the Linux or BSD templates nor assocated with any template in data.sql for 1.8.6 or 1.8.10 (they get put into a "help_items" table - whatever that's for) . Are they ready for primetime?
Got it. This works really well! Took a while to realise that the agent is performing time averaging and a delta calc isn't required in the item definition.
Originally posted by CeeEss
barging in here ... pardon me
Thanks for the pointer to vfs.dev.[read][write]. T'is good they return actual numbers, but the values that are returned are allegedly avg[1][5][15], so i'm guessing the agent side is using something like sar? Q: how (exactly) are these agent params obtaining and calculating disk data averages? I've compared sar and iostat output against data returned by agent and they don't correlate. Is there a relationship between agent polling/reporting frequency and the averaging period of returned data?
The vfs.dev. items weren't included in the Linux or BSD templates nor assocated with any template in data.sql for 1.8.6 or 1.8.10 (they get put into a "help_items" table - whatever that's for) . Are they ready for primetime?
Comment