Ignition ON/OFF delay with filter.static=true vs DB flooding with skipAttributes=ignition

I’m facing an issue with static filtering and ignition events and would like guidance on the correct approach.

When I use only:

<entry key="filter.static">true</entry>
<entry key="filter.stationaryPeriod">300</entry>
<entry key="filter.stationaryDistance">3</entry>

the device is correctly treated as stationary and positions are stored every 5 minutes.
However, in this case ignition ON/OFF events are also delayed by 5 minutes, since the position is considered static.

To fix the ignition delay, I enabled:

<entry key="filter.skipAttributes.enable">true</entry>
<entry key="filter.skipAttributes">ignition</entry>

With this configuration, ignition ON/OFF events are generated instantly, which is expected.
But after enabling this, filter.static=true seems to stop working and positions start getting stored very frequently (every 10–30 seconds or 1 minute), causing database flooding.

Enabling:

<entry key="filter.duplicate">true</entry>

does not seem to prevent this behavior.
Is there a recommended configuration or workaround where:

• ignition ON/OFF events are generated instantly, and
• static positions are still stored at a controlled interval (e.g. every 5 minutes) without flooding the database?

Any guidance would be appreciated.

I'm guessing ignition value is being reported in those events.

Ignition is off and coordinates are also not changing, spped is also 0. Just sharing a screenshot for ref.

You configured filter.skipAttributes to keeps all positions that have ignition, which I'm assuming is everything, so none of your filtering is working.

Maybe that’s the case, Anton, but my requirement is to have a position inserted immediately whenever the ignition value changes.
Is there any filtering parameter or recommended configuration in Traccar that allows storing a position instantly on ignition change while still keeping static position filtering intact?

No, there's no direct parameter that can help you. You probably need to use computed attributes to make something for your case.

Understood, Anton, and thank you for the guidance.
If possible, Could you share any link or reference where I can read more about this and understand it better? That would be a great help.

We have a dedicated documentation page for computed attributes. You should start from there.

Understood. Thank you Anton.