Glenn Renfro 2f0f78a2c8 Updating task metrics to micrometer 1.10
Changes include:
* Use Observable instead of metrics
* Update the setting of lowCardinalityTag to the correct events.
* Update the docs
* Remove EXTERNAL_EXECUTION_ID
* Utilize registry provided by boot instead of globalregistry
* Set the handler until Boot does this as shown on line 80 of TaskLifecycleConfiguration.
* Uses Observability long task timer

Updated to latest changes in Micrometer Observability

Updated based on code review and api change

Finished removing the metrics registry

Updated based on code review

Readded cloud foundry keys to observations

Renamed metrics to observations where applicable

Updated metric sample to be observation sample

Updated to set defaults and migrate tests to infrastructure

Updated based on code review

Remove duplicate keyvalues from task observation

Added DocumentedObservation to create the observation
Migrated code to use the LowerCardinality KeyNames from the DocumentedObservation
Test cleanup
Updated code based on code review

Exception is handled by the error in the observation vs logging it as a task metric key value

Updated to use ObservationConvention

Updated to handle user defined convention vs default

Removed the snapshot versions of observations

Removed unnecessary dependencies

Checkpoint tests fail after re-adding 1.10-SNAPSHOT

Replaced TimeObservationHandler with DefaultMeterObservationHandler

Updated to set micrometer to latest milestone

Updated to rename TaskValuesProvider variables to ObservationConvention
2022-07-22 17:24:08 -04:00
2022-01-14 13:31:35 -05:00
2022-01-21 14:09:19 -05:00
2019-03-20 16:10:18 -05:00
2019-02-03 19:27:07 +01:00
2019-03-20 16:10:18 -05:00
2019-03-21 16:34:26 -04:00
2019-03-11 12:48:37 -05:00
2019-03-11 12:48:37 -05:00

////
DO NOT EDIT THIS FILE. IT WAS GENERATED.
Manual changes to this file will be lost when it is generated again.
Edit the files in the src/main/asciidoc/ directory instead.
////


= Spring Cloud Task

Is a project centered around the idea of processing on demand.  A user is able to develop
a “task” that can be deployed, executed and removed on demand, yet the result of the
process persists beyond the life of the task for future reporting.


== Requirements:

* Java 17 or Above

== Build Main Project:

[source,shell,indent=2]
----
$ ./mvnw clean install
----

== Example:

[source,java,indent=2]
----
@SpringBootApplication
@EnableTask
public class MyApp {

    @Bean
    public MyTaskApplication myTask() {
        return new MyTaskApplication();
    }

    public static void main(String[] args) {
        SpringApplication.run(MyApp.class);
    }

    public static class MyTaskApplication implements ApplicationRunner {

        @Override
        public void run(ApplicationArguments args) throws Exception {
            System.out.println("Hello World");
        }
    }
}
----

== Code of Conduct
This project adheres to the Contributor Covenant link:CODE_OF_CONDUCT.adoc[code of conduct]. By participating, you  are expected to uphold this code. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.

== Building the Project

This project requires that you invoke the Javadoc engine from the Maven command line. You can do so by appending `javadoc:aggregate` to the rest of your Maven command.
For example, to build the entire project, you could use `mvn clean install -DskipTests -P docs`.
Description
No description provided
Readme Apache-2.0 6.6 MiB
Languages
Java 92.4%
XSLT 6.4%
CSS 1.1%