You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature aims to enhance the customization options for Prometheus request handling by introducing the PrometheusRequestHandler. This handler provides users with the ability to define their own request handling strategies tailored to their application's needs, enabling greater flexibility and control over how Prometheus metrics are scraped and served.
Proposal:
The proposal involves adding support for customizing Prometheus request handling through the introduction of the PrometheusRequestHandler. This handler can be configured to scrape metrics from a PrometheusMeterRegistry and serve them over HTTP, offering various configuration options for metrics endpoints and the Prometheus registry.
Use cases
Enhanced Flexibility: Users can define custom request handling procedures tailored to their application's unique requirements by customizing registry.
Adaptability: By allowing users to define their own request handling logic, the feature promotes adaptability to diverse project environments and use cases.
Implementation Details
The implementation involves:
Introducing the PrometheusRequestHandler interface with factory methods for creating handlers.
Providing configuration options for specifying PrometheusMeterRegistry and metrics endpoints.
Implementing the PrometheusRequestHandlerImpl class to handle HTTP requests for Prometheus metrics scraping.
PrometheusMeterRegistry customRegistry = new PrometheusMeterRegistry(PrometheusConfig.DEFAULT); customRegistry.config().namingConvention(NamingConvention.camelCase); router.route("/custom-metrics").handler(ctx -> PrometheusRequestHandler.create(customRegistry,"/custom-metrics") .handle(ctx.request()));
This feature enhancement will enrich the Prometheus integration in Vert.x, offering users greater flexibility and control over how metrics are handled and served.
Contribution
Who should implement this feature ? are you volunteering for implementing this feature - YES
The text was updated successfully, but these errors were encountered:
swamymavuri
changed the title
Add support for custom exception handler for VertxPrometheusOptions
Add support for customizing Prometheus request for metrics scraping by introducing PrometheusRequestHandler
May 25, 2024
swamymavuri
added a commit
to swamymavuri/vertx-micrometer-metrics
that referenced
this issue
May 25, 2024
Describe the feature
This feature aims to enhance the customization options for Prometheus request handling by introducing the PrometheusRequestHandler. This handler provides users with the ability to define their own request handling strategies tailored to their application's needs, enabling greater flexibility and control over how Prometheus metrics are scraped and served.
Proposal:
The proposal involves adding support for customizing Prometheus request handling through the introduction of the PrometheusRequestHandler. This handler can be configured to scrape metrics from a PrometheusMeterRegistry and serve them over HTTP, offering various configuration options for metrics endpoints and the Prometheus registry.
Use cases
Enhanced Flexibility: Users can define custom request handling procedures tailored to their application's unique requirements by customizing registry.
Adaptability: By allowing users to define their own request handling logic, the feature promotes adaptability to diverse project environments and use cases.
Implementation Details
The implementation involves:
PrometheusMeterRegistry customRegistry = new PrometheusMeterRegistry(PrometheusConfig.DEFAULT); customRegistry.config().namingConvention(NamingConvention.camelCase); router.route("/custom-metrics").handler(ctx -> PrometheusRequestHandler.create(customRegistry,"/custom-metrics") .handle(ctx.request()));
This feature enhancement will enrich the Prometheus integration in Vert.x, offering users greater flexibility and control over how metrics are handled and served.
Contribution
Who should implement this feature ? are you volunteering for implementing this feature - YES
The text was updated successfully, but these errors were encountered: