[JBoss JIRA] (ISPN-11390) Non-components cannot export metrics
by Nistor Adrian (Jira)
Nistor Adrian created ISPN-11390:
------------------------------------
Summary: Non-components cannot export metrics
Key: ISPN-11390
URL: https://issues.redhat.com/browse/ISPN-11390
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management, Server
Affects Versions: 10.1.3.Final
Reporter: Nistor Adrian
Assignee: Nistor Adrian
Fix For: 11.0.0.Alpha2
AbstractProtocolServer's worker thread pool and the protocol are such examples. They expose managed attributes but those cannot be currently exported as microprofile metrics due to fact these are not registered in the component registry.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11390) Non-components cannot export metrics
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11390?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11390:
---------------------------------
Status: Open (was: New)
> Non-components cannot export metrics
> ------------------------------------
>
> Key: ISPN-11390
> URL: https://issues.redhat.com/browse/ISPN-11390
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management, Server
> Affects Versions: 10.1.3.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Alpha2
>
>
> AbstractProtocolServer's worker thread pool and the protocol are such examples. They expose managed attributes but those cannot be currently exported as microprofile metrics due to fact these are not registered in the component registry.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11388) Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11388?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11388:
---------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7943
> Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
> ------------------------------------------------------------------
>
> Key: ISPN-11388
> URL: https://issues.redhat.com/browse/ISPN-11388
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.1.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Alpha2
>
>
> Given the interactions between CacheIgnoreManager and AbstractProtocolServer it seems that CacheIgnoreManager should be a global component in the registry of the EmbeddedCacheManager sitting behind the AbstractProtocolServer. It should be looked up from there, or better injected, rather than being received in ProtocolServer.start method. The start method also has an overloaded version that does not take a CacheIgnoreManager to support tests the do not need it. This lack of orthogonality is annoyoing.
> Another aspect to refactor: the startInternal method receives parametters that it assigns to fields. It seems that this should have been done already in the start method. That would get rid of some clunky hacks and some comments/excuses for the said hacks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11388) Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11388?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11388:
---------------------------------
Status: Open (was: New)
> Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
> ------------------------------------------------------------------
>
> Key: ISPN-11388
> URL: https://issues.redhat.com/browse/ISPN-11388
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 10.1.0.Final
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Alpha2
>
>
> Given the interactions between CacheIgnoreManager and AbstractProtocolServer it seems that CacheIgnoreManager should be a global component in the registry of the EmbeddedCacheManager sitting behind the AbstractProtocolServer. It should be looked up from there, or better injected, rather than being received in ProtocolServer.start method. The start method also has an overloaded version that does not take a CacheIgnoreManager to support tests the do not need it. This lack of orthogonality is annoyoing.
> Another aspect to refactor: the startInternal method receives parametters that it assigns to fields. It seems that this should have been done already in the start method. That would get rid of some clunky hacks and some comments/excuses for the said hacks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11388) Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
by Nistor Adrian (Jira)
Nistor Adrian created ISPN-11388:
------------------------------------
Summary: Refactor CacheIgnoreManager - AbstractProtocolServer collaboration
Key: ISPN-11388
URL: https://issues.redhat.com/browse/ISPN-11388
Project: Infinispan
Issue Type: Enhancement
Components: Server
Affects Versions: 10.1.0.Final
Reporter: Nistor Adrian
Assignee: Nistor Adrian
Fix For: 11.0.0.Alpha2
Given the interactions between CacheIgnoreManager and AbstractProtocolServer it seems that CacheIgnoreManager should be a global component in the registry of the EmbeddedCacheManager sitting behind the AbstractProtocolServer. It should be looked up from there, or better injected, rather than being received in ProtocolServer.start method. The start method also has an overloaded version that does not take a CacheIgnoreManager to support tests the do not need it. This lack of orthogonality is annoyoing.
Another aspect to refactor: the startInternal method receives parametters that it assigns to fields. It seems that this should have been done already in the start method. That would get rid of some clunky hacks and some comments/excuses for the said hacks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months
[JBoss JIRA] (ISPN-11238) Server Logging management via CLI
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11238?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11238:
-----------------------------------
Description:
The CLI should be extended with commands to view/alter the server logging configuration.
The CLI commands should reflect the REST API that is to be implemented by ISPN-10539:
* logging list-loggers
* logging list-appenders
* logging set --level=[level] --appenders=[appender] [category]
* logging remove [category]
was:
The CLI should be extended with commands to view/alter the server logging configuration.
The CLI commands should reflect the REST API that is to be implemented by ISPN-10539:
* logging list-loggers
* logging list-handlers
* logging list-formatters
* logging set --level=[level] [category]
* logging remove [category]
> Server Logging management via CLI
> ---------------------------------
>
> Key: ISPN-11238
> URL: https://issues.redhat.com/browse/ISPN-11238
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, JMX, reporting and management, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: supportability
> Fix For: 11.0.0.Final
>
>
> The CLI should be extended with commands to view/alter the server logging configuration.
> The CLI commands should reflect the REST API that is to be implemented by ISPN-10539:
> * logging list-loggers
> * logging list-appenders
> * logging set --level=[level] --appenders=[appender] [category]
> * logging remove [category]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 10 months