Projects and API keys
Create projects and the keys your applications use to send logs.
This page covers the two things you need before sending logs: a project and an API key.
Projects
A project groups the logs of one application or service, with its own error groups, tickets, channels and notification settings. Admins and owners create projects under Projects in the organization, with New project. The number of projects depends on the plan (Plans and usage).
Deleting a project deletes its keys, channels, groups and tickets. It cannot be undone.
Log history
Keep log history, under Settings in the project, is on by default. It stores the project's redacted log lines for replay, for your plan's retention. Admins and owners can turn it off. New lines then stop being stored, and lines already stored are deleted when their retention ends. The change is recorded in the audit log and does not affect group history, which holds only counts.
API keys
Applications authenticate with a project API key:
Authorization: Bearer lgf_live_<key_id>_<secret>Admins and owners create keys under API keys in the project, with Create API key. The full key is shown once, right after it is created; dlogify stores only a hash of the secret and cannot show it again. Keep it in an environment variable such as LOGIFY_API_KEY, never in source control.
Until the project receives its first log, the project's Overview shows ready-to-paste setup for curl and for OpenTelemetry, a button to create a key, and Waiting for the first log…. Once a log arrives, the setup folds away and the overview shows the project's recent tickets and error groups.
A key only sends logs to its own project. It cannot read data or call management endpoints.
The keys table shows each key's accepted events in the last 24 hours, with an hourly line, and this month. Select a key to see its last 48 hours by hour and its last 90 days by day, with rejected events stacked above accepted ones. A key that suddenly sends far more than usual, or stops sending, shows here first. See usage per API key for what each number counts.
Admins and owners rename a key on its page, under Name. Renaming changes only the label shown in the dashboard; the key keeps working and applications need no change.
Rotating a key
- Create a new key.
- Deploy it to your applications.
- Once nothing uses the old key, revoke it on the same page.
A revoked key stops working within seconds. Requests that use it get 401 unauthorized.