FiveM observability
FiveMesh Logs for searchable server events.
Centralize player, admin, vehicle, inventory, economy and resource events from every connected FiveM server. Search by time, severity, event type, resource, player or identifier, then inspect the full context and export what you need.
Metric 01
5
Severity levels
Metric 02
2
Export formats
Metric 03
90 days
Maximum retention
Metric 04
25M
Events per month on Pro
Problem
Server history is scattered across tools and channels.
FiveM teams often send player, admin and economy events into separate Discord channels or custom files. Important context becomes difficult to search, related events stay disconnected and investigations turn into manual scrolling.
FiveMesh approach
Keep structured events in one searchable operational record.
FiveMesh Logs brings events from connected servers into a shared workspace with precise filters, full event details, exports and ingestion analytics built around FiveM operations.
Use cases
Built around the work your server already does.
Player and moderation history
Find player actions, admin decisions and related targets by handle or exact platform identifier.
Inventory and economy investigations
Trace structured inventory, transaction and job events without searching across disconnected Discord channels.
Resource and error diagnosis
Filter warning, error and fatal events by resource, event type or time range to narrow an incident quickly.
Multi-server operations
Search all enabled sources together or isolate one registered server when an issue is local.
Audits and handoffs
Export the exact filtered result set as CSV or JSON for moderation reviews, support cases or offline analysis.
Workflow
Simple enough to start, clear enough to operate.
Step 1
Connect a server
Register your FiveM server in the workspace and enable it as a Logs source.
Step 2
Send structured events
Use the FiveMesh SDK for automatic sources or send your own events through the ingestion API.
Step 3
Search and filter
Query by time, server, severity, message, event type, resource, player handle or exact identifier.
Step 4
Inspect and export
Open the full event context, follow the fields that matter and export the result set when needed.
set FIVEMESH_SERVER_ID "your-cfx-server-id"
set FIVEMESH_LOGS_API_KEY "fm_live_..."
set FIVEMESH_LOGS_AUTOMATIC "true"
ensure fivemesh-sdkIn-game staff viewer
Give authorized staff a focused way to search logs in game.
The optional, open-source fivemesh-logs resource opens a focused Logs Explorer inside FiveM. Staff can investigate the same source connected to FiveMesh without leaving the server or receiving workspace credentials.
View resource on GitHubSearch the same source
Filter by time, severity, message, event type, resource, player handle or an exact player identifier from inside the server.
Inspect the full event
Review timing, resource, player and target context, structured JSON and safe image evidence without leaving the viewer.
ACE-controlled staff access
Only principals with fivemesh.logs.view can open the viewer, and authorization is checked again for every search.
Credentials stay server-side
A separate read-only query key remains in the FiveMesh SDK server runtime and is never sent to the game client or NUI.
set FIVEMESH_SERVER_ID "your-cfx-server-id"
set FIVEMESH_LOGS_QUERY_API_KEY "fm_live_..."
add_ace group.admin fivemesh.logs.view allow
ensure fivemesh-sdk
ensure fivemesh-logsControls
The controls operators expect.
FiveMesh Logs keeps the operational surface focused: fewer moving parts, clearer control and enough visibility to know what changed.
01
Precise event search
Combine common filters with resource, player and identifier fields to reach the relevant events faster.
02
Structured event context
Inspect timestamps, source, resource, trace, player identifiers and custom event data in one detail view.
03
Ingestion analytics
Track accepted events, batches, payload volume and pipeline timing across enabled sources.
Comparison
Discord log channels vs FiveMesh Logs
Keep Discord for notifications and team communication. Use FiveMesh Logs when you need structured history and repeatable investigation.
Discord log channels
FiveMesh Logs
FAQ
Answers before you start.
What is FiveMesh Logs?
FiveMesh Logs is a centralized event and log platform for FiveM servers. It stores structured server events so operators can search, filter, inspect and export activity from one workspace.
Can server staff browse logs in game?
Yes. The optional fivemesh-logs resource gives ACE-authorized staff an in-game viewer opened with /fmlogs. It searches the connected FiveMesh source while keeping the read-only query key on the server.
How do I connect a FiveM server?
Register the server in your FiveMesh workspace, enable it as a Logs source and configure the FiveMesh SDK with the server ID and a Logs ingestion API key. Custom integrations can also send structured events to the ingestion endpoint.
What can I search for?
You can search by server, time range, severity, message, event type, resource, player handle and exact player or target identifiers such as a Discord identifier.
Can I export log results?
Yes. Filtered results can be exported as CSV for spreadsheet workflows or JSON for development and deeper analysis.
How much history is retained?
Retention depends on your plan. Growth includes 30 days of Logs retention and Pro includes 90 days, with the current allowance shown in the dashboard.
Which plans include FiveMesh Logs?
FiveMesh Logs is included with Growth and Pro. Growth includes 5 million events per month, while Pro includes 25 million events per month.
Available in the dashboard
Bring your server events into one searchable timeline.
Connect a registered FiveM server, enable a Logs source and investigate events from the same workspace as the rest of your infrastructure.