You are not logged in.
This bug is fixed. Fix will be available in M2.
I'm using Derby v10.8.1.2. I was testing in the afternoon btw.
It might be an issue in the search query which we don't know about yet, or if you were doing your tests shortly before 24:00 it might be cause of the known issue with the time zone which got broken in the SAM Agent: https://jira.sopera.de/browse/TESB-2300
What database were you using for storing SAM events?
When I apply a filter on SAM events with TAC, using the "on" date filter, it appears to select the wrong date. So for events on July 18, I need to select July 17.