• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

• Ensure Prometheus /metrics endpoint streams correctly with clean EOF

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary): Tested locally with docker-compose and within a Kubernetes cluster which included a service monitor which was able to scrape the metrics into Prometheus.
  As you can see from the evidence attached, this now works locally and returns the format expected by Prometheus.

curl -I http://localhost:8080/metricsHTTP/1.1 200 OKtransfer-encoding: chunkedAccess-Control-Allow-Credentials: trueAccess-Control-Allow-Methods: GET, PUT, POST, DELETE, OPTIONSAccess-Control-Max-Age: 3600Access-Control-Allow-Headers: Content-TypeContent-Type: text/plain; version=0.0.4

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g.ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check outContributing andCode of Conduct

A picture of a cute animal (not mandatory but encouraged)