Skip to content

Commit

Permalink
Updates after rebasing on main (merged changes of Metrics)
Browse files Browse the repository at this point in the history
  • Loading branch information
tomas-langer committed Jul 31, 2024
1 parent 1d39ab6 commit b9021f9
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 8 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -52,20 +52,28 @@ Application tag value
Application tag name
|`enabled` |boolean |`true` |Whether metrics functionality is enabled.
If metrics are configured to be enabled
If metrics are configured to be enabled
|[.line-through]#`gc-time-type`# |GcTimeType (GAUGE, COUNTER) |`GcTimeType.COUNTER` |*Deprecated* Whether the `gc.time` meter should be registered as a gauge (vs. a counter).
The `gc.time` meter is inspired by the MicroProfile Metrics spec, in which the meter was originally checked to
be a counter but starting in 5.1 was checked be a gauge. For the duration of Helidon 4.x users can choose which
type of meter Helidon registers for `gc.time`.
The type of meter to use for registering `gc.time`
@deprecated Provided for backward compatibility only; no replacement
The `gc.time` meter is inspired by the MicroProfile Metrics spec, in which the meter was originally checked to
be a counter but starting in 5.1 was checked be a gauge. For the duration of Helidon 4.x users can choose which
type of meter Helidon registers for `gc.time`.
The type of meter to use for registering `gc.time`
@deprecated Provided for backward compatibility only; no replacement
Allowed values:
- `GAUGE`: Implement the meter as a gauge. This is backward-incompatible with Helidon 4.0.x releases but complies with
MicroProfile 5.1.
- `COUNTER`: Implement the meter as a counter. This is backward-compatible with Helidon 4.0.x releases but does not comply with
MicroProfile 5.1.
|`key-performance-indicators` |xref:{rootdir}/config/io_helidon_metrics_api_KeyPerformanceIndicatorMetricsConfig.adoc[KeyPerformanceIndicatorMetricsConfig] |{nbsp} |Key performance indicator metrics settings.
Key performance indicator metrics settings
|`permit-all` |boolean |`true` |Whether to allow anybody to access the endpoint.
Whether to permit access to metrics endpoint to anybody, defaults to `true`
See roles()
Whether to permit access to metrics endpoint to anybody, defaults to `true`
See roles()
|`rest-request-enabled` |boolean |`false` |Whether automatic REST request metrics should be measured.
True/false
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,20 @@ Application tag name
If metrics are configured to be enabled
|`endpoint` |string |`metrics` |
|[.line-through]#`gc-time-type`# |GcTimeType (GAUGE, COUNTER) |`GcTimeType.COUNTER` |*Deprecated* Whether the `gc.time` meter should be registered as a gauge (vs. a counter).
The `gc.time` meter is inspired by the MicroProfile Metrics spec, in which the meter was originally checked to
be a counter but starting in 5.1 was checked be a gauge. For the duration of Helidon 4.x users can choose which
type of meter Helidon registers for `gc.time`.
The type of meter to use for registering `gc.time`
@deprecated Provided for backward compatibility only; no replacement
Allowed values:
- `GAUGE`: Implement the meter as a gauge. This is backward-incompatible with Helidon 4.0.x releases but complies with
MicroProfile 5.1.
- `COUNTER`: Implement the meter as a counter. This is backward-compatible with Helidon 4.0.x releases but does not comply with
MicroProfile 5.1.
|`key-performance-indicators` |xref:{rootdir}/config/io_helidon_metrics_api_KeyPerformanceIndicatorMetricsConfig.adoc[KeyPerformanceIndicatorMetricsConfig] |{nbsp} |Key performance indicator metrics settings.
Key performance indicator metrics settings
Expand Down

0 comments on commit b9021f9

Please sign in to comment.