Monitoring responses for a route not working properly with endTimestamp parameter
Describe the bug Even if the route is having ping,jitter and response time when we try to fetch for there graph then the response from the api call has their values as 0 creating inconsistency.
To Reproduce Steps to reproduce the behaviour:
- Go to Monitoring
- Click on any route details for the one having ping,jitter and Response values.
- You will see that No values alert.
Expected behaviour We get the correct response from the api.
Screenshots



Desktop (please complete the following information):
- OS: Ubuntu 20.04
@Harkishen-Singh @muskankhedia can you please have a look at this I think there is a problem with the api but not sure what do you think ??
@ruddi10 The API calls are fine here, this is because no data is stored in the files for the respective route. This mainly occurs when we don't receive the desired data from the route or there is a faulty route. Also, this needs to be handled in a better way in the backend.
Yeah after opening this issue I saw that for some cases it working fine but for some its failing