| Warning |
|---|
When creating a new key, it is essential to check that it is not already present in memcached. |
When a memcached key does not directly refer to a system element but – for example – to derived quantities, the format of its name is free and can be arbitrary defined, provided that it is not already used.
Even though the name format is arbitrary, it is advisable to always use UPPERCASE and append an extension separated by a "_" (e.g. MY-ARBITRARY-NAME_DAT). In any case, do not use the "_AUX" extension for a "free key".
To avoid the proliferation of extensions, try using the ones listed in the table below
...
Memcached canonical keys
Normally memcached keys are generated by a front-end DEVIL and are directly associated with a system element (e.g. QUATB004). These canonical keys take the same name of the element with two possible extensions "_STA" and "_DYN" (for the the static and dynamic datasets).
Memcached free keys
...
:
| Extension | Description |
|---|---|
| _ |
...
| BUF, _JBUF* | Data |
...
| buffers (FIFOs , circular buffers, etc...), not necessarily associated with a system element. |
| _ |
...
Memcached traffic monitoring
As root user root on the memcached server (192.168.192.107)
| Code Block |
|---|
> iftop -i eth0 -B |
| INFO, _JINFO* | Static metadata, not necessarily associated with a system element. |
| _DAT, _JDAT* | Generic data structures, not necessarily associated with a system element. |
(*) "J" prefix indicates that the key content is a Json document.
...
| Children Display |
|---|