- 5 minutes to read

Settings Sidebar Menu Item

The Settings menu in the Nodinite Web Client is where an administrator configures the platform itself: where alerts go, where logged data is stored, which other Nodinite instances you can export to, the global System Parameters, the license, and the agent installers. This page lists every Settings sub-area, shows how they connect, and links to the guide for each.

On this page, a Nodinite Administrator learns what each Settings sub-menu item in the Administration sidebar does. Day-to-day users don't need these pages; they work in Log Views and Monitor Views.

Nodinite version 7 Nodinite Version 6
Settings sub-menu in the Version 7 Administration sidebar of the Web Client (7.x) Settings sub-menu in the Version 6 Administration sidebar of the Web Client (6.x)

The Settings menu item sits in the Administration sidebar; only administrators see it.

Understanding the Settings Sub-Areas

The Settings sub-areas are not isolated: Alarm Plugins deliver the alerts that the Monitoring Service raises for Monitor Views, failed deliveries wait in the Alarm Queue, and System Parameters such as AlarmQueueSettings control the retries. Log Databases hold logged data, with retention set in System Parameters, and External Instances are the targets for Import/Export, which is disabled in Nodinite 7.0 (use the Web API for now).

graph LR settings["fa:fa-gear Settings"] subgraph alerting["Alert delivery"] ap["fa:fa-plug-circle-bolt Alarm Plugins"] aq["fa:fa-bell Alarm Queue"] end subgraph storage["Data and configuration"] ldb["fa:fa-database Log Databases"] sp["fa:fa-sliders System Parameters"] end subgraph platform["Platform upkeep"] lic["fa:fa-key Manage License"] agents["fa:fa-download Download and Update Agents"] end settings --> ap settings --> ldb settings --> lic settings --> agents ap -->|"Failed delivery"| aq sp -->|"AlarmQueueSettings retries"| aq sp -->|"Retention and naming"| ldb style settings fill:#2678BD,color:#fff style ap fill:#E47528,color:#fff style aq fill:#E47528,color:#fff style ldb fill:#3F827B,color:#fff style sp fill:#3F827B,color:#fff style lic fill:#9E59BB,color:#fff style agents fill:#9E59BB,color:#fff

The Settings sub-areas grouped by purpose: orange for alert delivery, teal for data and configuration, purple for platform upkeep. Arrows show where one area depends on another.

Sub-area What an administrator does there Start here
Alarm Plugins Configure the Email, Email with Options, Event Log, and HTTP Webhook plugins, and the reusable alarm entries that Monitor Views use Alarm Plugins Overview
Alarm Queue Review, delete, and purge alerts that could not be delivered Alarm Queue Entry
Log Databases Register, edit, and update the online and archive Log Databases Add or manage Log Database, Update Log Database
External Instances ❌ Not available in Nodinite 7: the only use was as a target for Import/Export, which stays out of 7.x –
System Parameters Tune retention, Log Databases, message processing, Log View data protection, alarms, and Web Client features Manage System Parameters
Manage License View the license and update the Product Key Manage License
Download and Update Agents Check agent versions and download the installers Download and Update Agents

Links to these settings are also available in the Administration Overview:

Nodinite version 7 Nodinite Version 6
Settings card in the Version 7 Administration Overview (7.x) Settings card in the Version 6 Administration Overview (6.x)

The Settings card in the Administration Overview offers the same links as the sidebar.

Configuration Best Practices

Alarm Plugins Strategy

When to Use Alarm Plugins

  • Configure Alarm Plugins to route alerts to your existing operational tools
  • Support multiple channels: Email, HTTP webhooks, SIEM integration, ticketing systems
  • Use different reusable alarm entries for different severity levels or business areas

Alarm Plugin Best Practices

  • Redundancy: Configure 2+ plugins (e.g., Email with Options + an HTTP Webhook to ServiceNow) for critical alerts
  • Filtering: Use Monitor Views to control which alerts go to which plugins
  • Testing: Use the Execute Alarm test in a lower environment before production
  • Templates: Use Stylesheets to format alert content for business users
  • Context: Add Custom Metadata such as owner and runbook to Integrations so alerts say who to call (how)
  • Maintenance windows: Use Maintenance Mode in User Notifications to suppress alerts during planned work

Common Alarm Plugin Configurations

  • Email with Options - Operations team distribution lists
  • HTTP Webhook - Microsoft Teams, Slack, custom dashboards
  • HTTP Webhook to ServiceNow/Jira - Automatic ticket creation for critical issues
  • Event Log - Security operations center alerting through SCOM or a SIEM

Log Databases Management

When to Add Log Databases

  • Add Log Databases as your integration event volume grows
  • Archive historical data to secondary databases

Log Database Best Practices

  • Capacity Planning: Monitor database growth, plan for 20-30% annual increase
  • Retention Policies: Define retention based on compliance requirements, using the retention System Parameters
  • Backup Strategy: Regular backups aligned with RPO/RTO requirements

External Instances Configuration

Note

Import/Export is not available in Nodinite 7, so External Instances have no use. The External Instances menu item may still show in 7.12; it is a leftover that a later release hides. Read External Instances for what they were.

Alarm Queue Management

When to Review the Alarm Queue

  • Monitor and troubleshoot alert delivery issues
  • Review failed alert attempts and retries

Alarm Queue Best Practices

When to Review Settings

How often What to review
Weekly Alarm Queue – delivery failures
Monthly Log Databases – growth and performance; Alarm Plugins – contact lists are current
Quarterly Manage License – expiry date; Download and Update Agents – new agent versions
After major changes New integration platforms, organization restructuring, compliance updates, technology stack changes

Next Steps