Error scraping metrics does not provide context to which device was having issues

Open
#191 6 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
observability-sre

Research direction

Search the collector code for the “Error scraping metrics” message and trace how the device being scraped is represented at that point. Reproduce or inspect a scraping failure, then verify the emitted error identifies the affected device alongside the existing error details.

Written by the indexing model from the issue text.

Description

enhancement

I have a number of errors being generated from the custom otel collector that look similar to the following:

Error scraping metrics  {"error": "endpoint /mgmt/tm/ltm/profile/http3 returned code 400; endpoint /mgmt/tm/ltm/profile/quic returned code 400; failed to decode response payload: json: cannot unmarshal array into Go struct field ClientSSLProfiles.items.tmOptions of type string"}

This gives no context as to which device this collector is having issues scraping.

Please update the error to include information about the device this collector is having issues scraping.

Dominant language
Python
Stars
106
Forks
43
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from f5devcentral/application-study-tool

All issues in f5devcentral/application-study-tool

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.