User Guide and Manual for Project Canary

More documents

Recommendations

Info

The red lines denote CPU utilization and the green lines denote the number of Xsun processes running. Typically, there is one Xsun process for each display being managed. Note that the red lines move up and down during the workday. This particular Sun Ray server is on an engineering campus so the day “starts” a little later and “ends” a little later than it would in a standard office environment with more rigid working hours. In the off-hours and at usual “meeting times” and lunchtimes, the red lines should drop significantly. If they do not, then there is a potential runaway to be investigated. Note the large drop in the graph above where the number of Xsun processes dropped significantly on a normally busy server. One may infer that there were service outages of one form or another on that server from this graph or that many users may have been “idled out” and forcibly logged out of the Sun Ray server. Project Canary software also tracks Java applications and the resources consumed by the Java Virtual machines running. This is useful on all types of servers since many new applications use Java as part of their operation. This is especially important to track on data center servers which may be using Java to connect applications or User Guide and Manual for Project Canary Page 36
perform cross-architecture communication. 3.5.8: Java, Java Virtual Machine, and JRE Statistics Graph A graph of Java on a typical data center server looks like this: The red lines signify CPU utilization and the green lines indicate the number of Java applications running. Note that on the data center server, Java use is low. On the Sun Ray server, with users running Java applications and downloading applets to execute through web browsers, the Java graph is startlingly different, as shown below: User Guide and Manual for Project Canary Page 37
Page 1 and 2: User Guide and Manual for Project C
Page 3 and 4: Chapter 1: Project Canary Overview.
Page 5 and 6: 4.13: Graph PID[s] Report..........
Page 7 and 8: 4. /usr/bin/uptime 5. /usr/bin/prst
Page 9 and 10: client being monitored. A ten minut
Page 11 and 12: On this page, one sees a basic guid
Page 13 and 14: Here one can access the various rep
Page 15 and 16: By default, servers are grouped int
Page 17 and 18: As shown above, clicking on a “Ca
Page 19 and 20: This page shows when the Project Ca
Page 21 and 22: Each of the graphs shown in the pre
Page 23 and 24: Scrolling down on the page will rev
Page 25 and 26: Below is a graph taken from a typic
Page 27 and 28: The Blue line shows how many iterat
Page 29 and 30: This graph shows how many interrupt
Page 31 and 32: On a Sun Ray server with multiple u
Page 33 and 34: using it. If the red CPU utilizatio
Page 35: A Sun Ray server or diskless workst
Page 39 and 40: The X-axis shows the number of proc
Page 41 and 42: These statistics are collected from
Page 43 and 44: Note again, there are spikes at nig
Page 45 and 46: The network appears to be fairly sp
Page 47 and 48: From this graph, it would appear th
Page 49 and 50: The Data Center server is not runni
Page 51 and 52: Since the data center server is not
Page 53 and 54: The graph above shows that the data
Page 55 and 56: As the previous graphs have shown,
Page 57 and 58: Older versions of Sun Ray Server So
Page 59 and 60: When clicking on the Reports Tab, o
Page 61 and 62: The above is an example. To create
Page 63 and 64: From this screen, one must select a
Page 65 and 66: As described previously, this table
Page 67 and 68: This report is identical to the “
Page 69 and 70: The CPU Load (animated) report show
Page 71 and 72: systems administrator is advised to
Page 73 and 74: There are four reports on various c
Page 75 and 76: As described earlier in this docume
Page 77 and 78: As with all reports available from
Page 79 and 80: This graph is useful to see if the
Page 81 and 82: This chart is useful for monitoring
Page 83 and 84: As shown above, users who have logi
Page 85 and 86: From the graph shown on the previou
Page 87 and 88:
as CDE and GNOME which have been se
Page 89 and 90:
4.11.4: Total Resident Memory Consu
Page 91 and 92:
4.11.6: Total CPU Minutes Used for
Page 93 and 94:
4.11.8: Percentage of memory consum
Page 95 and 96:
4.11.10: Total resident memory cons
Page 97 and 98:
4.11.12: Total CPU minutes consumed
Page 99 and 100:
4.11.14: Percentage of server memor
Page 101 and 102:
Also note the power-user at the end
Page 103 and 104:
4.11.18: Total CPU minutes for all
Page 105 and 106:
The CPU Profiles report page looks
Page 107 and 108:
Note that peaks and valleys appear
Page 109 and 110:
As with the automount png graph des
Page 111 and 112:
Note that while ncsd doesn't appear
Page 113 and 114:
Here on this graph, it is shown tha
Page 115 and 116:
utdsd, like other system service da
Page 117 and 118:
The main purpose of this report is
Page 119 and 120:
Overview of Project Canary Software
Page 121 and 122:
management system. A2.2: I don't wa
Page 123 and 124:
Crypto 74 Crypto Settings report 78
Page 125 and 126:
unaway processes 9, 12, 16, 23p., 6
show all

User Guide and Manual for Project Canary

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?