recording rules not work

[hashwing]

set a recording rule:

groups
- name: example
    rules:
      - record: query_qps
        expr: irate(http_requests_total{handler="query"}[5m])

query irate(http_requests_total{handler="query"}[5m]) , can find data.

query query_qps , result no data.

[mariobede]

My lack of knowledge might not be identifying this issue properly but.. are you following config example file?

https://github.com/jacksontj/promxy/blob/master/cmd/promxy/config.yaml#L11

[hashwing]

@marioanton Yes, I add it. I can find rule details in web ui. but query 'query_qps', result no data

[mariobede]

isn't that looking for rule files created on prom?

Rule files specifies a list of globs. Rules and alerts are read from all matching files.

Sorry, might be confusing this a bit more.

[hashwing]

I want to know , recording rules config on promxy or prometheus? When I config on promxy, look for rules on promxy web ui, but it can't query in promxy. However, When I config rule on prometheus, it can query in promxy.

[jacksontj]

Thanks for opening an issue! Promxy does load the config for recording rules, and it even actually executes them, but it has no place to store them. Promxy used to actually log the values with a warning saying they aren't stored, but it looks like in the prom 2.x upgrade that was lost. Basically for this to work promxy needs to implement the Appender interface here. Unfortunately prometheus doesn't expose a remote_write endpoint or other API for external services to append points into it.

So, in case you got lost in the wall of text (apologies if its too much detail)-- promxy executes the rules but has no place to put the metrics (prom doesn't have an API to append points into). If its helpful I can implement an option to push that to a remote_write endpoint, but prom doesn't have that-- so you'd need something else to store that. Alternatively, if thats not useful I'll just add back in the warning logs etc. about this behavior.

[jacksontj]

I've pushed in #80 which adds more explicit logging on start/reload about the recordingrule behavior (which should avoid confusion in the fugure). I have also opened up #79 for discussion in the future about what to do about recording rules-- if you have input please let me know :) .

[jacksontj]

As an update here, #90 was merged in which adds support for recording rules through the use of remote_write endpoints.