Skip to content
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

Director import: Using custom_values as "All custom variables" does not work #534

Open
dgoetz opened this issue Sep 26, 2023 · 0 comments
Open

Comments

@dgoetz
Copy link
Contributor

dgoetz commented Sep 26, 2023

Expected Behavior

custom_values can be used by internal customers to add additional information as they need it and the monitoring administrators are not required to adjust the sync rules every time as custom_values are useable as "All custom variables".

Current Behavior

Trying to use it results in removal of all custom variables, probably because if it not being recognized as structured data like expected. Trying to use a modifier of json decode results always in custom_values being set to null, not honouring the on_failure setting.
Trying a similar thing with json data from a database and using the modifier works like expected.

Steps to Reproduce (for bugs)

Add custom attributes in vCenter, import virtual machines, try to sync the custom_values as "All custom variables".

Your Environment

  • VMware vCenter®/ESXi™-Version: 7.2
  • Version/GIT-Hash of this module: 1.7.1
  • Icinga Web 2 version: 2.11.4
  • Operating System and version: CentOS 7.9
  • Webserver, PHP versions: Apache with PHP 7.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant