Integrations

Loguro integrates with messaging platforms and issue trackers so you can act on logs without leaving the console. All integrations are project-scoped and configured per project from the filter bar or command palette.

Messaging

Slack

Connect a Slack workspace to send log summaries and alerts to any channel.

Setup:

--integrations::config:slack

Enter your Slack bot token and default channel, then press Cmd/Ctrl + Enter to save.

Send a message:

--send:slack
--send:slack#incidents

If a default channel was set during setup, --send:slack posts there. Pass #channel to override. Custom channel targeting requires the Pro plan.

Discord

Discord uses a webhook URL — no app setup required.

Setup:

--integrations::config:discord

Send a message:

--send:discord

Available on all plans.

Telegram

Telegram uses a bot token and chat ID. Create a bot via @BotFather and get your chat ID before setup.

Setup:

--integrations::config:telegram

Enter your bot token and chat ID, then press Cmd/Ctrl + Enter to save.

Send a message:

--send:telegram

Available on all plans.

Supported channels (notification alerts)

Account-wide notification channels used by alerts support:

Issue trackers

Create bug reports and tasks directly from log entries.

Supported trackers

• Linear — API key + team ID
• Jira — Base URL, email, API token, project key
• GitHub Issues — Personal access token, owner, repository

Setup

--integrations::config:linear
--integrations::config:jira
--integrations::config:github

Enter your credentials and press Cmd/Ctrl + Enter to save.

Creating an issue

From the filter bar:

--task:linear
--task:jira
--task:github

Loguro opens a form pre-filled with the log’s message, level, timestamp, and context.

With log context: Click logs in the console to add them to the global context (up to 20 logs), then run --task:linear. All selected logs are included in the issue description.

Memory & forever logs

When an issue is created, the associated log(s) are written to permanent memory — they survive your plan’s log retention window indefinitely.

Additionally, any future log with a similar message pattern is automatically linked to the same issue. The issue key appears inline next to those logs in the console, so you know when an old problem resurfaces — even years later.

Search memory:

--memory
message:"payment failed" --memory --count

See Memory & Forever Logs for details on how pattern deduplication works.

Viewing tasks

--tasks:list
--tasks:list:linear
--tasks:list:jira
--tasks:list:github

Task statuses sync automatically every 5 minutes. Use the sync button in the tasks list to force a refresh.

Plan limits

Chaining integrations

Use the > pipe operator to combine actions in one command:

--task:linear > --send:discord
--task:jira > --send:slack#eng

Creates the issue, then immediately sends a notification to the configured channel.