Hi.
I thought about using a Computed Attribute to mark the static heartbeats as valid = false (e.g., ignition == false && speed == 0 ? false : true) so that filter.invalid would drop them.
But as we know, Computed Attributes run after the XML filtering engine in the pipeline, so this doesn't prevent the positions from being saved to the database.
Is there any advanced configuration or filter combination to change this execution order, or any other workaround to drop these specific static heartbeats ?
Any help or insights would be greatly appreciated!
P.D.
I cannot simply use filter.static either, because it drops my "Ignition ON" events at 0 km/h in the garage (unless I use skipAttributes=ignition, which then bypasses the static filter entirely).
If you put negative priority on computed attribute, it will run before anything else.
Hi.
I thought about using a Computed Attribute to mark the static heartbeats as valid = false (e.g., ignition == false && speed == 0 ? false : true) so that filter.invalid would drop them.
But as we know, Computed Attributes run after the XML filtering engine in the pipeline, so this doesn't prevent the positions from being saved to the database.
Is there any advanced configuration or filter combination to change this execution order, or any other workaround to drop these specific static heartbeats ?
Any help or insights would be greatly appreciated!