[APM] Not displaying fallback message when transaction sample is not found within time range.

[formgeist]

Kibana version: 6.5

---

https://apm.elstc.co/tyo/app/apm#/opbeans-node/transactions/request/GET~20~2Fapi?_g=(refreshInterval:(pause:!t,value:0),time:(from:now-4h,mode:quick,to:now))&transactionId=400d0cd4576694b5&traceId=fca984e094e6f5f99d6d57e318707ca7

It looks we're not displaying the fallback message when a transaction ID doesn't return a sample for the selected time range.

Failed to load resource: the server responded with a status of 404 (Not Found)
react-redux-request.js:4704 Error: Not Found
    at kfetch.ts:54
    at step (tslib.js:133)
    at Object.next (tslib.js:114)
    at fulfilled (tslib.js:104)

[elasticmachine]

Pinging @elastic/apm-ui

[jasonrhodes]

So if I'm looking at a very narrow time range and click on "View Full Trace", and the trace started just outside of the time range, we'd want to show the 404 fallback message there? I didn't realize the individual transaction/trace ID lookup was still using the time range as part of the query but that sounds pretty rough.

[sorenlouv]

So if I'm looking at a very narrow time range and click on "View Full Trace", and the trace started just outside of the time range, we'd want to show the 404 fallback message there? I didn't realize the individual transaction/trace ID lookup was still using the time range as part of the query but that sounds pretty rough

That's a good point. We should probably create another issue for that.