Nagios Support Forum

Currently the Hyper-V monitoring wizard does not support USER macros as mechanism to supply the NCPA token. The NCPA port and token input from the wizard is stored as custom host macros. I dislike the idea that
- ordinary users can see the NCPA token on the 'Free Variables' screen;
- NCPA token is set on a per-host basis.

Could you change this behaviour?

Another issue is that some service checks settings cannot be changed afterwards in Core Config Manager as their (original) names have illegal characters. Example: "Hyper-V Dynamic Memory VM___\Average Pressure".
Can you help me spot what character is the issue here? Regards, Conclusion Xforce

It seems like we overlooked/didn't test the possibility of using USER macros here. Yes, we will change the free variable/macro behavior in the Hyper-V wizard.

As far as the object name issue, that name looks valid to me. However, it's clear that some characters have been replaced (most likely, the original name was "Hyper-V Dynamic Memory VM(*)\Average Pressure"). I wonder if perhaps the original name (with invalid characters) was placed into the database, and if the name is simply displaying as a version with "corrected" characters. Either way, we'll look into this and try to correct it when we make the other changes.

Regards,
Sebastian Wolf

Edit: The object_name issue seems to be coming from some frontend form validation which isn't strictly following the illegal_object_name_chars directive. If you remove the blackslash (change the service description to something like "Hyper-V Dynamic Memory VM___/Average Pressure") you should be able to edit this in the GUI.

Yes, we will change the free variable/macro behavior in the Hyper-V wizard.

Thank you Sebastian!

The object_name issue seems to be coming from some frontend form validation which isn't strictly following the illegal_object_name_chars directive.

Ah, that makes sense. My workaround was using re-configure this service on the home screen.

Thanks a lot for your quick answer.

We're always happy to help! Is it alright if we close this thread?

mbellerue wrote:We're always happy to help! Is it alright if we close this thread?

Sure, you may close this one. Thanks.