GCP Device Network: Error scraping metrics, failed to decode response payload
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, gcp, go
- Domain
- cloud, observability
Research direction
Start by reproducing the failure from the Device Overview dashboard's Device Network panels and inspect the application-study-tool-otel-collector logs. Use the reported scraper error and the entries.NestedStats.Entries.counters.pktsIn.value field as the starting point. Done means Network Addresses, Network Interface Data Rate, and Network Interface Error Rate display data for GCP-hosted BIG-IPs without breaking VLAN Info or other panels.
Written by the indexing model from the issue text.
Description
Describe the bug
Unable to collect network interface information from GCP-hosted F5s, even when service account is set as Administrator. Issue not seen with our other cloud-hosted or on prem systems.
To Reproduce
Dashboard: Device Overview; panel category Device Network; panels Network Addresses, Network Interface Data Rate, and Network Interface Error Rate all show "No data". VLAN Info is populated correctly, as are all other panels in the dashboard.
Expected behavior
Data displayed in panels.
Additional context
COLLECTOR_VERSION: v0.9.2
Issue occurs no matter permission level for service account, including full admin with bash access. Seen on BigIP v17.1.1.3 and after upgrading to v17.5 the issue persists.
Attachments
Error from "docker logs -f application-study-tool-otel-collector-1":
error [email protected]/obs_metrics.go:61 Error scraping metrics {"kind": "receiver", "name": "bigip/gcp1", "data_type": "metrics", "error": "failed to decode response payload: json: cannot unmarshal number 17674376737615511552 into Go struct field .entries.NestedStats.Entries.counters.pktsIn.value of type int64"}
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:175
- 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
-
good first issue hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 92/100
RogueAlg0/taken#387 · 4 comments ·
Maintainers usually reply within 1 day
-
tool-calling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vllm-project/vllm#59838 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
raullenchai/Rapid-MLX#4042 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
transitmatters/mbta-slow-zone-bot#70 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
open-webui/open-webui#31871 · 1 comment ·
Maintainers usually reply within 1 day