> For the complete documentation index, see [llms.txt](https://docs.ragnasync.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ragnasync.com/monitoring/server-monitoring/issues-notifications.md).

# Issues & Notifications

Get alerted when something affects your Discord bot or Ragnarok server

RagnaSync keeps an eye on your setup and tells you when something needs attention — a connection problem with your Discord bot, a spike of errors on your server, or you nearing your usage limit. You'll find these under **RagnaSync → Notifications** and **Ragnarok → Issues**.

***

## Notifications

The **Notifications** page is your inbox for anything affecting your Discord bot or Ragnarok client. The menu item carries a badge with your unread count — and it turns **red** when something critical is waiting.

* **Unread / Read filters** let you focus on what's new.
* **Mark as read** (one at a time, or all at once) clears items you've dealt with.

Typical notifications include usage warnings (80% / 95% / 100% of your limit — see [Usage & Billing](/account/usage-and-billing.md)), billing events, and connection or configuration problems.

***

## Your alerts channel in Discord

RagnaSync also posts its alerts straight into your Discord server, in a private **`#ragnasync-alerts`** channel that only your admins can see — usage warnings, your server going offline, message-delivery problems. It creates the channel for you the first time it has something to tell you, and if you delete it, it simply makes a new one the next time.

To create that channel the bot needs the **Manage Channels** permission. If you added the bot a while ago, it may not have it yet — just [re-add the bot with the install link](/getting-started/installation.md#add-the-ragnasync-discord-bot) and approve the permissions. Your settings stay exactly as they are.

Until the channel exists, RagnaSync sends those alerts to the **server owner by direct message** instead, so nothing is missed.

{% hint style="info" %}
Blocked DMs from server members? Then those direct messages can't reach you — granting **Manage Channels** is the reliable fix.
{% endhint %}

***

## Issues

When the [monitoring tool](/monitoring/server-monitoring.md) is running, RagnaSync turns recurring server problems into **Issues** under **Ragnarok → Issues** — each one a distinct problem it has detected, tracked over time rather than as a wall of repeated log lines.

An issue keeps a running **occurrence count** and a **priority**, so a problem that's happening more and more, or has been escalated to high priority, is easy to spot and act on. This is the actionable layer on top of your raw [Console Logs](/monitoring/server-monitoring/console-logs.md).

***

## Email alerts

Don't want to keep checking the dashboard? Turn on **email alerts** from the **Notifications** page (available once monitoring is configured). Alerts go to your **billing email address**, and you choose exactly what triggers one:

| Alert                          | Sends an email when…                                                                         |
| ------------------------------ | -------------------------------------------------------------------------------------------- |
| **New issue detected**         | A brand-new problem appears                                                                  |
| **Issue reopened**             | A previously-resolved issue comes back                                                       |
| **Occurrence spike**           | An issue's occurrence count crosses a threshold you set (and again at 10, 20, 50, 100, 500…) |
| **Priority escalated to High** | An issue is bumped up to high priority                                                       |

{% hint style="info" %}
Alert emails go to the address on your **Subscription** page. If you haven't set one, add it there first — otherwise there's nowhere to send them.
{% endhint %}

***

## Where it fits

Issues & Notifications is the alerting layer of [Server Monitoring](/monitoring/server-monitoring.md). It works alongside [Console Logs](/monitoring/server-monitoring/console-logs.md) (the raw errors and warnings) and [Crash Logs](/monitoring/server-monitoring/crash-logs.md) (full crash reports).