Solution to Dashboard issue after 3.2 upgrade

Graylog Central (peer support)
1

Hello,

I saw the following posted about that this, but didn’t appear to be an additional details the post went stale.

Like the last user to comment, I was curious about the what needs to be done to the fix this issue. I would like to keep my dashboard so remove the view documents is not an option. I have been using the Robo3T tool to look at my MongoDB documents. I have been going through the view documents and see some interval values set to the following:

"config" : {
    "interval" : {
        "type" : "auto",
        "scaling" : null
    }
}

What is not clear is what is the “wrong” interval value and what should it be done to fix it. Any information to solve this issue would be useful. Thanks!

1 Like
2

Hi @jamiebuxxx,

I am sorry my previous description was not quite helpful :frowning_face:

I hope I can be clearer now. In your mongo db should be a view which has a time row bucket config like
this:

"config" : {
    "interval" : {
        "type" : "timeunit",
        "timeunit" : null
    }
}

Where time unit can be anything. What it should be is like this:

"config" : {
    "interval" : {
        "type" : "timeunit",
        "scaling" : "1h"
    }
}

I hope this helps. Let me know otherwise, and we try to fix it.

Best regards,
Konrad

3

@konrad Thanks for the update. I did see quite a few of those null values when looking at the views. Should I just remove the null values? I wasn’t able to edit them from Robo3T and I don’t have the most experience with MongoDB outside of the Graylog setup. I think we will need to some more help with this one! :slight_smile:

In the meantime, I had a backup of the MongoDB that was running 3.1 and we just rolled back so users have their dashboards. I have a copy of the MongoDB in question(the 3.2 version), so we can do some testing on that if you have some commands/scripts you would like for us to try.

Thanks!

4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.