prometheus-community / prometheus-community/stackdriver_exporter

Retrieving fails with 400 errors from API

Open
#28 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
295
Forks
117
Avg merge
9d 14h
Merged PRs (30d)
7

Description

I'm getting this continuously in the log:

time="2018-05-22T18:37:40Z" level=error msg="Error retrieving Time Series metrics for descriptor `loadbalancing.googleapis.com/https/backend_request_count`: googleapi: Error 400: The provided filter doesn't refer to any known metric., badRequest" source="monitoring_collector.go:176"
time="2018-05-22T18:37:40Z" level=error msg="Error retrieving Time Series metrics for descriptor `loadbalancing.googleapis.com/https/backend_request_bytes_count`: googleapi: Error 400: The provided filter doesn't refer to any known metric., badRequest" source="monitoring_collector.go:176"

Running with the command line:

--monitoring.metrics-type-prefixes loadbalancing.googleapis.com,storage.googleapis.com
--monitoring.metrics-interval 30m
--monitoring.metrics-offset 2m

I'm not sure if it's just a metric that doesn't exist (e.g. an LB without HTTPS?) and that this is ignorable, but it's logged as error.

Version 0.5.1.

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.

Research direction

Start at monitoring_collector.go:176 and reproduce the 400 errors with the listed monitoring metrics flags and version 0.5.1. Check how unknown or unavailable metrics are handled by the Stackdriver API, then verify that the resulting behavior and log severity match the intended treatment of missing metrics.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, google-cloud
Domain
observability-sre
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.