NXLog Platform Release Notes

Due to the change from the hostname agents.tenant.DOMAIN_SUFFIX to agents.DOMAIN_SUFFIX, existing agents will show a sync error on NXLog Platform 1.2. To fix this, run the action Update Configuration on the affected agents.

NXLog Platform does not check the compatibility of configurations with NXLog Agent instances before applying them.

The performance of the free text search degrades if more than about 3 million records are collected in a given day. This issue will be addressed in the next release.

It’s not possible to save filters that use the Advanced mode, nor searches that use those filters.

Switching a filter to the Advanced mode adds the suffix ::String to the field name when the filter operator is LIKE. You must preserve this suffix if you edit the filter expression manually.

The Search button is disabled when filtering using the Advanced mode. This mode automatically performs the search as soon as the filter expression changes.

You cannot change the search string after you switch to the Advanced filtering mode. To enter a new search string, you must clear the search and start over.

The data export functionality is currently unavailable.

Date pickers may not function properly when the browser and NXLog Platform use different time zones.

When configuring the Mail server settings, sending a test email does not work until you change the default sender email. However, you cannot change the email address before completing the mail server setup. Please click the button Save changes before sending a test email.

The configuration editor does not accept the include_stdout directive when configuring im_file module instances.

NXLog Platform does not check the compatibility of the configuration with the NXLog Agent instance before applying it.

Advanced mode filters and searches using them cannot be saved.

Switching to Advanced mode filters adds ::String to the field name when an existing filter uses the LIKE operator. You must preserve this string if you edit the filter expression manually.

The Search button is disabled when filtering in Advanced mode. This mode automatically applies the search when the filter expression is changed.

You cannot change the search string after you switch to Advanced filtering mode. To enter a new search string, you must clear the search and start over.

The data export functionality is currently unavailable.

The Quick Start view shows an Unprocessable Entity error in place of the Agents sending data widget.

Date pickers may not function properly when the browser and NXLog Platform use different time zones.

In NXLog Platform on-premises installations, the login page shows a link to Sign up even though this function is unavailable by design. We will remove it in a future release.

Two-factor authentication is currently unavailable. Enabling it results in an error.

When configuring Mail server settings, the function to send a test email does not work until you change the default sender email. However, you cannot change the email address before completing the mail server setup. Please Save changes first before sending a test email.

Pagination in My Organization > Users only shows users up to the first 15 table entries.

NXLog Agent versions 6.0 and 6.1 show unpredictable behavior when used with NXLog Platform. NXLog Agent version 6.2 is fully supported, and we recommend using this version.

If NXLog Agent is exporting a large number of module variables, the ServerInfo response may exceed 5MB. This may cause a segmentation fault or no response.

If NXLog Agent is maintaining a large number of network connections, the ServerInfo response may exceed 5MB. This may cause a segmentation fault or no response.

If NXLog Agent contains an error in the ListenAddr parameter of the xm_admin module configuration, it will try to reconnect without an exponential backoff pattern.

If NXLog Agent is administratively being stopped and started, there is a risk of losing events transmitted through an outgoing TCP connection. This can occur if the events are already queued in the operating system’s buffer.

Enrolling an agent may fail with NXLog Agent versions 6.0 and 6.1. The issue is fixed in NXLog Agent version 6.2.

Cluster functionality is not available.

The configuration builder does not detect the presence of the automatically created API connection parts in the configuration templates, resulting in a duplicated configuration block when viewing the configuration as text.

When a new CA is imported into NXLog Platform, the OS must be restarted to ensure all service-specific certificates are regenerated.

When the amount of free memory is low, enrollment requests may fail. Split enrollment to multiple smaller sets to overcome this issue.

Enrolling 10k+ agents in one go may result in an incomplete response. Please enroll a smaller selection of agents.

Large-scale enrollment operations may result in some agents falsely reporting that their configuration is invalid and was reverted. This occurs in about 1% of agents with a 30k agents set.

Sometimes, a "Template out of sync" error can only be resolved by assigning the agent to the template again.

If the Update Configuration action option is unavailable in Agent Details for an individual agent, use the multi-select menu to access it.

The configuration builder does not support Extension or Processor modules. You can specify these modules in the text mode configuration editor.

The SQL search requires the full SQL query syntax.

When querying your log data, you must use nxlog for the database name and logs_p for the table name.

NXLog Platform does not currently have a database/table discovery tool.

The full-text search does not allow complex queries.

The SQL search currently requires a limit clause in the SQL query.

The full-text search input is limited to 10000 characters.

If you attempt to export search results to CSV or JSON formats and the results exceed 10,000 records, a warning message will be displayed, indicating the maximum exportable record limit.

The Pager widget does not apply to an SQL search. It requires a manual LIMIT/OFFSET to be specified in the query.

Only the “monthly” payment option is available.

Unit prices are not shown in the order summary.

Final unit prices in the order are different from what is displayed on the plan and feature selector.

The user cannot choose a node count for node-based extra features that differ from the plan node count.

When registering a new organization, only a very limited number of countries can be selected.

The installer asks for 16GB RAM even for a test setup handling a handful of agents.

When starting NXLog Platform, some starting jobs fail and then restart. The NXLog Platform system fully comes up eventually, but the logs from the initialization contain errors.

Licensing limits are not enforced.

Multiple on-premises instances can be installed for a single organization. This is not supported.

The NXLog Platform Back Office and Administration Home pages are empty.

The Single Sign-On (SSO) integrations with third-party authentication services are not stable enough for use in production environments because they have not been fully tested.