Failed to load explore view data
- Dominant language
- Go
- Stars
- 11.7k
- Forks
- 802
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 80
Description
#### Describe the bug
I use s3 to store data,When I query the data of a certain day in the past, I get the following error:

#### To Reproduce
Steps to reproduce the behavior:
For the server configuration, I only changed the s3 storage part and limits:
max_query_length: 30d
#### Expected behavior
A clear and concise description of what you expected to happen.
#### Environment
- Infrastructure: Kubernetes- Deployment tool: helm,
#### Additional Context
The scenario I often use is to trace back the performance data when an exception occurred in the past. I hope that it can be displayed well when querying the previous data.
In addition to the configuration I modified, is there any other configuration that can help optimize the use of s3 storage?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.