Beta CCM bug

[TenTimes]

I just found a bug in the new CCM.

When I search for the services which are all on the same host by the hostname, I get a list which is more than 15 records long. When I go to the next page, my search has gone and I get all the service on the Nagios server. I loved the function in the old CCM where you could filter the services and it stayed that way even if you went to a different page and returned later in the same session. Could you please bring this back, because it is really easy when you are trying to get the right syntax for a service check.

I also came accross a problem when I tried to add a switch monitoring by the wizard. I had completed adding all the switchports and found out I had not all the contacts. I tried to add the contact first, but it gave a error when applying the changes. So I removed the contact and then wanted to apply the config wizard. This was also unsuccesfulll, but when I wanted to add the switch, found out the switch was already there, even though it gave an error when I applied the changes in the latest step of the wizard. This is really strange, but it could be my work process. Can it be that the half completed wizard was in the part of the database, which the new CCM tried to apply?

FYI: When I added the contact later, everything went fine.

[mguthrie]

I've got item #1 added to the bug list, you are correct in that the search value should persist until cleared manually.

For the second item you mentioned, I'm betting the issue had to do with this bug I found since posting the public beta:

- Service 'Notification options' get written to DB without commas, apply config will fail

If you go back and look at your bad configuration snapshots, you'll be able to view what the configuration error was, I'm guessing you got an error about the notification options.

[TenTimes]

You were right about the notification error. The user I made didn't work because there were no notification option defined. A copy of my own user account and an edit to the correct values was the way to fix this.

Thanks for the advice and I'll look forward to the RC version of the CCM. Even though it is in a beta fase, it still was enormously helpfull.

[mguthrie]

These items should be fixed in the 0.4 version of the CCM Beta. : )