Observability docs for Launch #550
Conversation
| :::info | ||
| To turn on this capability, toggle on the `Launch observability` feature flag in your user settings. | ||
|
|
||
| This feature requires W&B Weave, which is not available on some Customer-managed and Dedicated Cloud. Contact your W&B representative to learn more. |
There was a problem hiding this comment.
The dashboard requires Weave 1 in particular, not sure if thats relevant. And must be turned on in user settings in SaS
|
|
||
| ## Dashboard and plots | ||
|
|
||
| Each queue now has a `Monitor` tab. When you click on the tab, W&B will gather data over the last 7 days of activity for this queue. Time ranges, grouping and filters can be controlled from the left panel. |
There was a problem hiding this comment.
Data gathering is technically independent, maybe "gather" -> "display"
|
|
||
|  | ||
|
|
||
| This plot shows, for every time period, the amount of time in minutes that jobs were queued. For example, if there were 10 jobs queued in that period, waiting for an average of 30 minutes each, the plot would show 300 minutes. |
There was a problem hiding this comment.
this is currently in seconds, but we can change that if you think jobs are going to sit in queued for a long time...
There was a problem hiding this comment.
I would actually update it to minutes in the product... things will be queued for a while...I will doc it as seconds here though.
There was a problem hiding this comment.
QQ: In my revision, I mentioned seconds. Is this still correct.
PS It'd be nice to have the units on plots...
|
|
||
| This plot shows the start and end of every job executed in a time period, with distinct colors for each run. This makes it easy to see at a glance what workloads the queue was processing at a given time. | ||
|
|
||
| Use the Select tool in the bottom right of the panel to brush over jobs to see more details in the table below. |
There was a problem hiding this comment.
| Use the Select tool in the bottom right of the panel to brush over jobs to see more details in the table below. | |
| Use the Select tool in the bottom right of the panel to brush over jobs to populate the table below. |
Co-authored-by: Griffin Tarpenning <[email protected]>
Description
What does the pull request do? If it fixes a bug or resolves a feature request, be sure to link to that issue.
Ticket
Does this PR fix an existing issue? If yes, provide a link to the ticket here:
Checklist
Check if your PR fulfills the following requirements. Put an
Xin the boxes that apply.yarn start. My changes did not break the local preview.yarn docusaurus build) was run locally and successfully without errors or warnings.maininto my feature branch before submitting this PR.