Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grafana shows metrics value after removal in victoria metrics #6300

Open
1 of 3 tasks
tonus01 opened this issue May 18, 2024 · 3 comments
Open
1 of 3 tasks

Grafana shows metrics value after removal in victoria metrics #6300

tonus01 opened this issue May 18, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@tonus01
Copy link

tonus01 commented May 18, 2024

Is your question request related to a specific component?

VictroiaMetrics with grafana

Describe the question in detail

Hi. I use victoria metrics with promethues scrape config. After I changed job name(from servs to hosts) grafana started showing 2 jobs(old and new).
jobs
Then I deleted the time series for the servs job.
http://victoria-metrics:8428/api/v1/admin/tsdb/delete_series?match[]={job="servs"}
And victoria metrics explorer return me only 1 job(hosts). But grafana still return 2 jobs(hosts and servs). Why does grafana return something that doesn't exist?

Troubleshooting docs

@tonus01 tonus01 added the question The question issue label May 18, 2024
@tonus01 tonus01 changed the title Grafana shows metrics value after removal in victroia metrics Grafana shows metrics value after removal in victoria metrics May 18, 2024
@tonus01
Copy link
Author

tonus01 commented May 19, 2024

This issue is rise when i choose prometheus version >= 2.24.x When i choose 2.23.x my grafana work fine and not show removed time series.

@hagen1778
Copy link
Collaborator

Why does grafana return something that doesn't exist?

It is likely Grafana caches the previous response. Will it show the old job value if you create a new datasource with identical settings?

@hagen1778 hagen1778 self-assigned this May 20, 2024
@tonus01
Copy link
Author

tonus01 commented May 20, 2024

Why does grafana return something that doesn't exist?

It is likely Grafana caches the previous response. Will it show the old job value if you create a new datasource with identical settings?

Yes, grafana show old job if i create new datasource with identical settings. And i use cache level: none for datasource to avoid cache influence. I try last releases grafana(10.4.{1-3} and 11.0.0) and this problem is everywhere. I use vm single install(try v1.101.0, v1.100.1,v1.93.14) Can you ask QA team to check this? And I repeat, everything works correctly if i select prometheus verison 2.23.X or less in datasource settings.

@hagen1778 hagen1778 added bug Something isn't working and removed question The question issue labels May 23, 2024
hagen1778 added a commit that referenced this issue May 24, 2024
…ls` and `/api/v1/label/.../values`

Check for deleted metrics when `match[]` filter matches small number of time series (optimized path).

The issue was introduced [v1.81.0](https://docs.victoriametrics.com/changelog_2022/#v1810).

Related issue #6300
Updates #2978

Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778 added a commit that referenced this issue May 29, 2024
#6342)

…ls` and `/api/v1/label/.../values`

Check for deleted metrics when `match[]` filter matches small number of
time series (optimized path).

The issue was introduced
[v1.81.0](https://docs.victoriametrics.com/changelog_2022/#v1810).

Related issue
#6300 Updates
#2978

Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778 added a commit that referenced this issue May 29, 2024
#6342)

…ls` and `/api/v1/label/.../values`

Check for deleted metrics when `match[]` filter matches small number of
time series (optimized path).

The issue was introduced
[v1.81.0](https://docs.victoriametrics.com/changelog_2022/#v1810).

Related issue
#6300 Updates
#2978

Signed-off-by: hagen1778 <roman@victoriametrics.com>

(cherry picked from commit b984f46)
Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778 added a commit that referenced this issue May 29, 2024
#6342)

…ls` and `/api/v1/label/.../values`

Check for deleted metrics when `match[]` filter matches small number of
time series (optimized path).

The issue was introduced
[v1.81.0](https://docs.victoriametrics.com/changelog_2022/#v1810).

Related issue
#6300 Updates
#2978

Signed-off-by: hagen1778 <roman@victoriametrics.com>

(cherry picked from commit b984f46)
Signed-off-by: hagen1778 <roman@victoriametrics.com>
hagen1778 added a commit that referenced this issue May 29, 2024
#6342)

…ls` and `/api/v1/label/.../values`

Check for deleted metrics when `match[]` filter matches small number of
time series (optimized path).

The issue was introduced
[v1.81.0](https://docs.victoriametrics.com/changelog_2022/#v1810).

Related issue
#6300 Updates
#2978

Signed-off-by: hagen1778 <roman@victoriametrics.com>

(cherry picked from commit b984f46)
Signed-off-by: hagen1778 <roman@victoriametrics.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants