Skip to main content
FiveMesh Logs collects player, inventory, economy and staff events from a FiveM server into one searchable view. Each server connects to Logs with the FiveMesh SDK and its Server API Key. The same key supports ingestion and the optional in-game staff viewer.

Prerequisites

Before you connect a server, confirm:
  • The resource owner’s account has an active Growth or Pro plan.
  • The cfx.re server is registered in Servers and selected in the sidebar.
  • You can edit your server’s server.cfg.
  • Someone with permission to manage the Server API Key can generate it from the Server page.

Connect a server

1

Select the server

The dashboard sidebar carries the selected server into every service. Open Logs and confirm the server you want to connect.
2

Enable Logs for the server

The first time the customer uses Logs, the page asks the resource owner to activate Logs for their account. Logs is available on Growth and Pro. After that, click Enable Logs for this server to create its source.
3

Generate the Server API Key

Open this Server in the dashboard and click Generate API key under Server API Key. Copy it now; FiveMesh shows the raw key only once.
4

Install the SDK

Download the latest FiveMesh SDK release and place it in your server resources like any other resource.
5

Configure server.cfg

Add the Server API Key to server.cfg. The key is already bound to this server.
Enable automatic logging only if you want the built-in events. Restart or reload the server with your normal deployment process.
6

Verify ingestion

Open Logs > Explorer. Generate server activity, then refresh Explorer. Events can take time to become searchable after ingestion has been accepted.
Keep the Server API Key in server-side configuration. Never put it in client Lua, NUI code or a public repository. If you lose it, rotate it from the Server page.

What the SDK records automatically

With FIVEMESH_LOGS_AUTOMATIC enabled, the SDK captures events from:
  • FiveM server and resource lifecycle
  • Player connections and baseevents death and kill notifications
  • ox_inventory item and money movement
  • txAdmin moderation actions
Resources can also send their own events through the SDK exports. See SDK Logs exports.

Automatic logging controls

FIVEMESH_LOGS_AUTOMATIC defaults to false. You can enable or disable individual integrations independently:
Death and kill notifications require baseevents and are client-reported. The SDK marks them as client_reported; treat them as operational context. Successful inventory actions require ox_inventory 2.47 or newer; older releases report observed hook attempts.

In-game staff viewer

The optional fivemesh-logs resource opens the Explorer inside the game with /fmlogs. It requires fivemesh-sdk 0.1.5 or newer.
  1. Download the latest FiveMesh Logs viewer.
  2. Configure the viewer and restrict access to staff groups. It uses the same Server API Key as the SDK.
Place the FIVEMESH_API_KEY setting before both ensure lines. The Server API Key already identifies this server.
Set FIVEMESH_LOGS_VIEWER_COMMAND to change the command or FIVEMESH_LOGS_VIEWER_ACE to change the required ACE permission. Configure them before starting the viewer. Grant access only to staff authorized to inspect player identifiers and structured event data.

Direct ingestion

Integrations that do not use the SDK can post atomic event batches directly to the ingestion endpoint shown in Logs > Settings. See the Logs ingestion reference for the payload and retry rules.

Next steps