What is Logcore?

Logcore is a hosted monitoring service for your servers and applications. It collects three kinds of data:

Data	Sent by	Where you see it
Log lines from files on your servers	Logcore agent	Logs: search, facets, live tail
Host metrics: CPU, memory, disk, swap, load, network	Logcore agent	Infrastructure: host map, host pages
Traces, metrics and logs from your applications	OpenTelemetry SDKs, through the agent or directly	APM: services, traces, flame graphs

On top of that data you can set up monitors that notify Slack, Microsoft Teams or any webhook, and build reports you can export as CSV.

Key concepts

Organization. Everything in Logcore belongs to an organization: hosts, logs, traces, monitors, users and API keys. Users only ever see their own organization's data.

API key. A key (lc_…) tells Logcore which organization the data belongs to. Each agent, and each application that sends data directly, uses one. An organization can have up to 5 active keys at a time.

Agent. A small background service (logcore-agent) that you install on each server. It only makes outbound HTTPS connections, so you don't need to open any inbound ports.

Service. A named group of log files, defined in a YAML file on the server. For example, nginx could cover /var/log/nginx/*.log. Every log line is labelled with its service, host, status and tags.

Tags. key:value labels such as env:prod or role:web. Host tags are added to everything the host sends; service tags are added only to that service's logs. You can filter and group by tags everywhere in the dashboard.

Supported platforms

Agent	Requirements
Linux	x86_64 (amd64) or arm64, systemd, curl, sudo access
Windows	Windows Server 2016+ or Windows 10+, x64 or arm64, PowerShell 5.1+, Administrator

APM works with any language that has an OpenTelemetry SDK, including Node.js, Python, Java, .NET, Go, Ruby, PHP and Rust.

Next steps

• Quick start: go from sign-up to your first logs in five minutes.
• How it works: what the agent does with your files.