Advanced Configuration

Configure system-wide settings, email notifications, proxy servers, and execute scripts on your infrastructure.

Administrator Access Required

Most features on this page require administrator privileges.

System Settings

Access global system configuration options.

Accessing System Settings

1. Navigate to Settings → System Settings (Admin only)
2. The System Settings dialog opens with multiple tabs

General Settings

Application Settings:

• Session Timeout: How long users stay logged in (minutes)
• Auto-logout: Automatically log out inactive users
• Default Map: Map to load on login
• Language: Interface language (if multiple languages supported)

Performance Settings:

• Cache Duration: How long to cache Zabbix data (seconds)
• Update Interval: How often to refresh data (seconds)
• Max Concurrent Requests: Limit simultaneous API calls
• Enable Compression: Compress data transfers

Security Settings:

• Password Policy: Minimum length, complexity requirements
• Two-Factor Authentication: Enable 2FA for all users
• API Rate Limiting: Limit API requests per user
• Session Security: Secure cookie settings

API Configuration

Configure how MapZ communicates with Zabbix:

Timeout Settings:

• Connection Timeout: Time to wait for Zabbix connection (seconds)
• Read Timeout: Time to wait for Zabbix response (seconds)
• Retry Attempts: Number of retries on failure
• Retry Delay: Delay between retries (milliseconds)

Connection Pool:

• Pool Size: Maximum concurrent connections
• Keep-Alive: Keep connections alive between requests
• Connection Lifetime: Maximum connection age (minutes)

Error Handling:

• Log Failed Requests: Log all API errors
• Alert on Failures: Notify admins of repeated failures
• Fallback Behavior: What to do when Zabbix is unavailable

Logging Configuration

Control application logging:

Log Level:

• Debug: Verbose logging (development only)
• Info: General information
• Warning: Warnings and errors
• Error: Errors only

Log Retention:

• Retention Period: How long to keep logs (days)
• Max Log Size: Maximum size per log file (MB)
• Rotation: Automatic log file rotation

Log Destinations:

• Console: Log to console output
• File: Log to file system
• Syslog: Send to syslog server
• External Service: Send to logging service (e.g., Datadog, Splunk)

Data Management

Database Maintenance:

• Auto-cleanup: Automatically remove old data
• Cleanup Interval: How often to run cleanup (days)
• Retention Periods:
  • Map history: 90 days
  • User activity: 30 days
  • System logs: 60 days

Backup Settings:

• Auto-backup: Automatically backup database
• Backup Schedule: When to run backups
• Backup Location: Where to store backups
• Backup Retention: How many backups to keep

Email Notifications

Configure email alerts and notifications.

SMTP Configuration

1. Navigate to Settings → Email Settings
2. Enter SMTP server details:

SMTP Server Settings:

• Server Address: SMTP server hostname or IP
• Port: SMTP port (usually 587 for TLS, 465 for SSL, 25 for unencrypted)
• Encryption: None, TLS, or SSL
• Authentication: Enable if server requires login

Credentials:

• Username: SMTP authentication username
• Password: SMTP authentication password
• From Address: Email address for outgoing messages
• From Name: Display name for outgoing messages

Testing Email Configuration

1. After entering settings, click "Test Configuration"
2. Enter a test email address
3. Click "Send Test Email"
4. Check the inbox for the test message

If the test fails:

• Verify server address and port
• Check username and password
• Ensure firewall allows SMTP traffic
• Check SMTP server logs

Email Templates

Customize email notification templates:

Available Templates:

• Problem Alert: When a problem is detected
• Problem Resolved: When a problem is resolved
• Maintenance Notification: Maintenance window reminders
• Task Assignment: When a task is assigned
• System Alert: System-level notifications

Template Variables:

• {HOST_NAME}: Host name
• {PROBLEM_NAME}: Problem description
• {SEVERITY}: Problem severity
• {TIMESTAMP}: Event timestamp
• {MAP_NAME}: Map name
• {USER_NAME}: User name

Editing Templates:

1. Select a template from the list
2. Click "Edit"
3. Modify subject and body
4. Use template variables for dynamic content
5. Preview the template
6. Click "Save"

