[APM] Time on x-axis doesn't align with time in tooltip

[insanity13]

I cannot match the time values with the abscissa signatures.

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[sorenlouv]

Hi there 👋

This definitely looks like a bug. I would appreciate it if you can provide me with some additional information.

1. narrow down to single transaction
First, let's narrow this down to a single transaction. You can do that by filtering in the query bar (transaction.id:), and the autocomplete should suggest you some ids. Pick any you like.

2. View transaction in UI
Now you should see a single spike in the UI (If not try to expand your time range). Please hover the spike and note down the timestamp like:

3. Find the transaction in Elasticsearch via Kibana Dev Tools
Go to Kibana Dev Tools and execute the following query:

GET apm-*-transaction*/_search
{
  "_source": "@timestamp", 
  "query": {
    "match": {
      "transaction.id": "<YOUR TRANSACTION ID>"
    }
  }
}

Remember to replace the transaction.id with your own

I'm interested to hear how the timestamp in the UI compares with the timestamp in Elasticsearch. I suspect there might be a timezone issue going on. What timezone are you in?

[insanity13]

> What timezone are you in?
My time zone: SAMT (Samara Time), UTC/GMT +4 hours
Server Time zone: (UTC-05:00) Eastern Time (US & Canada)
Kibana Settings:

[insanity13]

Single Spike:

{ "took" : 5, "timed_out" : false, "_shards" : { "total" : 2, "successful" : 2, "skipped" : 0, "failed" : 0 }, "hits" : { "total" : { "value" : 1, "relation" : "eq" }, "max_score" : 11.583956, "hits" : [ { "_index" : "apm-7.4.0-transaction-000001", "_type" : "_doc", "_id" : "oSbZtm0BDne2cmEGusrJ", "_score" : 11.583956, "_source" : { "@timestamp" : "2019-10-10T18:06:13.961Z" } } ] } }

[sorenlouv]

Thanks for your help. I've created this issue to track this problem.

The main problem is that the Kibana timezone settings are different from your local browser timezone settings. APM UI unfortunately doesn't handle this case well at the moment.

As a workaround you can change the Kibana Timezone settings to match that of your local browser. This only works if you don't have colleagues in other timezones who also uses the Kibana instance.