Re: Basic iocStats database

[Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>]

Hi Sean,

There is a similar community module at GitHub called iocStats that a number of other sites use, I don't know how the SSRL version differs from that or which one is newer, but I'm pretty sure they are related. Many community modules can be found in projects under the GitHub epics-modules organization which also hosts all of the synApps collection.

- Andrew

On 9/2/22 8:25 AM, Sean Leavey via Tech-talk wrote:

Hi all,

Following on from my first question a couple weeks ago about the feasibility of setting up EPICS for a small lab, I've provisioned a Debian 11 VM and gotten EPICS Base set up. While I wait for the arrival of the Modbus-based sensors I plan to use EPICS to read, I thought I'd set up iocStats (https://www.slac.stanford.edu/grp/ssrl/spear/epics/site/devIocStats/) so I have some real world values to play with - CPU usage, etc.

Following various guides I've managed to compile the example application with iocStats module support. However, I don't actually have any of the records provided by iocStats configured, and that's where I've gotten stuck. What I'd really like to see are examples of databases others have made that make use of the various records provided by iocStats (if such an example is provided with iocStats itself, I missed it). Ultimately I want to be able to caget my VM's CPU load, so I can play with archiving and plotting it later. Google has failed me so I thought I'd ask here. So, is anyone willing to share their iocStats configurations with me?

Cheers,
Sean

This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.

-- 
Complexity comes for free, Simplicity you have to work for.