Command-Line Tips and Tricks.
It would result in one time series per order where the value is set to 1 and will never increase. Not sure if I have to wait longer or something, but I was hoping to get back the same functionality that existed pre-2.0 for cleaning up old jobs where a single run of a script could clean up everything quickly. share. I've done the below several times testing it out, and while it does appear to clean up the data, the old job label is not removed even if no data exists for it.
ru; ShellHacks . Would be really nice if you could remove labels in the result without aggregation, like you do in an SQL statement like "SELECT (field1, field2) FROM mydb WHERE blah blah blah" On Thursday, January 3, 2019 at 8:58:25 AM UTC-5, Tim Epkes wrote: Actually that could work. Firstly you need to find which metric is the problem. Thankfully there's a way to deal with this without having to turn off monitoring or deploy a new version of your code. What I looking for is if there some sort of config we can do per Prometheus environment to say “do not remove these labels” when sending the alert, allowing me to keep the rules generic and use it across other environments/setups without confusing people on labels which might never exist in that setup. How to delete metrics that match some label, job, instance, etc. That could be fine, but sometimes you'd like a more meaningful value on your graphs and dashboards. Sometimes you may want to delete some metrics from Prometheus if those metrics are unwanted or … Prometheus groups are a collection of rules.
save hide report. Blog; Prometheus: Delete Time Series Metrics. It may be a DNS name but commonly it's just a host and port such as 10.3.5.2:9100 .
Seems to be giving a similar result with some grafana mods. 0 comments.
On the other hand, the Kubernetes/Prometheus combination is quite a prominent poster child and what IMO the future will look like more and more. In the extreme this can overload your Prometheus server, such as if you create a time series for each of hundreds of thousands of users. Often, enumerations within our domain model are … Toggle navigation. Any advice would be great, thanks.
Removing "job" as a magical label does get closer to letting people stick to local policies.
Before we continue, there's some prometheus terminology I just want to clarify. Posted on Wednesday September 12th, 2018 by admin. Due to the fact that Prometheus creates separate time series for each combination of label values, only labels with a small number of possible values should be used. and how to remove all data from Prometheus time series database. In Prometheus the instance label uniquely identifies a target within a job.