Better tools for investigating logs #32

Open
opened 2015-01-19 21:49:09 +01:00 by kjetil · 1 comment
kjetil commented 2015-01-19 21:49:09 +01:00 (Migrated from gitlab.lallis.org)

Currently the log is just displayed as a table containing every log entry, and with the values naively rendered in a popup.

There should be filters on the top level fields (timestamp, type and user) and the system should have knowledge about the different kinds of event so that they can be displayed in a proper way

Currently the log is just displayed as a table containing every log entry, and with the values naively rendered in a popup. There should be filters on the top level fields (timestamp, type and user) and the system should have knowledge about the different kinds of event so that they can be displayed in a proper way
kjetil commented 2015-01-23 15:05:22 +01:00 (Migrated from gitlab.lallis.org)

Other filters could include "hide admin events" (enabled by default), only show events for open contractsets, only show for a single market, set or contract.

Other filters could include "hide admin events" (enabled by default), only show events for open contractsets, only show for a single market, set or contract.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kjetil/predi#32
No description provided.