This repository was archived by the owner on Jul 9, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Add SCSt 2.0 and Micrometer compatibility #51
Milestone
Comments
This story depends on spring-projects/spring-boot#12594 |
We would also have to review the operational specifics of |
Also, note, we do not have any specifical handling in Flo for |
tzolov
added a commit
to tzolov/spring-cloud-dataflow-metrics-collector
that referenced
this issue
Apr 9, 2018
Resolve spring-attic#51 - New metrics have already the rates and latencies precomputed. Therefore the rate compute logic is removed from the ApplicationMetricsService. For the same reason the Cache keeps only the last metrics for an app instance (use to keep last 2 metrics). - New ApplicationMetrics and Metrics model classes to represent the JSON format - New AggregateMetrics model class to represent the metrics aggregated across multiple app instances - New compute logic for the Application#getAggregateMetrics - The MetricJsonSerializer is altered to adapt the new Metrics format into the REST format expected by the SCDF Metrics Controller the UI
This was referenced Apr 9, 2018
tzolov
added a commit
to tzolov/spring-cloud-dataflow-metrics-collector
that referenced
this issue
Apr 11, 2018
Resolve spring-attic#51 - Extend MetricAggregator to accept and dispatch Metrics coming from SpringBoot 1.x apps as well as MicrometerMetrics from SpringBoot2/SCSt2 apps. - Uses the spring.integration.send string as metrics type discriminator. - MetricAggregator converts on the fly the received MicrometerMetrics classes into Metrics such. - The MicrometerMetrics multidimensional (e.g. multi-tag) identity is converted into hierarchical Metrics name convention. - Only the spring.integration.x MicrometerMetrics metrics are filtered in. - The MicrometerMetrics have the rates precomputed. Therefore the ApplicationMetricsService rate computation logic is applied only to the Metrics (1.x) metrics. - New compute logic for the Application#getAggregateMetrics - Support for mixed SCSt1.x and SCSt2.x app metrics - Fix the Metrics 1.x tests and add MicrometerMetric tests
tzolov
added a commit
to tzolov/spring-cloud-dataflow-metrics-collector
that referenced
this issue
Apr 11, 2018
Resolve spring-attic#51 Resolve spring-attic#55 - Extend MetricAggregator to accept and dispatch Metrics coming from SpringBoot 1.x apps as well as MicrometerMetrics from SpringBoot2/SCSt2 apps. - Uses the spring.integration.send string as metrics type discriminator. - MetricAggregator converts on the fly the received MicrometerMetrics classes into Metrics such. - The MicrometerMetrics multidimensional (e.g. multi-tag) identity is converted into hierarchical Metrics name convention. - Only the spring.integration.x MicrometerMetrics metrics are filtered in. - The MicrometerMetrics have the rates precomputed. Therefore the ApplicationMetricsService rate computation logic is applied only to the Metrics (1.x) metrics. - New compute logic for the Application#getAggregateMetrics - Support for mixed SCSt1.x and SCSt2.x app metrics - Fix the Metrics 1.x tests and add MicrometerMetric tests
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As a developer, I'd like to upgrade to SCSt 2.0, so I can bring Micrometer compatibility.
Background:
Boot 1.x based
Metric
infrastructure is replaced with Micrometer in the 2.0 release. SCSt 2.0 builds on the new foundation already. The goal is to convertmetrics-collector
into another SCSt 2.0 consumer/sink.Acceptance:
The text was updated successfully, but these errors were encountered: