Current approach of saving timer-related data results in data being displayed with minutes delay

Description

Migrated from NovaTec Jira. Original ticket: INSPECTIT-992

Currently the aggregation of timer data is flawed. Data is displayed quite late, so the user might think the charting does not work. In situations when not so many methods are being charted, it can occur that write to the database is more than few minutes late. This is all because we are keeping data in memory based on the method/time-stamp combination, thus if not so many methods are monitored that our queue does not get filled fast. Meaning data is not dropping from the queue, and this is when we persist it to the database. Other than that we only persist when there is no new entry for one minute (situations when agent is disconnected).

If we are to move to influx this problem would be solved there as well.

Apart from that: The approach is also different from the aggregation of HTTP data.

Environment

None

Assignee

Ivan Senic

Reporter

Stefan Siegl

Labels

None

Integrator

None

Components

Affects versions

Priority

Medium
Configure