event timestamp on report result of a schedule is incorrect about lmapd HOT 3 OPEN

Looking at src/xml-io.c, and src/json-io.c function render_result(), we have:

if (res->event) render_leaf_datetime(node, ns, "event", &res->start);

This most likely should be:
if (res->event) render_leaf_datetime(node, ns, "event", &res->event);

I will submit a patch as a PR.

from lmapd.

Pull request #17 fixes the worst of the issue, by ensuring that at least the "event" time is correctly rendered to the report. This time comes from schedule->last_invocation via the CSV metadata.

I have not checked whether schedule->last_invocation has the desired semantics or not re. the random spread (i.e. that it does not have the random spread added to it).

from lmapd.

@schoenw, this is a really annoying bug that makes it quite hard to properly correlate the reports from multiple actions of the same schedule later on a data processing pipeline.

This bug rendered lmapd unusable for us, we have been using the solution we proposed on #17 for quite a while already on production, successfully.

from lmapd.