Skip to content

How should Agent pools exposed and stats be integrated into e.g. Prometheus #4149

@tdeekens

Description

@tdeekens

Thanks for undici, it's a great library and a joy to use!

I am planning on writing a Prometheus exporter in a library of mine. For that I see that a Pool as stats which could be used for that. As a result my plan was to integrate pools on a per origin bases into the metrics.

In this context I stumbled across some questions I'd greatly appreciate guidance with.

  1. An Agent instances pools if the desired connections are more than 1. However, an Agent does not expose the pools used publicly.
  2. One could build a custom Agent or Pool registry but I wonder if that the desired path.

Is there maybe an API or possible integration I overlook? The goal would be that an external system such as a Prometheus exporter gets access to the used pools. I would want to avoid an application having to build its own pool per origin as this makes testing harder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions