nodeDetails="Saves timeseries telemetry data based on configurable TTL parameter. Expects messages with 'POST_TELEMETRY_REQUEST' message type. "+
"Timestamp in milliseconds will be taken from metadata.ts, otherwise 'now' message timestamp will be applied. "+
"Allows stopping updating values for incoming keys in the latest ts_kv table if 'skipLatestPersistence' is set to true.\n "+
"Enable 'ignoreMetadataTs' param to ignore the timestamp that arrives from message metadata. "+
"<br/>"+
"Enable 'useServerTs' param to use the timestamp of the message processing instead of the timestamp from the message. "+
"Useful for all sorts of sequential processing if you merge messages from multiple sources (devices, assets, etc).\n"+
"For example, if you count number of messages from multiple devices into asset time-series value. "+
"Typically, you fetch the previous value of the counter, increment it and then save the value. "+
"If you use timestamp of the original message, the value may be ignored, since it has outdated timestamp comparing to the previous message.",
"<br/>"+
"In the case of sequential processing, the platform guarantees that the messages are processed in the order of their submission to the queue. "+
"However, the timestamp of the messages originated by multiple devices/servers may be unsynchronized long before they are pushed to the queue. "+
"The DB layer has certain optimizations to ignore the updates of the \"attributes\" and \"latest values\" tables if the new record has a timestamp that is older than the previous record. "+
"So, to make sure that all the messages will be processed correctly, one should enable this parameter for sequential message processing scenarios.",