Notification Rules

Configure who receives which notifications:

1. Navigate to Email Settings → Notification Rules
2. Click "Add Rule"
3. Configure:
   • Event Type: What triggers the notification
   • Severity: Minimum severity level
   • Recipients: Who receives the notification
   • Schedule: When to send (always, business hours, etc.)
4. Click "Save"

Example Rules:

Rule 1: Critical Problems
- Event: Problem Detected
- Severity: High, Disaster
- Recipients: Admins, On-call team
- Schedule: 24/7

Rule 2: Maintenance Reminders
- Event: Maintenance Starting
- Recipients: All users
- Schedule: Business hours only

Rule 3: Task Assignments
- Event: Task Assigned
- Recipients: Assignee only
- Schedule: 24/7

Zabbix Proxy Configuration

Configure Zabbix proxies for distributed monitoring.

What is a Zabbix Proxy?

Zabbix proxies are used to:

• Monitor remote locations
• Reduce load on main Zabbix server
• Monitor behind firewalls
• Improve scalability

Adding a Proxy

1. Navigate to Settings → Proxy Settings
2. Click "Add Proxy"

3. Enter proxy details:

   • Proxy Name: Descriptive name
   • Proxy Address: IP or hostname
   • Proxy Mode: Active or Passive
   • Port: Proxy port (default: 10051)

4. Click "Test Connection"

5. If successful, click "Save"

Assigning Hosts to Proxies

1. Right-click on a host node
2. Select "Properties" → "General"
3. In the "Monitored by Proxy" dropdown, select the proxy
4. Click "Save"

The host will now be monitored through the selected proxy.

Proxy Monitoring

Monitor proxy health and performance:

Proxy Status:

• Online: Proxy is connected and working
• Offline: Proxy is not responding
• Degraded: Proxy is slow or having issues

Proxy Metrics:

• Last Seen: When proxy last connected
• Queue Size: Number of pending items
• Items per Second: Monitoring throughput
• Delay: Average delay in data collection

Proxy Troubleshooting

Proxy Shows Offline

Check:

• Proxy server is running
• Network connectivity
• Firewall rules
• Proxy configuration

Solution:

• Restart proxy service
• Verify network connectivity
• Check Zabbix proxy logs
• Verify proxy configuration matches MapZ settings

Script Execution

Execute Zabbix scripts on hosts directly from MapZ.

Prerequisites

• Scripts must be configured in Zabbix first
• User must have script execution permissions
• Host must be accessible

Executing a Script

1. Right-click on a host node
2. Select "Execute Script"

3. Select the script from the dropdown

4. Review script details:

   • Script name
   • Description
   • What it does
   • Required permissions

5. Click "Execute"

6. Confirm execution when prompted

7. View execution results:
   • Exit code
   • Output
   • Errors (if any)
   • Execution time

Available Scripts

Common scripts you might execute:

System Information:

• Get system uptime
• Check disk space
• View running processes
• Check network configuration

Diagnostics:

• Ping test
• Traceroute
• DNS lookup
• Port scan

Maintenance:

• Restart service
• Clear cache
• Rotate logs
• Update packages

Custom Scripts:

• Any scripts configured in Zabbix
• Organization-specific automation
• Custom diagnostics

Script Execution Logs

All script executions are logged:

1. Navigate to Settings → Script Execution Logs

2. View execution history:

   • Who executed the script
   • Which host
   • When
   • Result (success/failure)
   • Output

3. Filter logs by:

   • Date range
   • User
   • Host
   • Script name
   • Result status

Security Considerations

Script Permissions:

• Only authorized users can execute scripts
• Scripts run with Zabbix agent permissions
• Audit logs track all executions

Best Practices:

• Review scripts before execution
• Test scripts on non-production hosts first
• Document what each script does
• Limit script execution to necessary users
• Monitor script execution logs

User Management

Manage user accounts and permissions (Admin only).

User Roles

Administrator

• Full system access
• Manage users and settings
• Execute all scripts
• Access all maps

Manager

• Manage maps and hosts
• Assign tasks
• View all data
• Limited system settings access

