Opsview 6.8.x End of Support

With the release of Opsview 6.11.0 on February 2025, versions 6.8.x have reached their End of Support (EOS) status, according to our Support policy. This means that versions 6.8.x will no longer receive code fixes or security updates.

The documentation for version 6.8.9 and earlier versions will remain accessible for the time being, but it will no longer be updated or receive backports. We strongly recommend upgrading to the latest version of Opsview to ensure continued support and access to the latest features and security enhancements.

Supported Unicode characters

Overview Copied

Opsview uses the UTF-8 encoding and supports a wide range Unicode characters in most string fields.

Object names will limit to characters categorized as Unicode “Letters” and “Numbers”, while descriptions and other types of data will additionally allow Unicode “Punctuation”, “Symbols” and “Separators”. Notes fields will allow some additional whitespace and formatting characters.

Note

Every field may have individual allowed or disallowed characters or length constraints, which will be reflected in the UI and API responses. There are still select fields that limit to the “Basic Latin” Unicode block (equivalent to ASCII), for example. Additionally, most fields will not allow leading whitespace, and will trim trailing whitespace.

Limitations Copied

• Unicode marks used in combined characters, such as Ä́, are not supported .
• Composite emojis, such as 👨‍👩‍👧‍👦, ❤️, or 🇬🇧, are not supported.
• Characters added in Unicode 6.1 and above (2012) will not be supported on all operating systems.
• Unicode characters not supported by the fonts provided with Opsview may or may not be displayed correctly depending on your system fonts.
• Opsview does not support International Domain Names (IDN) for DNS name fields.
• UTF-8 characters outside the “Basic Latin” block returned from SNMP Polling checks, or from Interface Names when querying SNMP-enabled Hosts, will be displayed as a Hex-String.
• UTF-8 characters outside the “Basic Latin” block are not supported in performance data labels, and will be converted to underscores.

Interact with Opsview Copied

To interact with Opsview correctly:

• Opsview must be used with a browser set to use the UTF-8 character encoding.
• When communicating with the Opsview REST API manually, ensure only the utf-8 charset is provided in the Content-Type header, if a charset is provided.

When inserting invalid data via the UI or REST API, error messages similar to the following may appear:

• The value in this field is invalid, Invalid characters, Failed allowed regex, Disallowed characters, and Failed disallowed regex — you have inserted characters that either do not match the allowed regex validation, or match a disallowed regex. Normally, the regex will be provided in the error message, so the invalid characters can be identified and removed. Note that invisible characters or some control characters could be inserted if pasting in from another source rather than typing, so these will need to be removed if present.
• Failed maximum length, Failed minimum length, Too many characters, and Too few characters — you have inserted too many or too few characters. Normally the limit either way will be provided in the error message.
• Failed maximum length ... on uri-encoded and Too many characters when URI encoded — this field requires the value to be below a certain limit when URI-encoded. Unicode characters which encode to multiple UTF-8 bytes will encode larger, so could take you across this limit and will need to be removed.
• Disallowed unicode characters outside Basic Multilingual Plane — this field requires all characters to be 3 UTF-8 bytes or less when encoded (for example, in the first plane of Unicode). Any characters outside the BMP will need to be removed.

Known issues Copied

Refer to the Opsview 6.x Known Issues page for the following:

• For OS-generic issues, see Character support.
• For OS-specific issues on older operating systems, see CentOS 7, OEL 7, and RHEL 7.