- 0 minutes to read

Settings Sidebar Menu Item

Unlock centralized control and configuration for your integration environment with the Settings menu in the Nodinite Web Client. This page guides Nodinite administrators through the essential sub-menu options, helping you streamline operations, ensure compliance, and deliver business value with confidence.

✅ Centralized management of Alarm Plugins, External Instances, and Log Databases
✅ Secure and unified configuration for all integration settings
✅ Empowered administration for compliance and operational efficiency

On this page, a Nodinite Administrator learns how to navigate and manage the Settings sub-menu within the Administration sidebar, as seen in the Nodinite Web Client. This sub-menu includes Alarm Plugins, External Instances, and Log Databases.

Nodinite version 7 Nodinite Version 6
Settings menu items - Version 7 Settings menu items - Version

Here's the crucial 'Settings' menu item in the sidebar of the Nodinite Web Client, a vital tool for the Nodinite Administrator.

The following sub-menu items empower you to configure and secure your integration environment:

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

Nodinite version 7 Nodinite Version 6
Options

Here's an example of the Settings card as seen in the Administration Overview.

Configuration Best Practices

Alarm Plugins Strategy

When to Use:

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

Best Practices:

  • Redundancy: Configure 2+ plugins (e.g., Email + ServiceNow) for critical alerts
  • Filtering: Use Monitor Views to control which alerts go to which plugins
  • Testing: Always test in lower environments before production deployment
  • Templates: Use Stylesheets to format alert content for business users
  • Escalation: Configure time-based escalation using multiple plugins

Common Configurations:

  • Email Plugin - Operations team distribution lists
  • HTTP Webhook - Microsoft Teams, Slack, custom dashboards
  • ServiceNow/Jira - Automatic ticket creation for critical issues
  • SIEM Integration - Security operations center alerting

Log Databases Management

When to Use:

  • Add Log Databases as your integration event volume grows
  • Separate databases by environment (Dev, Test, Prod) or business unit
  • Archive historical data to secondary databases

Best Practices:

  • Capacity Planning: Monitor database growth, plan for 20-30% annual increase
  • Retention Policies: Define retention based on compliance requirements
  • Performance: Consider partitioning for databases >500GB
  • Backup Strategy: Regular backups aligned with RPO/RTO requirements
  • Geographic Distribution: Databases closer to integration platforms reduce latency

Sizing Guidelines:

  • Small deployments (<1M events/month): Single database sufficient
  • Medium deployments (1-10M events/month): Consider 2-3 databases (by environment)
  • Large deployments (>10M events/month): Multiple databases by business unit or region

External Instances Configuration

When to Use:

  • Connect multiple Nodinite instances across environments or regions
  • Enable Import/Export of configuration between instances
  • Consolidate monitoring across geographically distributed deployments

Best Practices:

  • Change Management: Export from Test → Import to Production for consistency
  • Disaster Recovery: Export configurations regularly as part of DR strategy
  • Multi-Region: Connect regional instances for consolidated global monitoring
  • Version Alignment: Ensure compatible Nodinite versions across instances
  • Security: Use encrypted connections between external instances

Common Scenarios:

  • Dev → Test → Prod Pipeline: Export configurations through environments
  • Multi-Region: Europe, Americas, Asia instances with centralized reporting
  • Acquisitions: Integrate newly acquired company's Nodinite instance
  • Backup Configuration: Export to archive before major changes

Alarm Queue Management

When to Use:

  • Monitor and troubleshoot alert delivery issues
  • Review failed alert attempts and retry mechanisms
  • Understand alert volume and patterns

Best Practices:

  • Regular Review: Check Alarm Queue daily for failed deliveries
  • Root Cause Analysis: Investigate why alerts failed (network, credentials, etc.)
  • Tuning: Adjust retry logic based on queue patterns
  • Cleanup: Archive or purge old queue entries based on policy

When to Review Settings

Weekly:

Monthly:

Quarterly:

  • External Instances - Verify connectivity and sync status
  • Review all settings for alignment with current operations

After Major Changes:

  • New integration platforms added
  • Organization restructuring
  • Compliance requirement updates
  • Technology stack changes

With Nodinite, you gain a unified, secure, and highly configurable platform for all your integration settings—empowering your team to streamline operations, ensure compliance, and deliver business value with confidence.

Next Step

Add or manage Log Database
Add or manage Alarm Plugin
Add or manage External Instance

Settings Components:

Alarm Plugins – Alert destinations and integrations
Alarm Queue – Monitor alert delivery
Log Databases – Storage and retention management
External Instances – Multi-instance connectivity

Related Configuration:

Monitor Views – Use Alarm Plugins for alerts
Stylesheets – Format alert content
ImportExport – Configuration migration between instances
Customize – Additional configuration options

Platform:

Administration – Main administration overview
Web Client – User interface
Log Views – Logging configuration