NXLog Platform 1.4.0
Release date: 16 December 2024
New
-
The agent onboarding wizard is now more user-friendly and combines agent download, configuration and enrollment.
-
Auto-enroll rules can now be toggled on or off.
-
Agent search boxes and MQL filters now support labels and modules in expressions.
-
NXLog Platform now displays the Agent Management API SwaggerUI documentation under Agents > tab API, allowing users to view and try out the API endpoints and their parameters.
-
NXLog Agent 6.5 adds the OpenTelemetry Exporter output module for forwarding OpenTelemetry logs and traces over both HTTP(S) and gRPC connections to an OpenTelemetry collector or backend.
-
NXLog Agent 6.5 adds the Microsoft Azure Logs Ingestion input module for providing better support of the Azure log monitoring stack through the Azure Monitor Log Analytics API. For example, it supports proxies, internal pagination of long responses, and more precise request handling.
-
NXLog Agent 6.5 adds wildcard support to the Windows Performance Counters input module, enabling users to specify multiple counters with a single directive.
-
Log flow provides a centralized, end-to-end visualization of the configuration templates in use by agents and the EPS transfer through the various log sources and destinations. Learn how to configure your log flow visualization.
This feature is currently in BETA and the two following known issues will be fixed in future NXLog Platform versions:
-
The log flow dashboard is saved in the browser’s local storage. If the local storage is deleted, or a different browser or private mode is used, then the dashboard must be reconfigured.
-
The performance of the log flow dashboard degrades for a large number of agents, causing refresh delays and sluggish performance.
-
Changed
-
Improvements to the user interface for setting up solution packs.
-
Agent Manager tables and widgets now show placeholders while loading instead of zeros.
-
Auto-enroll rules now add
enrolled=false
to rules if that condition is not explicitly added by the user. -
Sort preferences are now kept when switching between the different Agent tabs.
-
The agent Licensing tab was renamed to License Usage.
-
The log sources widget under Agents > tab License Usage now represents the usage percentage.
-
Now, the configuration builder correctly shows the available
InputType
andOutputType
data converters from the loaded extension modules. -
The default LogLevel for the Remote management module changed to
WARNING
.
Known issues
Agent management
-
If a large number of agents are added to the NXLog Platform through auto-enrollment, some agents may be shown as offline before returning to online.
-
Due to the change from the hostname
agents.tenant.DOMAIN_SUFFIX
toagents.DOMAIN_SUFFIX
, agents still using the old hostname will show a sync error on NXLog Platform. 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.
Log search
-
The character
_
must be replaced with%
in full text search or no results will be found. -
It’s not possible to save filters that use the Advanced mode, nor searches that use those filters.
-
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.
NXLog Platform UI
-
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.
NXLog Platform 1.3.1
Release date: 18 November 2024
Changed
-
Fixed an error in redirect URL validation during login.
-
Fixed an input validation issue in log search that could potentially lead to SQL injection.
-
Updated several third-party components to address security vulnerabilities.
-
Grafana no longer uses the default user name and password:
-
Fresh NXLog Platform installations provision the Grafana user
nxlog
with a random password -
Upgrades from earlier NXLog Platform versions keep the existing Grafana user
admin
and update the password to a random value
Run the following command to obtain the Grafana user name and password after installing or upgrading NXLog Platform:
$ sudo podman inspect nxlog-1_3_1-grafana-1 | jq -r '.[]|.Config.Env' | grep GF_SECURITY_ADMIN "GF_SECURITY_ADMIN_USER=nxlog", "GF_SECURITY_ADMIN_PASSWORD=kNdG6W1WHY7EQt9",
-
Known issues
Agent management
-
Due to the change from the hostname
agents.tenant.DOMAIN_SUFFIX
toagents.DOMAIN_SUFFIX
, agents still using the old hostname will show a sync error on NXLog Platform. 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.
Log search
-
The character
_
must be replaced with%
in full text search or no results will be found. -
It’s not possible to save filters that use the Advanced mode, nor searches that use those filters.
-
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.
NXLog Platform UI
-
The Log Database Management dashboard occasionally displays Prometheus error messages
-
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.
NXLog Platform 1.3
Release date: 22 October 2024
New
-
Added support for timing out NXLog Platform idle sessions after a configurable time period.
-
To make it easier to find and target agents in large agent populations, NXLog Platform now provides advanced filtering for finding agents using agent attributes like name, address, ID, operating system, status and so on. These attributes can be matched using simple equality, lists, regular expressions and may be combined using boolean operators and more.
-
NXLog Agent 6.4 installers can be configured to connect to an agent management endpoint and provision agent labels to ease agent configuration and automatic enrollment inside NXLog Platform. This configuration is available in Windows, Debian/Ubuntu, Red Hat Enterprise Linux, and macOS.
-
NXLog Agent 6.4 provides Open Telemetry collection using both HTTPS and gRPC based communication for collecting logs and traces.
-
NXLog Agent 6.4 implements a new schema-based event transformation method.
-
NXLog Platform on-premise can now be configured during installation to listen on an arbitrary port for incoming agent management connections.
-
The installer can now import a custom TLS certificate provided by your own internal CA or a public CA.
-
This version of NXLog Platform introduces new solutions packs to configure log collection quickly and efficiently. For more information, see the complete list of available solution packs.
Changed
-
NXLog Platform log search now uses tokenized search. Each word typed in the search field is added to the same search field in arbitrary arrangement. The character _ must be replaced with % in full text search or no results will be found.
-
The default NXLog Platform log search time interval is now the last 1 hour.
-
NXLog Platform on-premise deployments are limited to 500 incoming NXLog Agent connections for log collection. If more agents need to send logs to NXLog Platform on-premise, NXLog recommends implementing multi-tier log collection.
Known issues
Agent management
-
Due to the change from the hostname
agents.tenant.DOMAIN_SUFFIX
toagents.DOMAIN_SUFFIX
, agents still using the old hostname will show a sync error on NXLog Platform. 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.
Log search
-
The character
_
must be replaced with%
in full text search or no results will be found. -
It’s not possible to save filters that use the Advanced mode, nor searches that use those filters.
-
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.
NXLog Platform UI
-
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.
NXLog Platform 1.2
Release date: 6 September 2024
New
-
Updated and simplified deployment architecture for on-premises NXLog Platform instances.
-
Support for defining the NXLog Platform domain suffix during the installation process.
-
Support for changing the NXLog Agent management port from the default
5515
. -
Support for adding custom TLS certificates for the NXLog Platform web services.
-
Support for API key authentication in the Agent Management API.
Changed
-
Small NXLog Platform instances now require 6GB of RAM instead of 4GB.
-
NXLog Platform no longer requires a logical volume nor LVM for storing data.
-
The NXLog Agent management endpoint can now be accessed using the hostname
agents.DOMAIN_SUFFIX
instead ofagents.tenant.DOMAIN_SUFFIX
.
Known issues
Agent management
-
Due to the change from the hostname
agents.tenant.DOMAIN_SUFFIX
toagents.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.
Log search
-
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 isLIKE
. 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.
NXLog Platform UI
-
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.
NXLog Platform 1.1
Release date: 10 July 2024
New
-
Added support for automatic agent enrollment. You can now create enrollment rules based on various properties, and NXLog Platform will automatically enroll and configure new agents that match a rule.
-
Access to the Agent Management API. With the API, you can programmatically enroll, configure, and manage your agents, configuration templates, and automatic enrollment rules.
-
Introduced advanced log search filtering and filter groups. You can now filter your searches on multiple properties using
AND
andOR
operands and switch to advanced filtering mode. -
Full support for NXLog Agent version 6.2 and newer versions.
-
Limited support for NXLog Agent version 5.10 and newer minor versions.
Known issues
Agent Management
-
The configuration editor does not accept the
include_stdout
directive when configuringim_file
module instances. -
NXLog Platform does not check the compatibility of the configuration with the NXLog Agent instance before applying it.
Log Analytics
The log search and log management functionality is in BETA. There may be other issues that are not listed here.
-
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 theLIKE
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.
NXLog Platform UI and infrastructure
-
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 Platform 1.0
Release date: 1 February 2024
Thank you for joining us on this exciting journey. Your feedback and insights are invaluable as we strive to create a solution that meets and exceeds your log management requirements.
Stay tuned for regular updates, and do not hesitate to reach out to our support team for any assistance or queries.
Known issues
NXLog Agent
-
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.
Agent Management
-
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.
Log Analytics
-
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.
NXLog Platform UI and infrastructure
-
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.