We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If service name set using apply rules ends with whitespace, BP will mark the node as missing.
Name a service in apply rule with trailing whitespace, e.g. "http " and try to add it as a new node in BP.
The object name will look like this: * __name = "example.com!http "
* __name = "example.com!http "
If applicable, add screenshots to help explain your problem.
Icinga Web 2 Version 2.12.1 PHP Version 8.2.26
icinga/icinga-php-library 0.14.1 icinga/icinga-php-thirdparty 0.12.1
businessprocess 2.5.1 icingadb 1.1.3 cube 1.3.3 director 1.11.1 doc 2.12.1 fileshipper 1.2.0 generictts 2.1.0 grafana 2.0.3 idoreports 0.10.1 incubator 0.22.0 ipl v0.5.0 kubernetes 0.2.0 map 2.0.0 mapDatatype 0.1.0 monitoring 2.12.1 pdfexport 0.11.0 reporting 0.10.0 vspheredb 1.7.1
The problem was previously described here few year ago but the problem still occurs.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
If service name set using apply rules ends with whitespace, BP will mark the node as missing.
To Reproduce
Name a service in apply rule with trailing whitespace, e.g. "http " and try to add it as a new node in BP.
The object name will look like this:
* __name = "example.com!http "
Screenshots
If applicable, add screenshots to help explain your problem.
Your Environment
Icinga Web 2 Version 2.12.1
PHP Version 8.2.26
Loaded Libraries
icinga/icinga-php-library 0.14.1
icinga/icinga-php-thirdparty 0.12.1
Loaded Modules
businessprocess 2.5.1
icingadb 1.1.3
cube 1.3.3
director 1.11.1
doc 2.12.1
fileshipper 1.2.0
generictts 2.1.0
grafana 2.0.3
idoreports 0.10.1
incubator 0.22.0
ipl v0.5.0
kubernetes 0.2.0
map 2.0.0
mapDatatype 0.1.0
monitoring 2.12.1
pdfexport 0.11.0
reporting 0.10.0
vspheredb 1.7.1
Additional context
The problem was previously described here few year ago but the problem still occurs.
The text was updated successfully, but these errors were encountered: