Exception in seyren logs for null data points. #430
Comments
|
It looks like Seyren is unable to find the metric in your Graphite tree named "REQUEST_FAILED". Double check that you are entering the complete metric name in the "Target" field on the Check in the Seyren GUI. Perhaps share with us a screenshot of your Seyren Check and an example Graph from the Graphite web application so we can see what you're working with? Cheers! |
|
And target for seyren : alias(sumSeries(derivative(prod...*.REQUEST_FAILED.count)),'REQUEST_FAILED') |
|
If your'e not seeing any data points in the Graph in Graphite, it could mean a few things.
You can try applying the function Basically though, you need to make sure that you have a graph that displays properly in Graphite web so that you can convert it to a Seyren check, otherwise exceptions like you posted will be what you get. |
|
My storage schemas : [metric_1min_for_3m] How can I check that metric is actually arriving in graphite? Also I am getting some other exceptions as well, after I deleted the checks which were in unknown state in seyren alert dashboard. Please find the stack trace: |
|
I'm not sure about that 2nd exception. As for checking if the metrics are arriving... you can look at |
|
I have checked in the location and only m1_rate.wsp is present. There is no count.wsp file. But graphs are visible in Grafana. So how can it be possible. Also after deleting those alerts, this problem must have resolved, right? But I am not getting alerts for other metrics as well even after WARN level has reached. Also, until count.wsp of the metric gets created, I should not create an alert to avoid this Exception? Or is there any way, to stop these alerts from pushing to seyren, instead of deleting those checks and once again creating them. |
Following are the logs formed:
Can anyone suggest how to resolve this?
I have used Meter.mark(); to push to graphite
[seyren.check-scheduler-2] WARN c.s.c.service.schedule.CheckRunner - No value present for Fail
09/02/2017 16:44:53.516 [seyren.check-scheduler-0] WARN c.s.c.s.c.GraphiteTargetChecker - {"target":"REQUEST_FAILED","datapoints":[[null,1486638240],[null,1486638300],[null,1486638360],[null,1486638420],[null,1486638480],[null,1486638540],[null,1486638600],[null,1486638660],[null,1486638720],[null,1486638780]]}
[seyren.check-scheduler-0] WARN c.s.c.s.c.GraphiteTargetChecker - REQUEST FAILURE failed to read from Graphite
com.seyren.core.exception.InvalidGraphiteValueException: Could not find a valid datapoint for target: "REQUEST_FAILED"
at com.seyren.core.service.checker.GraphiteTargetChecker.getLatestValue(GraphiteTargetChecker.java:83) ~[seyren-core-1.0.1-SNAPSHOT.jar:na]
at com.seyren.core.service.checker.GraphiteTargetChecker.check(GraphiteTargetChecker.java:54) ~[seyren-core-1.0.1-SNAPSHOT.jar:na]
at com.seyren.core.service.schedule.CheckRunner.run(CheckRunner.java:65) ~[seyren-core-1.0.1-SNAPSHOT.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ~[na:1.6.0_30]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) ~[na:1.6.0_30]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) ~[na:1.6.0_30]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) ~[na:1.6.0_30]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) ~[na:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) ~[na:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) ~[na:1.6.0_30]
at java.lang.Thread.run(Thread.java:701) ~[na:1.6.0_30]
[seyren.check-scheduler-0] WARN c.s.c.service.schedule.CheckRunner - No value present for REQUEST_FAILED
The text was updated successfully, but these errors were encountered: