-
Notifications
You must be signed in to change notification settings - Fork 81
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
[WFLY-18582] Add prometheus endpoint to micrometer extension #551
base: main
Are you sure you want to change the base?
Conversation
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Show resolved
Hide resolved
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Show resolved
Hide resolved
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Show resolved
Hide resolved
9430c02
to
b824555
Compare
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
0545d2b
to
d4ad021
Compare
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
b88c561
to
a62b1be
Compare
da4e03e
to
dd95960
Compare
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
dd95960
to
c36ef0c
Compare
*** `context`: the context (e.g., `/prometheus`) on which the metrics will be exposed | ||
*** `security-enabled`: whether to secure the context using the user and roles defined in the application server | ||
** If the user would like to use `/metrics`, the WildFly metrics extension must be disabled first to avoid a naming conflict. | ||
* Micrometer, using its OTLP-based push approach, should continue to work in manage domain mode, but if Prometheus is configured to be used on the host controller, the startup attempt of the HC should fail. |
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 needs clarification.
I believe the situation is that an attempt to add the new resource in a domain mode profile will be rejected, during execution of the resource's add operation. (That would be the correct behavior -- reject the attempt to add an illegal config as soon as it happens, which is when the user tries to add it to the domain profile.)
From there I don't think it's necessary to explain what will happen as a consequence of the add op failing as that is just standard WF behavior that applies to any resource add. If the add op happens during boot, boot fails, otherwise the DC reports the failure to the management client (CLI/HAL) that attempted the add.
I think there should be a requirement about noting this in the text description of relevant add op (i.e. the text in LocalDescriptions.properties)
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.
@bstansberry Text updated. If you're happy with the update, please resolve this conversation. thx.
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
observability/WFLY-18582_add-prometheus-endpoint-to-micrometer-extension.adoc
Outdated
Show resolved
Hide resolved
Add analysis document Update to new AD format
c36ef0c
to
5ea03f6
Compare
https://issues.redhat.com/browse/WFLY-18582
Add analysis document
Resolves #590