Skip to main content
Once a server is connected, the Logs service follows the server selected in the dashboard sidebar.

Explorer

Explorer is the search surface for stored events.
  • Filter by server, time range, level, event type, resource, message and player identifiers.
  • Open a result to inspect its identifiers, metadata and payload.
  • Export the current filter as CSV or JSON when your role allows exports. A single dashboard export includes at most 10,000 events; narrow the filter or split the time range for larger exports.
Growth retains events for 30 days; Pro retains them for 90 days. Explorer can search within the plan’s retention. SDK and public API queries have a separate seven-day limit per request. Retention follows the customer’s plan. Events older than the retention window are removed automatically.

Usage and allowances

Log Events is the single Logs allowance. It counts accepted events across all of your servers during your subscription billing period. An accepted batch of 500 events counts as 500 Log Events. Rejected batches count as zero. Retrying an accepted batch with the same batch ID and unchanged payload adds no usage. Custom integrations should preserve the batch ID when retrying. Open Billing to see accepted usage, your allowance and a projection for the end of the billing period. Usage refreshes after acceptance; delivery delays can postpone an update. The period follows your subscription renewal dates, rather than a calendar-month reset. The planned overage rate is €1 per additional million accepted events. During the observation period, Logs overage is not charged. The projection shows an estimate at that planned rate, not an amount due. Charging starts only after usage accounting is validated and customers are informed.

Analytics

Analytics summarizes accepted ingestion over the selected time range, including event volume, batches, payload size and the sources that contributed them. Use it to confirm ingestion is healthy and to see which resources produce the most activity. Analytics and payload-size metrics help you monitor ingestion. Payload bytes, batches and queries are not additional customer-facing billing quotas.

Settings

Settings applies to the server currently selected in the sidebar and holds the connection state, credentials and lifecycle actions.
Installation steps live in Set up FiveMesh Logs. Use Open installation guide to return to them whenever you connect another server.

Permissions

Logs respects organization roles and API key scopes.
  • logs:read searches events and reads event details.
  • logs:write ingests events from a server.
  • logs:export exports filtered events.
  • logs:admin enables, disables and deletes a server’s Logs configuration.

When events are missing

Confirm the correct server is selected, its Logs source is enabled and connection state is active. Check the SDK console for rejected or retrying batches, and allow time for accepted events to become searchable. Review the time range and filters before sending the event again.

Next steps