...
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
Memcached canonical keys When a memcached key is Normally memcached keys are generated by a front-end DEVIL and are directly associated with a system element (e.g. QUATB004), it takes . These canonical keys take the same name of the element name with two possible extensions : QUATB004"_STA and QUATB004" and "_DYN" (for the the static and dynamic datasets). Memcached free keys When a memcached key is associated with a system element element but refers to data non belonging to its static or dynamic datasets (e.g. a waveform not included in the dynamic dataset), it takes the name of the element with the _BUF extension (e.g. DCTEL001_BUF is the acquisition buffer of the MRe Current Monitor) When many different keys are associated with the same system element, they take different names but always end up with the _BUF extension (eg. ORBP*DAT_BUF, ORBP*AVG_BUF, ORBP*VAR_BUF are respectively: the last acquired, the average and the variance buffers of the MRp orbit). When a memcached key is not calculated by a front-end DEVIL and/or is not directly associated to a system element, it take a name defined by the developer.does not refer to the "_STA" or "_DYN"dataset of a system element, it takes a name of 8 characters followed by a 3 characters extension separated by a "_". Both the name and the extension are arbitrary even though It's advisable use conventional extensions:
|
Memcached traffic monitoring
...