Filter skipLimit, skipAttributes and skipAlarm
There is already a GitHub thread with discussion about it, but there is no perfect solution.
Ok, I found it : https://github.com/traccar/traccar/issues/4135.
But every one has mentioned that what should not be considered while skipLimit, skipAttributes and skipAlarm.
Everyone suggests different things. If you want to discuss it further I would recommend to do it there.
As per my testing below looks good to be done.
These filters should not be cancelled by skipLimit, skipAttributes and skipAlarm
filter.future
filter.invalid
filter.zero
filter.maxspeed
filter.minperiod
filter.accuracy
filter.approximate
filter.distance
These filters should be cancelled by skipLimit, skipAttributes and skipAlarm
filter.static
filter.duplicate
The content of this discussion of mine is also connected to this https://www.traccar.org/forums/topic/best-configuration-settings-of-configuration-file/#post-39604
Any approx dates for new release with solution for above.......I see last release as 10th November, 2018.....
Anton, please let us know if this being taken care off
Nothing has been changed, as far as I know.
I meant the filter issue is getting resolved ?
I am not working on it, if that's what you are asking.
I think this is done. Can we have the updated file to use and check.
There is overriding of the skipLimit, skipAttributes and skipAlarm
filter.future
filter.invalid
filter.zero
filter.maxspeed
filter.minperiod
filter.accuracy
filter.approximate
creating issues in the monitoring of the devices. despite above filters set, because of skipLimit, skipAttributes and skipAlarm, the database is registered with unwanted records affecting various alerts and reports