Mark Tripod

I have seen instances in the past where certain conditions can cause the translation of an `offset` value of 180 in the config.yml to exceed the maximum allowed by the...

Nothing has changed in the API. The version 2 log endpoints require timestamps in milliseconds. This is a departure from the original version 1 log endpoints expecting a timestamp in...

``` version: "1.0.0" dls_settings: log_filepath: "/tmp/duologsync.log" log_format: "JSON" api: offset: 179 timeout: 180 checkpointing: enabled: True directory: "/tmp" servers: - id: "test" hostname: "127.0.0.1" port: 514 protocol: "TCP" account: ikey:...

Each log endpoint has individual argument requirements that have never changed since they were published. My point was that DLS takes into account which arguments are required for each endpoint...

@JBHilke Are you still having the periodic shutdown issue with Duo Log Sync?

Which RFC are you basing the message format compliance against?

@novwhiskey07 There is currently no way to transform data directly using DLS. The primary function of DLS is to extract raw log information from the Duo Admin API and then...