Server Build Info

View detailed information about your MongoDB server including version details, system configuration, SSL/TLS setup, storage engines, and network compression. Server build info helps you verify deployment configuration, troubleshoot compatibility issues, and ensure security settings are correct.

Version Information

The version section displays MongoDB's release version and build details, helping you confirm which version is running and whether it's a production or debug build:

Field	Description	Why It Matters
Version	MongoDB release version (e.g., 7.0.5, 6.0.13)	Determines available features, compatibility with drivers, and security patch level
Version Array	Version broken into numeric components [major, minor, patch]	Useful for programmatic version comparison and compatibility checks
Git Version	Exact commit hash from MongoDB's source repository	Pinpoints the exact code revision; useful for bug reports and support tickets
Build Type	Indicates Production or Debug build	Debug builds have extra logging and slower performance; production servers should always use release builds

System Information

The system section reveals platform details, compiler info, and MongoDB's internal configuration. This helps you verify architecture compatibility and understand how MongoDB was compiled:

Field	Description
Architecture	System architecture and bit version (e.g., x86_64, 64-bit)
Distribution	Operating system distribution (e.g., Ubuntu 22.04, RHEL 8)
Target OS	Operating system MongoDB was built for (Linux, Windows, macOS)
JavaScript Engine	JavaScript runtime used (typically mozjs for MongoDB 4.0+)
Memory Allocator	Memory management library (tcmalloc, system, etc.)
Max BSON Size	Maximum allowed BSON document size (typically 16 MB)
Compiler	Compiler and version used to build MongoDB (e.g., GCC 11.2, MSVC 19.29)
Storage Engines	Available storage engines (WiredTiger, devnull, ephemeralForTest, etc.)

SSL/TLS Information

The SSL section shows OpenSSL version details for both running and compiled versions. This is critical for security auditing and ensuring your MongoDB deployment uses up-to-date SSL libraries:

What You'll See

• Running Version - The OpenSSL library version currently loaded by MongoDB at runtime
• Running Date - Release date of the running OpenSSL version
• Compiled Version - The OpenSSL version MongoDB was originally built against
• Compiled Date - Release date of the compiled OpenSSL version
• Version Match Status - Green badge if versions match, yellow warning if they differ

Understanding Version Mismatches

A version mismatch between running and compiled OpenSSL can occur when:

• Your operating system updated OpenSSL libraries after MongoDB was installed
• MongoDB was compiled on a different system with a different OpenSSL version
• You deployed a MongoDB binary built for a different OS distribution

Note: Minor version mismatches are usually safe due to OpenSSL's backward compatibility. Major version differences (e.g., OpenSSL 1.1 vs 3.0) may indicate compatibility issues and should be investigated.

Network Compression

MongoDB supports network compression to reduce bandwidth usage between clients and servers. This section lists available compression algorithms your server supports:

Common Compression Algorithms

Algorithm	Description	Best For
snappy	Fast compression with moderate compression ratio	Low-latency networks, CPU-sensitive workloads
zlib	Better compression ratio but slower than snappy	Bandwidth-constrained networks, large documents
zstd	Best compression ratio with good speed (MongoDB 4.2+)	Modern deployments needing optimal bandwidth savings

If no compression algorithms are shown, network compression is not enabled or supported by your MongoDB version.

Additional Information

The bottom section provides quick stats and status indicators:

Metric	Description
Loaded Modules	Number of MongoDB Enterprise modules loaded (e.g., enterprise authentication, LDAP)
Storage Engines	Count of available storage engines (WiredTiger is the default and recommended engine)
Server Status	OK (green) if the server responded successfully, ERROR (red) if the command failed

Available Actions

Refresh Information

Click the Refresh button to reload server build information. The button shows a spinner animation while loading. Use this after server upgrades or configuration changes to verify the new settings.

Copy Details

Click on version strings or other text fields to copy them to your clipboard for documentation, support tickets, or comparison purposes.

Connection Status

The header displays a green dot with "Connected" or red dot with "Disconnected" to show real-time connection status to the MongoDB server.

Pro Tips

1. Version Verification: Always check server version before deploying application code. Features and commands vary between MongoDB versions, and using unsupported features causes runtime errors.
2. Production Build Check: Ensure the Build Type shows "Production" or "Release" on production servers. Debug builds have 10-30% performance overhead and should only be used for development troubleshooting.
3. SSL Security: If using SSL/TLS connections, check that running OpenSSL version is recent and matches compiled version. Mismatched major versions may cause connection failures or security vulnerabilities.
4. Storage Engine Confirmation: Verify WiredTiger is in the available storage engines list. WiredTiger is the default since MongoDB 3.2 and provides better performance and compression than older engines.
5. Architecture Match: Ensure the Architecture field matches your deployment environment. Running 32-bit MongoDB binaries is not supported for production and has a 2GB data limit.
6. Compression for Remote Connections: If connecting to MongoDB over the internet or slow networks, check that compression algorithms are available and enable them in your connection string for bandwidth savings.

Understanding Build Info Commands

VisualLeaf executes these MongoDB commands to retrieve server information:

Build Information

db.adminCommand({ buildInfo: 1 })

Returns version, system configuration, OpenSSL details, modules, storage engines, and compilation flags.

Hello Information

db.adminCommand({ hello: 1 })

Returns server status, replication info, and network compression capabilities. The hello command replaced the deprecated isMaster command in MongoDB 5.0.

Performance Considerations

• No Performance Impact - Build info commands only read server metadata and don't access any data or indexes
• Instant Response - Results are served from server memory; no disk I/O required
• Safe to Run Anytime - You can safely refresh build info during heavy production workloads
• No Locking - These commands don't acquire database locks

Common Use Cases

Version Compatibility Checks

Before deploying application updates, verify the MongoDB version supports the features and commands your code uses. For example, transactions require MongoDB 4.0+, and zstd compression requires 4.2+.

Security Audits

Check OpenSSL versions during security audits to ensure your deployment isn't vulnerable to known SSL/TLS exploits. Compare running and compiled versions to detect unexpected library changes.

Troubleshooting Connection Issues

If clients can't connect or report compression errors, check available compression algorithms and ensure client-requested algorithms match what the server supports.

Deployment Verification

After deploying new MongoDB binaries or upgrading servers, use Server Info to confirm the new version is running, the architecture is correct, and all expected modules are loaded.

Support Tickets

When opening MongoDB support tickets, include the full version string, git version, OS, and compiler information to help support engineers reproduce issues in matching environments.

Related Features

• Database Statistics - View storage, collection counts, and index sizes for databases on this server
• Collection Statistics - Drill into individual collection metrics including cache usage and storage details
• Connection Manager - Manage MongoDB connections and view all connected servers
• Query Monitor - Enable and configure database profiling to capture slow queries
• Access Control - Verify and manage user roles and permissions on the server