Monitoring & Alerts: Sleep While Your Positions Work
Telegram alerts for every scenario that matters: imbalance, liquidation proximity, negative funding, and regular summaries.
Delta-neutral positions don't need you watching them every minute. They do need something watching them. That's what the monitoring system does — and it talks to you via Telegram.
Once configured, monitoring runs as a background session, independent of your trading session. You can close the app, close your laptop, and go to sleep. If something needs your attention, you'll receive a message. If nothing fires, everything is fine.
This guide walks through setting up Telegram, configuring monitoring for a position, and understanding the alerts you'll receive.
Step 1: Set Up Telegram
Monitoring notifications are delivered via Telegram. To receive them, you need a Telegram bot that ArchiNeutral can use to message you directly. Creating one takes about two minutes.
Create a bot via @BotFather:
- Open Telegram and search for
@BotFather - Send
/newbotand follow the prompts — choose a name and a username for your bot - BotFather will reply with your bot token, a string that looks like
123456789:AAF... - To get your chat ID, search for
@userinfoboton Telegram, press Start — it replies with your ID. Copy it into the "Chat ID" field
Connect it to ArchiNeutral:
- Open ArchiNeutral settings and navigate to the Notifications section
- Paste your bot token and chat ID into the corresponding fields
- Click Send Test — ArchiNeutral will send a test message to your bot immediately
- Check Telegram. If you receive the message, the connection is working
Your bot token is encrypted after you save it. It is never stored in plaintext. The step-by-step instructions for finding your chat ID are also built into the UI, so you don't need to look them up separately.
Step 2: Configure Monitoring Per Position
Each active position has its own monitoring configuration. There is no global setting that applies to all positions at once — this is intentional. A position sized at $50,000 with a tight break-even warrants different thresholds than a smaller, more conservative one.
To configure monitoring for a position, open it in the Position Manager and navigate to the Monitoring tab.
Liquidation proximity
"Alert me when price gets within X% of my liquidation price."
This is your most important alert. If the price on either leg approaches the liquidation threshold, you need to know before it gets there — not after. Set this to 10-15% for meaningful early warning. At 10%, you receive the alert while you still have time to act: add margin, reduce size, or close the position deliberately rather than being forced out.
A critical alert fires for this. It will appear immediately. Do not ignore it.
SL/TP proximity
"Alert me when price approaches my stop-loss or take-profit."
If you have stop-loss or take-profit orders configured on a position, this alert tells you when price is getting close to triggering them. The purpose is to give you time to review the position before the order executes — if conditions have changed since you set the level, you may want to adjust it. If conditions are as expected, you can let it run.
Imbalance threshold
"Alert me when my two legs diverge by more than X%."
A delta-neutral position requires both legs to be approximately equal in size. If they diverge — because of a partial liquidation, a failed order, or a change made on the DEX directly outside of ArchiNeutral — the position is no longer neutral. It now has directional exposure.
Set this threshold to 5% for early detection. At 5% divergence, the position is drifting but not yet critical. You have time to assess and rebalance before the imbalance compounds. At 15%, you're exposed.
Funding rate threshold
"Alert me when net funding drops below X."
Set this to 0 to receive an alert whenever net funding turns negative. Negative funding means you are paying to hold the position rather than earning. For most delta-neutral strategies, negative funding is a signal to evaluate whether holding continues to make sense.
If you want to be more conservative, you can set the threshold above zero — for example, 0.005 — to receive an alert when funding drops below a minimum acceptable rate, even if it hasn't gone negative yet.
Summary interval
"Every X hours, send me a status update."
Options: off, 30 minutes, 1 hour, 4 hours, 12 hours, 24 hours.
A periodic summary sends a Telegram message with the current state of your position: size on each leg, current funding rate, net PnL, imbalance percentage, and proximity to liquidation. It is not an alert — nothing is wrong. It is a regular update so you can confirm things are running as expected.
For a position you're monitoring closely, 1-4 hours is a reasonable interval. For a stable position with conservative thresholds, 12 or 24 hours may be sufficient.
Alert cooldown
"Don't repeat the same alert more than once every X minutes."
If a condition persists — for example, funding stays negative for several hours — ArchiNeutral will not send you the same alert repeatedly every few minutes. The cooldown defines the minimum time between repeat alerts of the same type on the same position.
Set this based on how quickly you can realistically act. If you're monitoring actively, 15-30 minutes is reasonable. If you're asleep and will review in the morning, 120 minutes avoids filling your Telegram with duplicates overnight.
SL Safety Net delay
"If my stop-limit SL doesn't fill, force-close after X seconds."
This setting only applies if you chose stop-limit as your SL execution type in the SL/TP configurator. If you're using market stop-losses (the default), this has no effect.
When a stop-limit trigger price is breached but the limit order hasn't filled — because the market gapped through the limit price — monitoring detects this and starts a countdown. After the configured delay, it force-closes the position with a market order.
The default is 30 seconds (range: 5–300 seconds). On liquid markets with tight spreads, 15–30 seconds gives the limit order a fair chance to fill before the fallback kicks in. On less liquid DEXs or during high-volatility events, a shorter delay (5–10 seconds) reduces your exposure to extended unfilled orders.
Understanding Alert Types
Alerts are grouped by severity. When a message arrives in Telegram, its content and framing reflect how urgently it needs attention.
Critical alerts — act now
liq_proximity — Price is within your configured percentage of the liquidation price on one leg. You need to either add margin, reduce the position, or close it. This is not a warning to file away — at this proximity, the window to act is narrow.
dex_unreachable — ArchiNeutral attempted to reach a DEX three consecutive times and failed. This means the monitoring system cannot verify the current state of that leg. Check your internet connection, and check whether the DEX itself is experiencing an outage. If the DEX is unreachable during a volatile market, you cannot rely on your position data being current.
sl_safety_net — A stop-limit SL trigger price has been breached but the position is still open — the limit order did not fill. Monitoring is counting down to a force-close with a market order. This alert fires immediately when the breach is detected, giving you a window to intervene manually before the automatic force-close executes after the configured delay.
Warning alerts — review soon
imbalance — Your two legs have diverged beyond the configured threshold. The position has directional exposure. Rebalancing is needed. See the Managing Imbalances guide for how to respond.
sltp_proximity — Price is within your configured percentage of a stop-loss or take-profit level. Review the position and decide whether to let the order trigger or adjust the level.
funding_negative — Net funding has turned negative. You are now paying to hold the position. Evaluate whether the position remains viable at current funding rates or whether closing makes more sense.
Info alerts — awareness
funding_low — Funding has not turned negative but has dropped below your configured threshold. A heads-up that conditions are shifting.
periodic_summary — Your scheduled status update. No action required. This is confirmation that monitoring is running and the position is being tracked.
position_closed — Both legs of the position have reached zero. The position is fully closed. The system transitions the position status from Active to Closed.
position_imbalanced — The imbalance has reached a level where the system flags the position as Imbalanced in the UI. This is a status transition, not just a notification.
The Sleep Test
There is a simple way to evaluate whether your monitoring is configured correctly.
Ask yourself: "Can I go to sleep with this position open?"
If the answer is yes — your thresholds are set, Telegram is connected, the test message worked, and monitoring is running — then the system is doing its job. You've delegated the watching to ArchiNeutral. You'll be notified if anything changes.
If the answer is no, ask why. Usually it comes down to one of two things:
Thresholds feel too loose. If you're worried that something could go wrong without triggering an alert, tighten the thresholds. Lower the liquidation proximity percentage. Lower the imbalance threshold. Add a periodic summary. The configuration is yours to adjust.
The position itself carries risk you're not comfortable with overnight. No monitoring configuration can fix a position that's already too close to liquidation, or one where funding is already negative, or one where the spread has widened beyond what you expected. In that case, the right step is to address the position first — reduce size, add margin, or close — before relying on monitoring to hold the watch.
A properly monitored position with appropriate margins and sensible thresholds is one you can walk away from.
Alert History
Every alert ArchiNeutral sends is logged and viewable in the UI under the position's Monitoring tab.
The history lets you review what happened, when, and in what sequence. If an imbalance alert fired at 3am followed by a funding alert two hours later, you can see that sequence in the morning and understand how the position behaved overnight.
Alert history is also useful for calibrating your thresholds over time. If you're receiving too many alerts of a particular type, the history shows you how frequently that condition is occurring and how long it persists — which tells you whether the threshold needs to move or whether the position itself is consistently borderline.
What's Next
Monitoring is the system that tells you something is wrong. Knowing what to do when an imbalance alert fires is a separate skill. When your two legs diverge and you need to rebalance, see the Managing Imbalances guide.
This guide is part of the ArchiNeutral Guide Series.