@timestamp in local time

[flyasfish]

The search result table shows event @timestamp in UTC time, is there a way to convert this to local time using local timezone? Kibana 2 did a great job on this.

[gurvindersingh]

+1

[lftgl]

+1

[ghost]

+1

[ShoeKSU]

+1

[typerlc]

+1

[rnavarro]

+1

[xavierbaude]

+1

[alex-LE]

+1

[klamar]

+1

[MatthiasBittner]

+1

[Kazuma]

+1

[dhawani]

+1

[stha]

+1

[kayrus]

+1

[delfuego]

+1

[ddes]

+1

[SYNchroACK]

+1

[kiranos]

+1

[ursweiss]

+1

[delfuego]

Is there a chance of seeing local time soon-ish? My brain is starting to hurt converting from UTC... :/

[dhawani]

You can use my fork till that time.

https://github.com/dhawani/kibana

[bergemalm]

+1

[grant-osborne]

+1

[Hydhen]

+1

[h3x3d]

+1

[cdeck]

+1

[ehartford]

It seems to me that the user's preferred timezone and date/time display format settings are a presentation/view issue not a backend issue. So Kibana would be the right place to expose this.

[frameloss]

I agree it would be nice to have time support in the UI.

It is probably too expensive for high-volume log flows, but I am using something along the lines of this in my filters:

        date {
            match => ["timestamp.raw", "MMM  d HH:mm:ss", "MMM dd HH:mm:ss"]
            timezone => "America/Denver"
            add_field => { "timestamp" => "%{@timestamp}" }
        }
        ruby {
          code => "require 'time'; event['timestamp'] = Time.parse(event['timestamp']).localtime.strftime('%Y-%m-%d %H:%M:%S:%L')"
        }

[hryamzik]

@rashidkpc it misses format support, we have a unix timestamp that could be converted with javasctipt but there's no way to define any rules...

[JulienBlancher]

+2

[mradamlacey]

+1

[climbbike]

the original request here is supported in Kibana now from what I can tell (timezone support in log tables and not just graphs . . . . works great for us after upgrading Kibana). Seems like the all misc. requests other than that, would get proper attention if they were there own issues . . .

[mradamlacey]

Maybe I'm missing something, I'm running the latest download (3.1.0-rc19105c) and I don't see a timezone option in the dashboard configuration or the table panel configuration.

[mradamlacey]

Sorry - replied too soon.

It looks like in the Table settings under 'Panel' there is a 'Local Time'
checkbox. Looks like it only supports timestamps in ISO8601 format?

On Wed, Sep 17, 2014 at 12:34 PM, jpieruc notifications@github.com wrote:

the original request here is supported in Kibana now from what I can tell
(timezone support in log tables and not just graphs-works great for us
after upgrading Kibana). Seems like the all misc. requests other than that,
would get proper attention if they were there own issue . . .

—
Reply to this email directly or view it on GitHub
#95 (comment).

---

Adam Lacey

[climbbike]

There is no timezone option. just an option to display in localtime. It's been there sometime for histograms and we needed it for tables as well and it's there now in the latest version we just upgraded to.

[climbbike]

by the way, we had been working around this by using the code filter to run some ruby that added a field in local time. So you really want a custom field showing timestamps in localtime, you can. Of course that won't work if you have kibana users in different time zones.

[climbbike]

Just saw your second comment. You should be setting your timestamp using the Date filter anyhow. If you don't you won't get correct timestamps. They will be the time when logstash processed it, not the time in the log

[boubou191911]

Small question.
I did not check in the code but does Kibana takes into account the locatime at the date the time was asked.

I mean: in the datepicker I choose a local time range over the DST date e.g. from 25 oct 8am til 27 oct 2014 8AM. the timezone offset is not the same for the from date and the to date.
from = 2014-10-25T08:00:00.000+02:00
to = 2014-10-27T08:00:00.000+01:00
In UTC it translates to
from = 2014-10-25T06:00:00.000Z
to = 2014-10-27T07:00:00.000Z

Does Kibana take this into account?

[GodHong]

+1 It is not really good for users!

[monotek]

+1

[climbbike]

What exactly are you guys looking for? This was fixed a long time ago.

[monotek]

not in kibana 4 or not?

[KrishnaPG]

At the least users should have the option to select the original time (the timestamp as-is stored in the backend) or their own local time in UI.

1. UI support for UTC is mandatory when user base is cross-geographic
2. UI support for local time zone is unavoidable when performing exploratory analysis

Forcing only UTC or only local-time zone will not help users.

Not sure if Kibana 4 fixed this problem. Our backend stored the date in UTC and Kibana 4 seems to be forcing me to use my local time.

We have cross-geographic users who access same reports from multiple locations - imagine their confusion when they try to address some problem and everyone talks in their local time zone.

[rtkmhart]

All of our systems are running in UTC timezone, and data is in elasticsearch in UTC. Our customers and employees are spread across multiple timezones. What we need is to be able to set Kibana to a timezone of choice, which could be any of the timezones including local, UTC or something else. Setting one panel to a different timezone isn't enough, I need to be able to set the entire app to a different timezone.

[kylebrandt]

Would also like to be able to set Kibana to a UTC time.

[arganzheng]

+1

[logston]

+1 for Kibana 4 + ability to set UTC as default TZ

[kjsteuer]

+1 the ability to toggle view in UTC

[bburket]

+1

[jovistruck]

+1
Using Kibana 3 and though the graph options Time Options have a timezone correction set to browser, it wouldn't correct it.

@rashidkpc

[xiaoping378]

+1 for Kibana 4 + ability to set the default TZ

[spalger]

@xiaoping378 please follow #1600

[prashantp48]

I want to convert my PDT timezone to IST timezone, but date filter its not working. pls help.