[JBoss JIRA] (ISPN-11427) RestMetricsResource#testMicroprofileMetricsMetadata can timeout
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11427?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11427:
---------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 10.1.4.Final
11.0.0.Dev03
Resolution: Done
Merged this on master and 10.1.x and happy with the fix. Will close the issue as we're never going to ses thousands of metrics in real-life and we're also not really going to replace JsonMetadataExporter with a more efficient alternative.
> RestMetricsResource#testMicroprofileMetricsMetadata can timeout
> ---------------------------------------------------------------
>
> Key: ISPN-11427
> URL: https://issues.redhat.com/browse/ISPN-11427
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 11.0.0.Alpha2
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 10.1.4.Final, 11.0.0.Dev03
>
>
> The testMicroprofileMetricsMetadata method times out trying to invoke a rest command. This appears to be due to scalability issues in small rye metrics with json exporter with a few thousand metrics.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11438) Additional metric registration config option: namesAsTags
by Nistor Adrian (Jira)
Nistor Adrian created ISPN-11438:
------------------------------------
Summary: Additional metric registration config option: namesAsTags
Key: ISPN-11438
URL: https://issues.redhat.com/browse/ISPN-11438
Project: Infinispan
Issue Type: Enhancement
Components: JMX, reporting and management
Affects Versions: 11.0.0.Alpha2, 10.1.3.Final
Reporter: Nistor Adrian
Assignee: Nistor Adrian
Fix For: 10.1.4.Final, 11.0.0.Dev03
Boolean options, false by default. If enabled it results in the cache manager name and cache name being added as tags rather than being included in the metric name.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11425) Missing metada for persistent counter upon server restart
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11425?page=com.atlassian.jira.plugi... ]
Ryan Emerson resolved ISPN-11425.
---------------------------------
Resolution: Done
> Missing metada for persistent counter upon server restart
> ---------------------------------------------------------
>
> Key: ISPN-11425
> URL: https://issues.redhat.com/browse/ISPN-11425
> Project: Infinispan
> Issue Type: Bug
> Components: Clustered Counter
> Affects Versions: 10.1.3.Final, 11.0.0.Alpha2
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 10.1.4.Final, 11.0.0.Dev03
>
>
> If you create a counter with a persistent storage, shutdown and spin up the server again then it's no longer possible to add a value to that counter. Instead following error appear in the CLI log:
> {code}
> Error: java.lang.IllegalStateException: ISPN029518: Metadata not found but counter exists. Counter=cnt1
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month