Q1: What is the “Optional Prefix” for event logs?
A1:
In NCC, event logs can now include an optional prefix. This prefix is a short, customizable text string that admins define in advance. When enabled, the prefix is automatically added at the beginning of each log message.
The main purpose is to improve log readability and filtering, especially in large environments or when exporting logs to external systems such as SIEM or syslog servers.
Q2: Why would I need to use a prefix?
A2:
The prefix helps differentiate logs when multiple sites, organizations, or teams are using the same monitoring system. For example:
An MSP managing several customers can add the customer code as a prefix.
A company with many branch offices can insert the office code (e.g., “LDN01” for London branch).
IT teams can tag logs for test vs. production environments.
Without a prefix, all logs look similar, which makes filtering and correlation harder.
Q3: How do I configure the prefix in NCC?
A3:
Administrators can set the prefix in the NCC Event Log settings page.
The prefix field is optional.
If you leave it blank, logs are generated normally (without prefix).
If you enter text (e.g., “HQ”), that string will appear in front of every log line exported from NCC.
This setting is simple and does not affect device operation — it only modifies how the log message is displayed or exported.
Q4: Does the prefix affect all types of event logs?
A4:
Yes. Once configured, the prefix is applied consistently to all event logs in that site/organization, regardless of whether they are viewed directly in NCC, downloaded, or forwarded to external logging systems.
Q5: Can I use special characters in the prefix?
A5:
The prefix is designed to be a short text label. Best practice is to use only alphanumeric characters and dashes/underscores (e.g., “SITE-1” or “LAB_ENV”). While some special characters may technically work, they can cause parsing issues in external SIEM systems.
Q6: What are some best practices for prefixes?
A6:
Keep it short – ideally under 10 characters, so log lines remain readable.
Use a clear scheme – for example, country + site number (e.g., “DE-02” for Germany site 2).
Be consistent – if you manage many sites, stick to the same naming convention across all.
Avoid frequent changes – changing prefixes often can make historical log analysis more difficult.
Q7: What happens if I change the prefix later?
A7:
If the prefix is updated, all new logs will carry the new prefix, but older logs will still show the previous value. This makes it possible to trace logs back to when the change occurred. However, it also means that filters or SIEM rules may need updating to account for the new prefix.
Q8: Does the optional prefix replace site or org names in logs?
A8:
No. Existing fields such as site name, device name, or org ID remain unchanged. The prefix is an extra tag that is added at the start of the message, not a replacement for existing identifiers.
Summary
The Optional Prefix feature for event logs is a simple but powerful enhancement for NCC. It helps MSPs and enterprise admins organize and filter logs more effectively, especially when handling events from multiple sites or exporting them to centralized monitoring systems. By applying clear and consistent prefixes, IT teams can save time during troubleshooting and improve the clarity of log data.
Comments
0 commentsPlease sign in to leave a comment.