You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/DS-documentation/dashboard.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,16 +64,17 @@ The relative slope of your graph can also be informative.
64
64
For the run pictured at top, we discovered that a fraction of our jobs were erroring because the machines were running out of memory.
65
65
Midway through 7/12 we upped the memory of the machines in our fleet and you can see from that point on a greater slope as more jobs were finishing in the same amount of time (as fewer were failing to complete because of memory errors.)
66
66
67
-
## Distinct Logs with “cellprofiler -c”
67
+
## Distinct Logs
68
68
69
-

69
+

70
70
71
-
This widget shows you the number of different specific CellProfiler jobs that start within your given time window.
71
+
This widget shows you the number of different specific jobs that start within your given time window by plotting the number of Cloudwatch logs that have your run command in them.
72
+
In this example, our run command is "cellprofiler -c".
72
73
It is not necessarily informative on its own, but very helpful when compared with the following widget.
73
74
74
-
## “cellprofiler -c”
75
-
This widget shows you the number of times that CellProfiler is started within your log group within the given time window.
76
-
Ideally, you want this number to match the number in the previous widget as it means that each job is starting in CellProfiler only once.
75
+
## All logs
76
+
This widget shows you the number of total times that jobs are started within your log group within the given time window.
77
+
Ideally, you want this number to match the number in the previous widget as it means that each job is starting in your software only once.
77
78
78
79
If this number is consistently larger than the previous widget’s number, it could mean that some of your jobs are erroring and you’ll need to figure out why (see MemoryUtilization and Show Errors or look directly in your Cloudwatch Logs for insights).
0 commit comments