-
Notifications
You must be signed in to change notification settings - Fork 695
Metrics Improvements #529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metrics Improvements #529
Conversation
@@ -70,8 +70,8 @@ conductor.default-event-queue.type=sqs | |||
# conductor.zookeeper-lock.namespace | |||
|
|||
#disable locking during workflow execution | |||
conductor.app.workflow-execution-lock-enabled=false | |||
conductor.workflow-execution-lock.type=noop_lock |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this change feels out of place w.r.t metrics changes.
Why do we need to change these flags ?
Same comment for server-lite/src/main/resources/application.properties
@@ -74,6 +75,8 @@ public void setupKitchenSink() { | |||
LOGGER.info("Loading Kitchen Sink examples"); | |||
createKitchenSink(); | |||
} | |||
} catch (ConflictException ignored) { | |||
// Already present in the system :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this for debugging ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes and if there is a conflict it means the workflow already exists, so its OK to ignore.
|
||
@Bean | ||
public MeterRegistry getCloudWatchMetrics( | ||
@Value("${management.cloudwatch.metrics.export.namesapce:conductor}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo?
namesapce or namespace
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
|
||
@Bean | ||
public MeterRegistry getAzureMonitorMeterRegistry( | ||
@Value("${management.cloudwatch.metrics.export.instrumentationKey:null}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cloudwatch or azuremonitor ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
Pull Request type
NOTE: Please remember to run
./gradlew spotlessApply
to fix any format violations.Changes in this PR
Upgrade metrics system to use the micrometer.
Conductor now supports publishing metrics to all the popular metrics systems.
See https://docs.micrometer.io/micrometer/reference/implementations.html for more details
Describe the new behavior from this PR, and why it's needed
Issue #
Alternatives considered
Describe alternative implementation you have considered