| Wiki Markup |
|---|
h2. What should we measure?
h3. All applications should have the following metrics in common:
*Number of Users*
* by community (department, MIT affiliation, etc)
* total unique users
* number of user accounts
* number of user sessions/logins
* by time period (peak usage, average usage)
*System Utilization*
* CPU
* memory
* disk space
* network
*Application Specifics (metrics here vary from applications to application)*
* wikis (automated)
* DW (automated)
* Roles (automated)
* Jira
* Jabber
* RT
* Web Servers (Apache, etc)
* Web Services (UAWS)
* Thalia (manual)
* Stellar (manual)
* Touchstone unique users by app and logins by app (should merge with DW to report by community)
* Developer Tools
* Kerberos (via RT, bug fixes, commits to tree)
h3. How do we measure them?
*Getting information into the Data Warehouse*
* in a standard format
* except system utilization
*SAMM would provide a continuous view of these stats*
* show trends
* how app behaves (learn more about environment)
* blending of stats (users, memory, spikes)
h3. What do we have right now?
|| Number of Users \\ || users by community \\ || total unique users \\ || user accounts \\ || logins \\ || time period \\ ||
| wikis | DLC \\ | Y \\ | Y \\ | \\ | Y \\ |
| jira | | \\ | \\ | \\ | \\ |
| jabber | | \\ | \\ | \\ | \\ |
| request tracker \\ | | \\ | \\ | \\ | \\ |
| data warehouse \\ | DLC \\ | Y \\ | Y \\ | \\ | Y \\ |
| roles | DLC \\ | Y | | | |
| web servers \\ | | | | | |
| web services \\ | | | | | |
| thalia | ? \\ | Y \\ | Y \\ | | |
| stellar | by subject, role \\ | Y | Y \\ | Y | Y |
| touchstone | | | | | |
| developer tools \\ | | | | | |
| kerberos | | | | | |
|| System Utilization \\ || CPU \\ || memory \\ || disk space \\ || network \\ ||
| wikis | | | | |
| jira | | | | |
| jabber | | | | |
| request tracker \\ | | | | |
| data warehouse \\ | | | | |
| roles | | | | |
| web servers \\ | | | | |
| web services \\ | | | | |
| thalia | | | | |
| stellar | | | <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->\~1 terabyte | |
| touchstone | | | | |
| developer tools \\ | | | | |
| kerberos | | | | |
|| Application Specifics || \\ || \\ || \\ || \\ || \\ ||
| wikis | \# of transactions (edits, comments) | \# of pages \\ | \# of authors \\ | \# of sites \\ | \# of views \\ |
| jira | | | | | |
| jabber | | | | | |
| request tracker \\ | | | | | |
| data warehouse \\ | | | | | |
| roles | \# of transactions (creations, deletions and updates) \\ | | | | |
| web servers \\ | | | | | |
| web services \\ | | | | | |
| thalia | \# of images \\ | \# of domains \\ | storage per domain \\ | | |
| stellar | \# of courses \\ | | | 10,000\+ | |
| touchstone | \# of access requests (by application) \\ | method (username, certs or kerb) \\ | | | ? |
| developer tools \\ | | | | | |
| kerberos | RT bug fixes \\ | commits to tree \\ | | | |
h3. What requires more work?
* see grid above for whats missing
* how do we allocate resources?
All applications should have the following metrics in common:Number of Users - by community (department, MIT affiliation, etc)
- total unique users
- number of user accounts
- number of user sessions/logins
- by time period (peak usage, average usage)
System Utilization - CPU
- memory
- disk space
- network
Application Specifics (metrics here vary from applications to application) - wikis (automated)
- DW (automated)
- Roles (automated)
- Jira
- Jabber
- RT
- Web Servers (Apache, etc)
- Web Services (UAWS)
- Thalia (manual)
- Stellar (manual)
- Touchstone unique users by app and logins by app (should merge with DW to report by community)
- Developer Tools
- Kerberos (via RT, bug fixes, commits to tree)
How do we measure them?Getting information into the Data Warehouse - in a standard format
- except system utilization
SAMM would provide a continuous view of these stats - show trends
- how app behaves (learn more about environment)
- blending of stats (users, memory, spikes)
What do we have right now? Number of Users
| users by community
| total unique users
| user accounts
| logins
| time period
|
|---|
wikis | DLC
| Y
| Y
|
| Y
| jira | |
|
|
|
| jabber | |
|
|
|
| request tracker
| |
|
|
|
| data warehouse
| DLC
| Y
| Y
|
| Y
| roles | DLC
| Y | | | | web servers
| | | | | | web services
| | | | | | thalia | ?
| Y
| Y
| | | stellar | by subject, role
| Y | Y
| Y | Y | touchstone | | | | | | developer tools
| | | | | | kerberos | | | | | |
System Utilization
| CPU
| memory
| disk space
| network
|
|---|
wikis | | | | | jira | | | | | jabber | | | | | request tracker
| | | | | data warehouse
| | | | | roles | | | | | web servers
| | | | | web services
| | | | | thalia | | | | | stellar | | | ~1 terabyte | | touchstone | | | | | developer tools
| | | | | kerberos | | | | |
Application Specifics |
|
|
|
|
|
|---|
wikis | # of transactions (edits, comments) | # of pages
| # of authors
| # of sites
| # of views
| jira | | | | | | jabber | | | | | | request tracker
| | | | | | data warehouse
| | | | | | roles | # of transactions (creations, deletions and updates)
| | | | | web servers
| | | | | | web services
| | | | | | thalia | # of images
| # of domains
| storage per domain
| | | stellar | # of courses
| | | 10,000+ | | touchstone | # of access requests (by application)
| method (username, certs or kerb)
| | | ? | developer tools
| | | | | | kerberos | RT bug fixes
| commits to tree
| | | |
What requires more work?- see grid above for whats missing
- how do we allocate resources?
|