serve.py can only work as part of the ddev meta scripts serve-openmetrics-payload command.
After
You can call serve.py directly to serve openmetrics payloads.
Motivation
Some integrations, for instance vllm don't work with the serve-openmetrics-payload command. They require more than just the OM HTTP endpoint, they scrape some endpoints for metadata.
I found that I needed to hack something together for that case:
invoke serve.py directly to serve the OM payloads
modify the vllm source to skip crawling the metadata endpoint
run ddev env start vllm... and point the agent to the server exposed by serve.py
Review checklist (to be filled by reviewers)
[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged
What does this PR do?
Before
serve.py
can only work as part of theddev meta scripts serve-openmetrics-payload
command.After
You can call
serve.py
directly to serve openmetrics payloads.Motivation
Some integrations, for instance
vllm
don't work with theserve-openmetrics-payload
command. They require more than just the OM HTTP endpoint, they scrape some endpoints for metadata.I found that I needed to hack something together for that case:
serve.py
directly to serve the OM payloadsvllm
source to skip crawling the metadata endpointddev env start vllm...
and point the agent to the server exposed byserve.py
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged