suvodeep-pyne commented on a change in pull request #5740:
URL: https://github.com/apache/incubator-pinot/pull/5740#discussion_r459680850



##########
File path: thirdeye/thirdeye-frontend/app/utils/yaml-tools.js
##########
@@ -29,6 +28,20 @@ rules:
     type: DATA_SLA              # Alert if data is missing.
     params:
       sla: 3_DAYS               # Data is missing for 3 days since last 
availability
+
+# You can mention a cron to allow this detection to be run periodically
+# For example, the cron below would execute every 5 minutes.
+# cron: "0 0/5 * 1/1 * ? *"
+
+# Backfill detections
+# You can use the backfillStart parameter to denote how far back you want the 
anomalies
+# to be detected.
+# A valid entry is a timestamp value in millis.
+# 
+# - By default, (if not mentioned), the lookback is 30 days
+# - A value of 0 (zero) implies complete backfill till the start of data. As 
shown below.
+# backfillStart: 0 
+

Review comment:
       Hey @akshayrai 
   
   I understand your point. The problem is that it is very hard for a regular 
user to get started on ThirdEye. These configurations are buried in the doc 
somewhere on a FAQ or you have to go through the code. I didn't know that there 
is a capability to add cron until someone else told me.
   
   I think a YAML interface may be good for advanced users who can have 
configurations saved in files/elsewhere. However for a regular user,  it might 
help to just have a simple UI with text boxes and dropdowns etc which have 
hints/prepopulated and are easy to use without the need for documentation.
   
   I added to the template here so that the user doesn't need to go find 
information elsewhere but is able to see it right within the app. I agree this 
makes the template more complex and that's the reason why I pushed it down at 
the bottom. Let me know what you think and I can revert the template changes.
   
   




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to