Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Failure response time not displaying in UI.
See original GitHub issuelocust.events.request_failure takes response_time but does nothing with it.
In fact, the UI shows 0’s even if a response time is reported with the request_failure event:
Issue Analytics
- State:
- Created 9 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Response Time Limits: Article by Jakob Nielsen
How users react to delays in a user interface, whether website or application. The 3 main response time limits are determined by human...
Read more >Why Application insight not showing Failed requests, Server ...
I have two project Web app and Web API. I have integrated application insight to them simply by right-click on my project and...
Read more >Graph Error when enabling Response time edges · Issue #2549
Steps to reproduce the behavior: Change graph edge to show Response time. Expected behavior. No error should occur.
Read more >How to troubleshoot UI Actions either or not showing or not ...
If a UI Action is not showing you can check the Table, Condition, Visibility, and Action Name. If a UI Action shows but...
Read more >Response time chart types (APM and browser)
Response time charts; Histograms; Percentile line graphs. For example, on the APM summary UI page, the chart types are represented with these icons:....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, I think we should include the response time of failures as long as we get an HTTP response from the server, but not for other failures such as socket, dns, or connection errors.
To achieve this we should make it so that if response_time is provided by the failure event, it’ll be included in the stats. And then in the HTTP client make sure that we only provide response_time to the failure event when we’ve gotten an actual HTTP response.
Can’t reproduce in current version.