Slack

dlogify posts to Slack through an incoming webhook: a secret URL that lets anyone who has it post to one channel. You paste that URL in dlogify; no Slack app needs to be installed.

Create the channelCopy Anchor Link

1. In Slack, create an incoming webhook for the channel that should receive tickets (Slack's guide). Copy its URL: https://hooks.slack.com/services/T…/B…/….
2. In dlogify, open the project, go to Channels and select Add channel, then Slack.
3. Give it a name, paste the URL and select Add channel.
4. Select Send test on the new row. A test message appears in the Slack channel.

dlogify stores the URL encrypted and never shows it again; the channel list shows a hint such as hooks.slack.com/services/T01…/B04…/…GHij. To use another URL, delete the channel and add a new one.

What a message containsCopy Anchor Link

• Ticket: severity, service and title with a link to the ticket, the summary, the probable cause and suggested fix, and the project, service, environment, category, trigger, occurrences, first and last seen. The color of the bar follows the severity.
• Digest: up to 10 tickets with links, a link to the rest, and the INFO totals with the latest summary.

The stack trace and the log lines around the error are not sent to Slack; open the ticket to see them. Text from your logs is escaped, so it cannot mention @channel or a user, or hide a link behind other text. A plain URL in a log message still shows as a link, with its real address.

When delivery failsCopy Anchor Link

If the webhook is removed, or the channel is archived, Slack rejects the message and dlogify marks the delivery as failed. After 3 failed deliveries in a row the channel shows Failing. Rate limits and server errors are retried for up to about 22 hours (Notifications).