User Guide and Manual for Project Canary

More documents

Recommendations

Info

The only options available on this page are viewing or downloading Project Canary documentation. The menu on the left lists the documents available for download or viewing in the browser. Currently, these documents include: The Project Canary Overview The Project Canary User Guide and Manual (this document) The Project Canary FAQ README files for various portions of the Project Canary software including Project Canary server software Project Canary client probe software Project Canary server-side web software There is also a download link on the left so one can download a copy of Project Canary from this page. It is strongly recommended to read through all the README files for each release of Project Canary software as those will include late-breaking news, release notes, and other errata that may not have had time to make it into the formal Project Canary documentation. Chapter 3: Dashboard Tab 3.1: Dashboard Tab: Root Page The Dashboard Tab is where servers are grouped and data on individual servers can be found. The root page of the Dashboard Tab looks like this: User Guide and Manual for Project Canary Page 14
By default, servers are grouped into “Geos” and “Campuses.” Multiple “Campuses” make up a “Geo” as is shown above. This is configurable in the server_to_geo.cfg file. Details on how to name and/or rename “Geos” and “Campuses” are available in the Project Canary Installation and Configuration Guide. 3.2: Dashboard Tab: Runaway Link Next to the “Geo” name is a “Runaway” link. This link lists all processes that Project Canary software thinks are runaway processes and make good candidates for termination. Clicking on the “Runaway” link brings one to a page listing the owner of the alleged runaway process, the server it is running on, how much CPU time it has used, etc. This list is a sorted list based on the output from ps(1) which the client software runs at regular intervals as part of its data collection process. User Guide and Manual for Project Canary Page 15
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: Here one can access the various rep
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 and 36: A Sun Ray server or diskless workst
Page 37 and 38: perform cross-architecture communic
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?