[
http://jira.nuxeo.org/browse/NXP-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Lacoin updated NXP-2985:
---------------------------------
Assignee: Stéphane Lacoin (was: Thierry Delprat)
For AFP needs we're going to provide
* a service inventory (to do)
* an http session accounting (to do)
* a repository session accounting (already done)
* a document lifecycle events accounting based onto the audit service (to do)
* a jms queues accounting (to do)
My first checkin will be the associated MBeans definition.
> introduce the monitoring business logic
> ---------------------------------------
>
> Key: NXP-2985
> URL: http://jira.nuxeo.org/browse/NXP-2985
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Reporter: Stéphane Lacoin
> Assignee: Stéphane Lacoin
> Priority: Major
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Nuxeo monitoring is based onto JMX standard.
> From now, we already introduced a runtime management service that mainly
> helps you publishing POJO beans in JMX (see NXP-2981).
> So, we're now going to define our own business.
> Here is the main features we want to cover
> * inventory
> * status
> * accounting
> The service inventory will be mainly based onto the runtime service that is
> the component registry.
> It will mainly adapt the registration objects graph (components, extension
> points, contributions) as an mbean tree.
> The service inventory will be completed with service status. The main sources
> of information for that will be
> the runtime service and the audit service. The runtime service manage the
> service bootstrap and can report
> information about. The other natural source of information will be the audit,
> that logs events issued by services.
> We also want to be able to test the service quality by by running a basic
> test case onto the service. This will be
> the quality states. There is no dedicated place for in the system from now.
> The service inventory will be also completed by accounting informations. The
> first kind of accounting information will
> be provided directly by services. It's the accounting information that they
> can easily provide to users with no costs overhead.
> As example, directory manager provide already core sessions counters. The
> second kind of accounting information will be built
> over audit service. As events are logged into, we can extract indicators from
> them by executing some kind of pro stock logic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
