Project

General

Profile

Feature #1847

improve server instrumentation

Added by Greg Shah over 13 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
FWD - Deployment and Management Improvements
Start date:
Due date:
% Done:

0%

Estimated time:
120.00 h
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Runtime Infrastructure - Feature #1849: expose management features, configuration...to inspection and control via JMX (instead of only via the admin UI) Closed
Related to Runtime Infrastructure - Support #9514: assess, recommend and document monitoring tools plan New
Related to Runtime Infrastructure - Feature #6871: add JMX instrumentation to monitor the appserver agents Closed
Related to Base Language - Feature #6814: JMX instrumentation for FWD core, persistance and ORM layers New

History

#1 Updated by Greg Shah over 13 years ago

more logging/tracepoints; ability to log/trace for specific users?; or other ways to enable inspection more selectively; other supportability features based on production experiences;

#2 Updated by Greg Shah over 13 years ago

  • Target version set to Deployment and Management Improvements

#3 Updated by Greg Shah over 9 years ago

  • Target version changed from Deployment and Management Improvements to Deployment and Management Improvements

#4 Updated by Greg Shah over 4 years ago

I think one area of useful information may be related to the persistence layer:

  • locks
  • temp-tables
  • buffers
  • queries
  • database connections

The other area that seems very useful would be:

  • transaction manager/block details
  • any tracepoints used by the PROFILER system handle (#3819)
  • user session details

#5 Updated by Greg Shah over 4 years ago

  • Related to Feature #1849: expose management features, configuration...to inspection and control via JMX (instead of only via the admin UI) added

#7 Updated by Greg Shah over 4 years ago

As part of the work in #4785 (see #4785-746 and later), we have implemented general purpose JMX counter and timer support (see branch 3821c rev 11645). The code is in package com.goldencode.p2j.jmx.* and only the remote object protocol is instrumented as of that revision.

#8 Updated by Greg Shah over 1 year ago

We will work on this in the coming months and I want to have a more specific list of the highest value tracepoints.

Team: Please review #1847-4 and suggest specific tracepoints that should be high priority for implementation.

#9 Updated by Greg Shah over 1 year ago

  • Related to Support #9514: assess, recommend and document monitoring tools plan added

#10 Updated by Constantin Asofiei over 1 year ago

I would add a 'sampled' heap size of a context - this at least can show high-memory contexts and destroy them manually if needed. This was discussed in #8661 and IMO will be required to have a stable PASOE server.

#11 Updated by Greg Shah over 1 year ago

  • Related to Feature #6871: add JMX instrumentation to monitor the appserver agents added

#12 Updated by Greg Shah over 1 year ago

  • Related to Feature #6814: JMX instrumentation for FWD core, persistance and ORM layers added

Also available in: Atom PDF