Hi DaPeng, Griffin reads your data, execute the rule steps on the data, then persist the metrics. If there's any exception like data can not find or execution error, the rule step might fail, and the following steps will not success either, the metrics is collected after the last step, thus there might be no metrics in such a situation. All the exceptions will be logged in the application log, you can find some information there. I cannot see your attachment, I'm not sure what kind of job are you running, what's the data like, is it accessible in every minute?
Thanks, Lionel On Mon, Jan 14, 2019 at 11:06 AM 大鹏 <18210146...@163.com> wrote: > > What is the strategy of ES to save metric?My task was executed every five > minutes, and part of the metric generated in the process of execution was > lost, which did not match the number of task execution. For this problem, > please see the red part in the attachment. > > >
