Bug 1136619 - Investigate options to expose performance data remotely
Summary: Investigate options to expose performance data remotely
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Performance
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-03 02:53 UTC by Sean Flanigan
Modified: 2015-07-29 02:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-29 02:13:17 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1136600 0 unspecified CLOSED Integrate hawt.io console, including Infinispan plugin 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1136616 0 unspecified CLOSED Ship GWT error messages to the server to be logged 2021-02-22 00:41:40 UTC

Internal Links: 1136600 1136616

Description Sean Flanigan 2014-09-03 02:53:42 UTC
Description of problem:

Allow admins to examine performance remotely (without requiring access to JBoss Management Console).


Some questions we would like to answer (historical and instantaneous):

 - How many users have editors open?  (Is now a good time to reboot?)
 - How many users are actively translating?
 - Number of active uploads/downloads
 - How often is copytrans invoked?
 - Performance stats for operations like:
  - document uploads
  - copytrans
  - stats calculations


Possible options for gathering metrics:

 - Java Simon (exposes JMX)
 - JAMon (may be obsolete)
 - adding more logging statements to our code
 - Dropwizard Metrics (Coda Hale, Yammer) (exposes JMX/JSON)
 - Netflix Servo (exposes JMX)


Possible options for publishing metrics:

 - hawt.io to expose JMX via web console
 - LogStash/Kibana to collect and analyse logging
 - Jolokia is "remote JMX with JSON over HTTP" (another option)
 - Graphite
 - JRDS


Considerations:

 - authentication/authorisation (console should be for *admin only*)
 - cluster compatibility (how to access console for a node, can we see aggregate info?)
 - performance impact


Tools reference: http://theholyjava.wordpress.com/wiki/development/ops-monitoring/

Comment 1 Zanata Migrator 2015-07-29 02:13:17 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-163


Note You need to log in before you can comment on or make changes to this bug.