-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
-
False
-
-
As a developer, I'd like to refactor prometheus lookups to use swatch-product-configuration, so that I can retire tag_profile.
Don't forget about the template substitution stuff at https://github.com/RedHatInsights/rhsm-subscriptions/blob/main/src/main/java/org/c[…]scriptions/metering/service/prometheus/promql/QueryBuilder.java
That query builder injects into templates defined in properties. https://github.com/RedHatInsights/rhsm-subscriptions/blob/main/src/main/resources/application-openshift-metering-worker.yaml#L15
Note that some of those queryParam identifiers were renamed when migrated to swatch-product-configuration.
tag_profile.yaml | swatch-product-configuration yaml files |
---|---|
prometheusMetric | metrics[].prometheus.queryParams.metric |
prometheusMetadataMetric | metrics[].prometheus.queryParams.metadata_metric |
resourceName | metrics[].prometheus.queryParams.resourceName |
Done:
- The following classes contain no references to tag_profile
- InternalMeteringResource
- PrometheusMeteringController
- PrometheusAccountSource
- PrometheusMeteringController
- PrometheusMetricsTaskManager
- MeteringJob
- Remove the use of .withEventType(MeteringEventFactory.getEventType(measuredMetric.value(), productTag)) from MeteringEventFactory
QE:
Verify metering
- blocks
-
SWATCH-1242 Remove tag profile classes and data
- Closed
- is blocked by
-
SWATCH-1230 Implement swatch-product-configuration lookup methods
- Closed
-
SWATCH-1375 Unify the values of metricId and UOM in tag profile/configuration
- Closed