User Guide and Manual for Project Canary

More documents

Recommendations

Info

Project Canary was originally created to show where load comes from on a Sun Ray Server so that systems administrators could watch for trends and correct performance problems before they developed into larger issues. Project Canary software has also proved capable of exposing load issues on any server running the Solaris Operating System, from version 2.6 through version 10 on both SPARC and x86 platforms as well as machines running the Linux Operating System. If you do not have Project Canary software installed, please refer now to the Project Canary Installation and Configuration Guide and follow the installation instructions. This document, the User Guide and Manual for Project Canary will prove worthless without having a working installation of Project Canary software to refer to. 1.1: Design Criteria The design criteria initially used to create Project Canary software included, but was not limited to: • No formal installation of software on machines to be monitored • No requirement to create special accounts on machines to be monitored • The same software will work without modification on multiple operating systems, hardware platforms, and machine types - Currently, Project Canary software works without modification on clients running the Solaris Operating System (both SPARC and x86) and is confirmed to run on and is supported on two flavors of the Linux Operating System, SuSE and Red Hat. • The software will not interfere with the function of any other client or application software running on a client being monitored • Root privileges are not required to gather data from machines being monitored • Crontab entries are not required to run the software on client machines being monitored • The software must match performance against many of the SE-Toolkit rules so that users can take advantage of those suggestions and recommendations • The software must display the load generated by Web Browsers, GNOME sessions, the Xsun server, Java applets, and StarOffice sessions, specifically. • The software must provide network performance graphs showing Input and Output packets per second, error codes, and other statistics and data useful when examining network throughput and performance 1.2: How Project Canary software gathers data from machines it monitors Servers are probed using a shell script that each machine monitored executes locally. For machines running the Solaris Operating System, this shell script is called canary_solaris.sh and for machines running the Linux Operating System, it is called canary_linux.sh Both shell scripts are included with Project Canary software. The canary_solaris.sh and canary_linux.sh scripts execute the following 48 commands on every client machine monitored by Project Canary software as shown on the next page: Data Gathering (continued) 1. /usr/bin/showrev 2. /usr/sbin/psrinfo -v | grep operates | sort | uniq -c 3. /usr/sbin/prtconf -p -v | grep banner-name: User Guide and Manual for Project Canary Page 6
4. /usr/bin/uptime 5. /usr/bin/prstat -c -n 9999,99 1 1 | nawk -f prstat1.awk | sort | ... 6. /usr/bin/ps -eo s,comm,user,pid | egrep ^O|^R | sort 7. cleanRunaways -m 3 -r -t 2 8. /usr/bin/prstat -c -n 99,999 -a 1 1 9. /usr/bin/prstat -c -n 1,1 -Z 1 1 10. /usr/bin/prstat -m -c -n 9999,999 1 1 | nawk -f p_m.awk |sort 11. /usr/sbin/swap -l 12. /usr/bin/netstat -i 13. /usr/bin/netstat -s -P tcp 14. /usr/bin/netstat -s -P udp 15. /usr/bin/netstat -k | nawk ... 16. /usr/bin/gconftool-2 ... 17. shmlist 18. /usr/bin/grep ^set /etc/system 19. /usr/bin/cat /etc/auto_master 20. /usr/bin/grep automount /etc/init.d/autofs 21. /usr/bin/ypcat -k auto.master 22. /usr/bin/grep AUTOMOUNT /etc/default/autofs 23. /usr/bin/cat /etc/release 24. /usr/bin/netstat -anP tcp -f inet | nawk '{print $NF}' | sort | ... 25. /usr/bin/iostat -xn 30 2 | nawk '{ if ($10 >4) print $0; if ( $1 ... 26. /usr/bin/mpstat 30 2 27. /usr/bin/vmstat 30 2 28. /usr/sbin/ping -s DATA_SERVER 56 3 29. /usr/sbin/traceroute DATA_SERVER 30. /usr/bin/df -lk 31. /usr/bin/sar -k 15 4 32. /usr/bin/sar -a 15 4 33. /usr/bin/sar -g 15 4 34. /usr/bin/sar -u 15 4 35. /usr/bin/sar -d 15 4 36. /usr/bin/sar -r 15 4 37. /usr/bin/ps -ef | grep metacity (or) ps -ef | grep dtwm 38. ce 39. /usr/bin/ps -eo pid,nlwp,comm | nawk ... 40. /usr/bin/who -H | egrep dtlocal|dtremote 41. utwho -c 42. /opt/SUNWut/sbin/utcrypto 43. /usr/bin/ls -1a /tmp | grep Xauth | wc 44. /usr/bin/pkgparam SUNWuto VERSION 45. st.xx files | nawk st.awk 46. /usr/bin/ls -l /tmp/.cleanRunaways/*state 47. /usr/sbin/ifconfig -a 48. /usr/bin/ps -eo pid,user,vsz,rss,s,pri,nice,time,etime,pcpu,nlwp ... The monitoring script uses approximately 19 seconds of CPU time and has an elapsed time (clock time to run) of approximately 90 seconds. The output of this script is stored in the local /tmp directory of the client being monitored temporarily before being sent to the central Project Canary monitoring server to be incorporated into the Web display. All data gathered from clients is sent to the central Project Canary monitoring server and must be viewed using the Web interface. Project Canary software does not support viewing data directly on client machines being monitored. The temporary file generated by the client software is overwritten every time Project Canary gathers data from the client. User Guide and Manual for Project Canary Page 7
Page 1 and 2: User Guide and Manual for Project C
Page 3 and 4: Chapter 1: Project Canary Overview.
Page 5: 4.13: Graph PID[s] Report..........
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 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?