You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2025. It is now read-only.
We would like to run queries with different execution times. For example, the query that checks table space fullness doesn’t need to run frequently. However, queries checks lock or app session info needs to run more frequently. I don’t see a way of running queries with different execution intervals. It seems all queries are running with the same execution intervals.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Some queries do not need to run as frequently as others.
Please tell us about your environment:
We are using the latest Oracle Prometheus on Oracle 19c
Version: X.Y.Z
The text was updated successfully, but these errors were encountered:
I had the same issue and as a workaround I'm adding time constraints to some queries, like:
"and (to_char(sysdate,'HH24')=10 and to_char(sysdate,'MI')<20)"
Depending on your needs this could be doable this way.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm submitting a ...
What is the current behavior?
We would like to run queries with different execution times. For example, the query that checks table space fullness doesn’t need to run frequently. However, queries checks lock or app session info needs to run more frequently. I don’t see a way of running queries with different execution intervals. It seems all queries are running with the same execution intervals.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Some queries do not need to run as frequently as others.
Please tell us about your environment:
We are using the latest Oracle Prometheus on Oracle 19c
Version: X.Y.Z
The text was updated successfully, but these errors were encountered: