Known limitations
Process message limitations
-
PQM process machine data with the messaging semantic "at most ones". So there is no guarantee that the data is persisted in the Influx database in case of failures.
-
There is a size limitation of 68 kb (compressed) per process message. Depending on the compression rate, in most of the cases it has been proofed, that the maximum raw message size per process message is about 108 kb.
-
There is a limitation for a process timestamp ($process.ts) precision for timestamps with a precision higher than milliseconds. Process timestamps with such precision are not displayed. For example, the timestamp ‘2024-03-21T12:54:23.5919Z’ will not be shown, while ‘2024-03-21T12:54:23.591Z’ works correctly.
Deviation Processor is not available or has a low ingest performance
If the deviation processor is deployed, automatically PQM becomes a detecting module in the context of the deviation processor. More information on this can be found in the deviation processor user manual.
By becoming a detecting module, PQM forwards the events as deviations via HTTPS to the deviation processor.
If PQM receives a non-successful status code, PQM will return status code 500 to the initiator of the process message request.
The sender is responsible for re-sending the process message.