On this page

Getting started

This chapter helps new users get started with Mugnsoft. We will begin by explaining a few essential Mugnsoft concepts and terminology and then discuss installation, configuration and introduce you to the top level navigation of the interface.

Essential Concepts

Several fundamental concepts underlie and drive the Mugnsoft system. If you are a new user, knowing about them will help you use or integrate Mugnsoft into your environment.

Platform Components

  • MNS Webserver (port 8050/9090): The central management hub that manages the entire infrastructure and data. Components (a.k.a. Servers), Monitors, Reports, Downtimes, and Users are managed through its Web UI. It bundles its own REST API interface (port 8050) that starts simultaneously with its Web UI (port 9090). Learn more
  • MNS Monitor (port 8051): A distributed probe responsible for executing monitoring checks – business transaction scenarios (Selenium), URL checks, API checks, TCP, Ping, DNS, SNMP, Database queries, and System metrics. It exposes a REST API and stores results locally in the embedded key-value store. Deploy multiple probes across your infrastructure for distributed monitoring. Learn more
  • MNS Integrator (port 8052): A high-throughput data forwarding engine that receives monitoring results and dispatches them to third-party systems (InfluxDB, Splunk, Elasticsearch, Kafka, Zabbix, Canopsis) and notification channels (Email, Slack, Teams, PagerDuty). Learn more
  • MNS Sentinel Agent (port 8070, still discovery_agent internally — config file, binary, and API keep that name): A system and process metrics collector that monitors the host it runs on. It discovers services by process name and port, collects CPU/memory/I/O/network metrics, and generates threshold-based alerts. Includes network traffic analysis via packet capture. Learn more

Monitoring Concepts

  • Monitor (EUM): A business transaction scenario executed via Selenium WebDriver in a real browser. Supports multi-step transactions, screenshots, video recording, and HAR file capture.
  • URL Check: An HTTP/HTTPS endpoint check that measures response time, validates status codes, checks SSL certificate expiry, and supports pattern matching.
  • API Check: A REST API endpoint check supporting GET/POST/PUT/DELETE methods with custom headers, body, and response validation.
  • TCP Check: A TCP port connectivity check measuring connection time.
  • Ping Check: An ICMP echo check measuring latency, jitter, and packet loss.
  • DNS Check: A DNS resolution check validating lookup time and responses.
  • SNMP Check: An SNMP OID polling check supporting v1/v2c/v3 with MIB expression evaluation.
  • Database Check: A database query check supporting MySQL and MSSQL with result validation.
  • System Check: A self-monitoring check collecting CPU, memory, and disk metrics from the probe host.

Key Concepts

  • Downtime: A scheduled time window during which a monitor should not run. The monitor is in a disabled state, and alerts are suppressed.
  • Keystore (KV Store): An embedded key-value database. Each component has its own keystore – no external database is required.
  • WebDriver: An API and protocol for controlling web browsers. Each browser (Chrome, Firefox, Edge) requires a matching WebDriver. The Monitor auto-detects browser versions and downloads the correct WebDriver. For details, refer to the Selenium documentation.
  • JSON Web Token (JWT): An internet standard for creating signed access tokens. Mugnsoft uses RS256 (RSA + SHA-256) for token signing. User tokens expire after 15 minutes; component tokens last 60 days.
  • mTLS (Mutual TLS): All inter-component communication uses mutual TLS authentication where both parties verify each other’s certificates.
  • SSL Certificates: TLS certificates are auto-generated during installation. Components exchange certificates during self-registration for mTLS.
  • Auto-Thresholding: Monitors can automatically calculate performance thresholds based on historical data using standard deviation analysis.
  • Tags: Labels applied to monitors, components, and users for organizing and scoping access. Users only see resources matching their assigned tags.

Translations

Use cases