For 1) and 2), alerting based on metrics and profiling graphs, Grafana
works pretty good on my experience.
Problem in 4) can be solved in several ways:
- "predicates": it is possible to configure data source with predicate
logic, which will be checked before job gets started. However there are
I think, if there is clear use case, it makes sense to document that in
Jira.
For 1), it sounds like it requires some "state" to be preserved between job
runs, something which is not available directly. This theoretically can be
done with elasticsearch input reading latest previous result of the
[
https://issues.apache.org/jira/browse/GRIFFIN-237?focusedWorklogId=210621=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-210621
]
ASF GitHub Bot logged work on GRIFFIN-237:
--
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/GRIFFIN-229?focusedWorklogId=210623=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-210623
]
ASF GitHub Bot logged work on GRIFFIN-229:
--
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/GRIFFIN-237?focusedWorklogId=210616=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-210616
]
ASF GitHub Bot logged work on GRIFFIN-237:
--
Author: ASF GitHub Bot
