In the 6.1 (and earlier) series of mAirList one could define start and stop log entry formats via the config tool. We exploited this and built an importer that parses log data and posts it to our traffic database. Fundamental to that import is knowing that a complete “advertisement” was played.
6.3 seems to have changed the way that logging entries are defined. By default, only start entries are logged. Consequently, all our advertisements are being flagged as unplayed. To recover, I’m working on a hack to mine the missing information from the system log. This is not sustainable as it requires a manual process.
There are new checkboxes on the logging config’s filter property page that enable/disable start and stop log entries. When our 6.1 config was migrated, the stop entry was disabled. When I re-enabled it, start and stop entries were logged but it’s not possible to tell (other than by inference) which is which (i.e. other than timestamps, the start and stop entries for each item are identical.
In 6.1 (and earlier) it was possible to independently define the format of the start and stop entries. In 6.3 there is a single line format.
How should I configure the logging to restore the previous behaviour?
Is it possible to place the broadcast duration token (%e) in the format string? Previously that token was only available on the stop entry. Our traffic system uses this information to determine whether we’ve met our contractural obligations to our commercial sponsors.
Thanks in advance for your advice.