[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikita Amelchev updated IGNITE-12943: - Fix Version/s: 2.17 (was: 2.16) > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.17 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Plehanov updated IGNITE-12943: --- Fix Version/s: 2.16 (was: 2.15) > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.16 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-12943: -- Fix Version/s: 2.15 (was: 2.14) > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.15 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12943: - Fix Version/s: 2.14 (was: 2.13) > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.14 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-12943: Fix Version/s: 2.13 (was: 2.12) > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.13 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Gidaspov updated IGNITE-12943: - Fix Version/s: (was: 2.11) 2.12 > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.12 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12943: - Fix Version/s: (was: 2.10) 2.11 > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.11 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12943: --- Fix Version/s: (was: 2.9) 2.10 > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.10 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12943: - Fix Version/s: (was: 2.8.1) 2.9 > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.9 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12943: Labels: IEP-35 (was: ) > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Labels: IEP-35 > Fix For: 2.8.1 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12943: Description: As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add {{Metrics Filtering}} section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics was: As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.8.1 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add {{Metrics Filtering}} section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > {{MetricExporterSpi.setExportFilter}} JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > {{MetricExporterSpi.setMetricsFilter}} to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12943: Description: As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics was: As per {MetricExporterSpi.setExportFilter} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.8.1 > > > As per {{MetricExporterSpi.setExportFilter}} contract, the user can filter > out metrics for a specific exporter instance. For instance, this is how we > can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add `Metrics Filtering section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > `MetricExporterSpi.setMetricsFilter` to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12943: Description: As per {MetricExporterSpi.setExportFilter} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics was: As per {code}MetricExporterSpi.setExportFilter{code} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.8.1 > > > As per {MetricExporterSpi.setExportFilter} contract, the user can filter out > metrics for a specific exporter instance. For instance, this is how we can > ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add `Metrics Filtering section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > `MetricExporterSpi.setMetricsFilter` to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12943: Description: As per {code}MetricExporterSpi.setExportFilter{code} contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics was: As per `MetricExporterSpi.setExportFilter` contract, the user can filter out metrics for a specific exporter instance. For instance, this is how we can ask a JMX exporter instance to ignore the cache metrics: {code} JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); cfg.setMetricExporterSpi(jmxSpi); {code} We should add `Metrics Filtering` section to this documentation page [1] explaining how to use the filtering. Also, I would clarify in the `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out certain metrics from a specific exporter. Also, should we possibly rename the method to `MetricExporterSpi.setMetricsFilter` to make things crystal clear? [1] https://apacheignite.readme.io/docs/new-metrics > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.8.1 > > > As per {code}MetricExporterSpi.setExportFilter{code} contract, the user can > filter out metrics for a specific exporter instance. For instance, this is > how we can ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add `Metrics Filtering section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > `MetricExporterSpi.setMetricsFilter` to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12943) Document how to filter out metrics from registries
[ https://issues.apache.org/jira/browse/IGNITE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12943: Component/s: documentation > Document how to filter out metrics from registries > -- > > Key: IGNITE-12943 > URL: https://issues.apache.org/jira/browse/IGNITE-12943 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis A. Magda >Priority: Major > Fix For: 2.8.1 > > > As per `MetricExporterSpi.setExportFilter` contract, the user can filter out > metrics for a specific exporter instance. For instance, this is how we can > ask a JMX exporter instance to ignore the cache metrics: > {code} > JmxMetricExporterSpi jmxSpi = new JmxMetricExporterSpi(); > jmxSpi.setExportFilter(mreg -> !mreg.name().startsWith(«cache»)); > cfg.setMetricExporterSpi(jmxSpi); > {code} > We should add `Metrics Filtering` section to this documentation page [1] > explaining how to use the filtering. Also, I would clarify in the > `MetricExporterSpi.setExportFilter` JavaDocs that the method filters out > certain metrics from a specific exporter. > Also, should we possibly rename the method to > `MetricExporterSpi.setMetricsFilter` to make things crystal clear? > [1] https://apacheignite.readme.io/docs/new-metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)