influxdata / influxdata/influxdb
Prometheus can't read "cursor"
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
I'm in Prometheus Remotewrite and remotewrite are correctly configured in yaml, and I also saw Prometheus write data to informdb using show measurements in informdb. This does not seem to be a problem, but I manually create a table such as http_ reqeust_total and constantly customize some data into it. Then I query http_reqesut_total through Prometheus graph, but I can't find it.
And when i query on prometheus, I saw influxdb logs:
ts=2022-08-17T08:12:37.586827Z lvl=info msg="Prometheus can't read cursor" log_id=0cLRYF6l000 service=httpd cursor_type=int64 series="[{__name__ traefik_reqesut_total} {code 200}]"
[httpd] 172.30.24.208 - - [17/Aug/2022:08:12:37 +0000] "POST /api/v1/prom/read?db=grafana&rp=autogen HTTP/1.1 " 200 4 "-" "Prometheus/2.36.2" 5b1fa5a6-1e04-11ed-9f5f-066c3e672749 1299
what is the problem?
Contributor guide
Research direction
Start by reproducing the Prometheus query against the manually created measurement and inspect the InfluxDB /api/v1/prom/read entry point, using the reported “Prometheus can't read cursor” log as the initial clue. Determine why the measurement is not returned and whether the behavior is expected; done means the cause and a verified correction or clear compatibility requirement are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- backend-api-design, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100