[
https://jira.jboss.org/jira/browse/JOPR-55?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy commented on JOPR-55:
-------------------------------------
As for 2749, I agree that this is a weak approach. Alternatives were discussed but
nothing obvious jumped out. As it stands, discovery is performed in a vacuum. It is not
communicated or coordinated between plugins that a process has triggered resource
creation, even between dependent plugins. Higher order logis is needed, if Process A
generates a Resource in Plugin X. Discovery for that process should be ignored, or
skipped, for super plugins of X.
Ideas welcome. If we revert 2749 today we'll end up with Tomcat processes resulting
in JMX and Tomcat Server resources.
Tomcat plugin Discovery
-----------------------
Key: JOPR-55
URL:
https://jira.jboss.org/jira/browse/JOPR-55
Project: Jopr
Issue Type: Sub-task
Components: Plugin - Tomcat
Affects Versions: 2.1
Reporter: Jay Shaughnessy
Assignee: Jay Shaughnessy
Fix For: 2.2
This is to track the Discovery portion of the Standalone Tomcat plugin. This encompasses
Server/Service hierarcrhy definition, resource definition ( including properties,
metrics..), process discovery etc..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira