FMS - LHS Synker - KPI for the most recent hour are at 0 or have a higher number than expected : Timining

FMS - LHS Synker - KPI for the most recent hour are at 0 or have a higher number than expected Imprimir

Creado por: Carlos Gajardo

Fecha de modificación: Jue., 16 Feb., 2023 a las 8:15 P. M.

Tima version: 2022-2

LHS version: 4.2

DeltaTima version:

GeometryServer version:

FMS type:

Client:

NOTE: The following image was modified to simulate the situation!:

Diagnosis and Solution: It may occur, for example, when the performance KPI is calculated using data from different tables. It is likely to happen that the tables are not updated at the same time. So, it could happen that the table with extraction information get updated to current time but the table with effective/operating times is not updated yet. Then, when calculating the KPI, the algorithm may obtain a value too much higher than expected (Performance = Extraction/Effective or operating time). It is a common behavior in TIMA DMH.

This behavior can be controlled by a reduction of the period for KPI connectors execution on lhs\etc\lhs-synkerrc.yml. The common value for freq parameter is 29 minutes, so you could reduce it to 10 or 15 minutes.

Carlos es el autor de este artículo de solución.

¿Le resultó útil? Sí No

FMS - LHS Synker - KPI for the most recent hour are at 0 or have a higher number than expected Imprimir

Artículos relacionados