VTAdmin: Initiate workflow details tab

[beingnoble03]

Description

This PR adds a new tab Details which extracts the Workflow Show and Workflow Status output into structured UI elements. The Details tab includes

• Summary: Gives the overall status of the workflow. Streams status (how many in running, copying, throttling, stopped, error phase), traffic status (whether reads or writes are switched), maximum vreplication lag. If switched, link to reverse workflow.
• Streams: Info about each stream of the workflow. State, stream message, transaction timestamp, database name.
• If in copying phase, progress of each table (i.e. Total Bytes, Bytes Copied, Total Rows, Rows Copied.)
• Recent logs from each stream, each log entry with log type, stream state, update timestamp, log message, count.

Related Issue(s)

• Fixes VTAdmin: Workflow Details tab #16537

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.92%. Comparing base (81ed314) to head (ee97ac2).
Report is 15 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16570      +/-   ##
==========================================
- Coverage   68.96%   68.92%   -0.04%     
==========================================
  Files        1562     1562              
  Lines      200730   200855     +125     
==========================================
+ Hits       138430   138436       +6     
- Misses      62300    62419     +119     

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

[beingnoble03]

Screenshots for single stream:

Screenshots for multiple streams:

[rohit-nayak-ps]

Excellent work. Only issue I see atm is whether we load the tab upfront or lazily.

[rohit-nayak-ps]

Do we load the Details info all the time? If so, we should only load on clicking the tab, since there are a large number of shards that could take a lot of time.

[beingnoble03]

We are loading the details info when we click on the tab.

[rohit-nayak-ps]

We should figure out a way to dynamically load some of the details info like logs or streams in clusters with a very large number of shards. We can do that later once we have some experience in the field with the new UI. Just mentioning it here for future reference.

[notfelineit]

You'll want to supply a key here, since it's a mapped react component:

Suggested change

	<tr>
	<tr key={row.workflowData.workflow.name}>

or another unique identifier!

[beingnoble03]

Done.

[notfelineit]

Awesome, thank you!