-
Notifications
You must be signed in to change notification settings - Fork 174
Invalid interval specified, must be non-null and non-empty #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Getting the same issue. |
Just starting out here. I am getting the same issue. |
Reading an old thread I found #41 (comment). |
Hey thanks. But right now my whole install seems hosed, some pkgs changed like the keyring no longer using apt-get and when I tried to reload my files, not all of them seem to get processed. I am attempting to rebuild this on my FreeBSD system which is much more stable than WSL under win10. |
Hi |
Interesting, how do you import the dashboard? Also, got everything rebuilt but parsedmarc can't open up a connection to ES even after changing to localhost:9200 |
Same issue, and akky's patch does not solve it... |
@MeNearly I had the same issue, it's because the last version of the dashboard only works for newer versions of elasticsearch (^8.0.0). I used and old version of the dashboard and it worked fine.(https://github.com/domainaware/parsedmarc/blob/bddc2adb9cd7dad408049e7032e85ef9c9470e48/grafana/Grafana-DMARC_Reports.json) |
ran into the same issue, deleted the dashboard and imported this one using the id 11227 to edit you may need to log into grafana first, the default account is user: admin, password: admin. It will let you set your own password after first log in |
Easiest fix for me, was to login as admin, select the title of each panel, then click edit. In the query settings at the bottom you should see the row that starts with "Then By", where it says "Interval:auto" select that option and click "auto". Clicking "auto" (even though that's what it was already set to) must reset it to what it's expecting, then each graph works as expected. Should be noted that I also followed the recommendation of @teradiot and updated my grafana to 10.2.3 |
@jeppebundsgaard did @akky submit a pull request for it? that's how commits can be accepted— |
I guess not. |
The text was updated successfully, but these errors were encountered: