Skip to content

Improve/fix iso8601 timestamp parsing and generation#20

Open
blalor wants to merge 3 commits intoDieterbe:masterfrom
blalor:better_iso8601
Open

Improve/fix iso8601 timestamp parsing and generation#20
blalor wants to merge 3 commits intoDieterbe:masterfrom
blalor:better_iso8601

Conversation

@blalor
Copy link
Contributor

@blalor blalor commented Jan 13, 2015

Improves compatibility with Logstash, Kibana, Grafana. Timezone always stored in UTC with "Z", and parsing supports fractions of a second.

Improves compatibility with Logstash, Kibana, Grafana.  Timezone
always stored in UTC with "Z", and parsing supports fractions of a
second.
@blalor
Copy link
Contributor Author

blalor commented Jan 13, 2015

This also removes the apparently-unused timezone property in config.py.

Events are already being stored in UTC, but unless the browser and
server are in the same timezone, timestamps get munged.  Using
`picker.setLocalDate` is especially problematic.  With this commit,
everything is entered and displayed in UTC.

The timezone *can* be made configurable, and it would probably make
sense to allow users to enter times in their local timezone, but
that's too much work for right now.
@blalor
Copy link
Contributor Author

blalor commented Jan 13, 2015

I had to switch to UTC for all entry and display of timestamps. Unless the browser and server are in the same timezone, the times would get munged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant