fix bug by keeping track of interval within the explorer

[derek-ho]

Signed-off-by: Derek Ho [email protected]

Description

Keeps track of interval selected in the explorer and timechart header so that the interval is not reset whenever the query changes

Issues Resolved

#1249

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[joshuali925]

what's the difference between startingTime and startTime?

[derek-ho]

I may need someone more familiar with this component/code (@mengweieric ?) - but from what I can tell this explorer is rendered by both Application analytics and event analytics - for event analytics startTime is undefined, resulting in auto interval not getting picked up. In either case startingTime should be already set above based on the query so I think(?) this is a more general implementation

[mengweieric]

Yes confirmed. Event analytics previously does not use any passed in start/starting time, I think later there's live tail introduced with starting/ending time for differentiating existing start/end time just for reusing the exiting data fetching

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 41.70%. Comparing base (a1527c5) to head (4cae301).
Report is 4 commits behind head on 2.4.

Files with missing lines	Patch %	Lines
...ics/explorer/timechart_header/timechart_header.tsx	50.00%	1 Missing ⚠️
...alytics/components/dashboard/dashboard_content.tsx	0.00%	1 Missing ⚠️
...ace_analytics/requests/services_request_handler.ts	0.00%	1 Missing ⚠️

❌ Your project status has failed because the head coverage (41.70%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@              Coverage Diff              @@
##                2.4    #1266       +/-   ##
=============================================
- Coverage     70.27%   41.70%   -28.57%     
  Complexity      292      292               
=============================================
  Files            42      296      +254     
  Lines          2395    17747    +15352     
  Branches        248     4277     +4029     
=============================================
+ Hits           1683     7401     +5718     
- Misses          571    10174     +9603     
- Partials        141      172       +31     

Flag	Coverage Δ
dashboards-observability	37.24% <50.00%> (?)
opensearch-observability	70.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

The base branch was changed.

[joshuali925]

CI failed, retrying. not sure why recently bootstrap often fails