I would like to see this, but I have two things in mind.

• We have to change and support both formats in logconv etc, and it may break splunk etc.
• I don't like config options.

So perhaps if @mreynolds is okay with it, we can change this to be the default in 1.4.x?

I would like to see this, but I have two things in mind.

We have to change and support both formats in logconv etc, and it may break splunk etc.
I don't like config options.

So perhaps if @mreynolds is okay with it, we can change this to be the default in 1.4.x?

I like adding this "option". However, we should not change the current default behavior format (even in 1.4.x). Too many customers rely on it. This should definitely be a config option - even though William hates new config options :)

I really really hate new config options:

First, we open ourselves to customers making mistakes, and this being a format string, that adds a lot of complexity to compile and parse safely.

As well, logconv.pl (or our python) only knows about the "one true format".

IMO it's the path of least resistance to just fix this to use ISO 8601 instead, because at least it's a standard, and makes sense. Everything else is uneccessary work that 99% of our users will never ever ever touch.

Let's just update the default for 1.4.x . It's easier.

" However, we should not change the current default behavior format"

Also, we changed this format in the last 12 months - no one complained at all. I think we can change to 8601 in a major release. :)

" However, we should not change the current default behavior format"

Also, we changed this format in the last 12 months - no one complained at all. I think we can change to 8601 in a major release. :)

I agree, its fine for 1.4.0

Thanks mate. We'll leave this is the ticket queue for then then.

As per design doc http://directory.fedoraproject.org/docs/389ds/design/audit_improvement.html, > the fail log (and audit log) has now the format:

time: 20151111152800

So we should update the audit log timestamp format too.

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2319

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.