why do these logs occur? - failed to make http request
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- observability-sre
Research direction
Start with the otel-collector logs for the bigip/1 metrics scrape and the reported BIG-IP request URL, focusing on the context deadline exceeded error. Reproduce against the configuration with about 8,000 servers if available; done means documenting the cause and a verified remediation or configuration change.
Written by the indexing model from the issue text.
Description
Why do these logs occur?
I think it occurs because the number of objects increases and the content increases.
I am currently using a dns license and have about 8,000 servers registered.
- otel-collector logs
025-04-02T02:19:08.055Z error [email protected]/obs_metrics.go:61 Error scraping metrics {"kind": "receiver", "name": "bigip/1", "data_type": "metrics", "error": "failed to make http request: Get "https://192.168.49.201/mgmt/tm/gtm/server?%24skip=20000&%24top=10000&ver=17.1.2.1\": context deadline exceeded"}
go.opentelemetry.io/collector/scraper/scraperhelper.wrapObsMetrics.func1
go.opentelemetry.io/collector/scraper/[email protected]/obs_metrics.go:61
go.opentelemetry.io/collector/scraper.ScrapeMetricsFunc.ScrapeMetrics
go.opentelemetry.io/collector/[email protected]/metrics.go:24
go.opentelemetry.io/collector/scraper/scraperhelper.scrapeMetrics
go.opentelemetry.io/collector/scraper/[email protected]/controller.go:256
go.opentelemetry.io/collector/scraper/scraperhelper.NewMetricsController.func1
go.opentelemetry.io/collector/scraper/[email protected]/controller.go:228
go.opentelemetry.io/collector/scraper/scraperhelper.(*controller[...]).startScraping.func1
go.opentelemetry.io/collector/scraper/[email protected]/controller.go:171
- Dominant language
- Python
- Stars
- 106
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from f5devcentral/application-study-tool
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
f5devcentral/application-study-tool#267 · 7 comments ·
All issues in f5devcentral/application-study-tool
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
modelcontextprotocol/python-sdk#3648 ·
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
VenetoStato/giorgio#6 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
EclipseFdn/open-vsx.org#13831 ·
Maintainers usually reply within 1 day
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days