User

• View and edit own maps
• Create hosts and connections
• Acknowledge problems
• Limited script execution

Viewer

• Read-only access
• View maps and data
• Cannot make changes
• No script execution

Creating Users

1. Navigate to Settings → User Management
2. Click "Add User"
3. Enter user details:
   • Username
   • Email
   • Full name
   • Role
   • Password (or send invitation)
4. Click "Create"

User Permissions

Configure granular permissions:

Map Permissions:

• Create maps
• Edit own maps
• Edit all maps
• Delete maps
• Share maps

Host Permissions:

• Add hosts
• Edit hosts
• Delete hosts
• Execute scripts

Problem Permissions:

• View problems
• Acknowledge problems
• Create tasks
• Assign tasks

System Permissions:

• Access system settings
• Manage users
• View logs
• Configure email

Advanced Features

API Access

Generate API keys for external integrations:

1. Navigate to Settings → API Keys
2. Click "Generate Key"
3. Enter key details:
   • Key name
   • Permissions
   • Expiration date
4. Copy the generated key (shown only once)
5. Use in external applications

API Key Permissions:

• Read-only: View data only
• Read-write: View and modify data
• Admin: Full access

Webhooks

Configure webhooks for external notifications:

1. Navigate to Settings → Webhooks
2. Click "Add Webhook"
3. Configure:
   • URL: Webhook endpoint
   • Events: Which events trigger the webhook
   • Payload: Data to send
   • Headers: Custom HTTP headers
4. Test the webhook
5. Click "Save"

Webhook Events:

• Problem detected
• Problem resolved
• Maintenance started
• Task created
• Map modified

Custom Integrations

Integrate with external systems:

Supported Integrations:

• Slack: Problem notifications
• Microsoft Teams: Alerts and updates
• PagerDuty: Incident management
• ServiceNow: Ticket creation
• Jira: Issue tracking

Setting Up Integrations:

1. Navigate to Settings → Integrations
2. Select the integration type
3. Follow the setup wizard
4. Authenticate with the external service
5. Configure integration settings
6. Test the integration

Troubleshooting

Email Not Sending

Check:

• SMTP settings are correct
• Server allows SMTP traffic
• Credentials are valid
• From address is allowed

Solution:

• Test SMTP connection
• Check server logs
• Verify firewall rules
• Contact email administrator

Proxy Connection Failed

Check:

• Proxy is running
• Network connectivity
• Firewall rules
• Proxy configuration

Solution:

• Restart proxy service
• Check Zabbix proxy logs
• Verify network connectivity
• Review proxy configuration

Script Execution Failed

Check:

• Script exists in Zabbix
• User has permissions
• Host is accessible
• Script syntax is correct

Solution:

• Verify script in Zabbix
• Check user permissions
• Test host connectivity
• Review script logs

Best Practices

System Configuration

1. Regular Reviews

   • Review settings quarterly
   • Update as needs change
   • Document changes

2. Security

   • Use strong passwords
   • Enable 2FA
   • Limit admin access
   • Audit user permissions

3. Performance

   • Monitor system resources
   • Adjust cache settings as needed
   • Optimize update intervals
   • Clean up old data

Email Configuration

1. Use Dedicated SMTP

   • Use a dedicated email service
   • Don't use personal email accounts
   • Configure SPF/DKIM for deliverability

2. Template Customization

   • Customize templates for your organization
   • Include relevant contact information
   • Use clear, actionable language

3. Notification Management

   • Don't over-notify
   • Use appropriate severity filters
   • Respect quiet hours

Script Management

1. Documentation

   • Document all scripts
   • Include usage instructions
   • Note any prerequisites

2. Testing

   • Test scripts thoroughly
   • Use non-production hosts for testing
   • Have rollback procedures

3. Access Control

   • Limit who can execute scripts
   • Audit script executions
   • Review permissions regularly

Related Features

• User Management: See Advanced Features
• Email Templates: Customize notification content
• API Integration: Extend MapZ functionality

caution

Changes to system settings can affect all users. Test changes in a non-production environment first, and document all modifications.