Exactly. Loggly will only sync with a unix `timestamp` parameter. If the field is missing, the event date/time is assumed to be the date/time that the event request was received by Loggly.

Having both a `timestamp` and `datetime` parameter sent will cause confusion to users as it's likely that the times will vary slightly.

Some custom implementations may have created a dependency on the `datetime` parameter so it can't be safely removed. Would you consider it safe to remove for 1.8?