Related to:

OP5 Monitor supports UTF-8 encoding; however, diacritical (accented) characters are not supported in host_name and service_description object fields. Attempting to use such characters in configuration templates may result in the value not being accepted or not being saved properly in the GUI.

Problem:

Configuring hostnames or service descriptions containing diacritical characters (e.g., accented letters such as ą, ć, ł, é, ñ).

Possible cause(s):

• Root Cause 1: host_name field validation restricts special/diacritical characters.
• Root Cause 2: service_description field validation restricts special/diacritical characters.
• Root Cause 3: UTF-8 support applies to encoding, but not all object definition fields allow extended character sets.

Possible solution(s):

[Guide: Please provide solutions that correspond in both number and order to the identified root causes.]

• Solution Root Cause 1: Replace diacritical characters in host_name with ASCII equivalents (e.g., ł → l, é → e).
• Solution Root Cause 2: Replace diacritical characters in service_description with ASCII equivalents.
• Solution Root Cause 3: If diacritical characters are required for display purposes, consider using them in fields that allow free-text content (e.g., display name fields, comments), while keeping object identifiers ASCII-compliant.

Related article(s):

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry