TIBCOSoftware / TIBCOSoftware/bw-tooling
Prometheus Integration fails when Linkerd is enabled
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
When service mesh (Linkerd) is used, Prometheus fails to get the metrics from Pod while giving EOF error.
No logs are printed in application or prometheus pod.
Following log is found in linkerd-proxy sidecar container -
hyper::proto::h1::role unexpected content-length found, canceling
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Prometheus scrape failure with Linkerd enabled, then inspect the Prometheus and Linkerd proxy logs around the EOF and unexpected content-length errors. Done means Prometheus can retrieve the pod metrics successfully without the EOF failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- networking, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100