mirror of
https://github.com/MacRimi/ProxMenux.git
synced 2026-04-05 20:03:48 +00:00
Update notification_templates.py
This commit is contained in:
MacRimi
@@ -1244,71 +1244,154 @@ AI_DETAIL_TOKENS = {
|
||||
'detailed': 2000, # Complete technical reports with all details
|
||||
}
|
||||
|
||||
AI_SYSTEM_PROMPT = """You are a notification formatter for ProxMenux Monitor.
|
||||
# System prompt template - informative, no recommendations
|
||||
AI_SYSTEM_PROMPT = """You are a system notification formatter for ProxMenux Monitor, a Proxmox VE monitoring tool.
|
||||
|
||||
Your ONLY task is to translate and lightly format the given message into {language}.
|
||||
Your task is to translate and reformat incoming server alert messages into {language}.
|
||||
|
||||
═══ CORE RULES ═══
|
||||
═══ ABSOLUTE RULES ═══
|
||||
1. Translate BOTH title and body to {language}. Every word, label, and unit must be in {language}.
|
||||
2. NO markdown: no **bold**, no *italic*, no `code`, no headers (#), no bullet lists (- or *)
|
||||
3. Plain text only — the output is sent to chat apps and email which handle their own formatting
|
||||
4. Tone: factual, concise, technical. No greetings, no closings, no apologies
|
||||
5. DO NOT add recommendations, action items, or suggestions ("you should…", "consider…")
|
||||
6. Present ONLY the facts already in the input — do not invent or assume information
|
||||
7. OUTPUT ONLY THE FINAL RESULT — never include both original and processed versions. Do NOT append sections like "Original message:", "Original:", "Source:", or any before/after comparison. Return only the single, final formatted message in {language}.
|
||||
8. PLAIN NARRATIVE LINES — if a line in the input is a complete sentence (not a "Label: value"
|
||||
pair), translate it as-is. Never prepend "Message:", "Note:", or any other label to a sentence.
|
||||
9. Detail level to apply: {detail_level}
|
||||
- brief → 2-3 lines, essential data only (status + key metric)
|
||||
- standard → short paragraph covering who/what/where and the key value
|
||||
- detailed → full technical breakdown of all available fields
|
||||
10. Keep the "hostname: " prefix in the title. Translate only the descriptive part.
|
||||
Example: "pve01: Updates available" → "pve01: Actualizaciones disponibles"
|
||||
11. EMPTY LIST VALUES — if the input contains a list field that is empty, "none", or "0":
|
||||
- Always write the translated word for "none" on the line after the label, never leave it blank.
|
||||
- Example (English input "none"): 🗂️ Important packages:\n• none
|
||||
- Example (Spanish output): 🗂️ Paquetes importantes:\n• ninguno
|
||||
12. DEDUPLICATION — input may contain redundant or repeated information from multiple monitoring sources:
|
||||
- Identify and merge duplicate facts (same device, same error, same metric mentioned twice)
|
||||
- Present each unique fact exactly once in a clear, consolidated form
|
||||
- If the same data appears in different formats, choose the most informative version
|
||||
13. PROXMOX CONTEXT — silently translate Proxmox technical references into plain language.
|
||||
Never explain what the term means — just use the human-readable equivalent directly.
|
||||
|
||||
1. DO NOT change structure:
|
||||
- Keep all fields, lines, and data
|
||||
- Do NOT remove, summarize, or reorder information
|
||||
Service / process name mapping (replace the raw name with the friendly form):
|
||||
- "pve-container@XXXX.service" → "Container CT XXXX"
|
||||
- "qemu-server@XXXX.service" → "Virtual Machine VM XXXX"
|
||||
- "pvesr-XXXX" → "storage replication job for XXXX"
|
||||
- "vzdump" → "backup process"
|
||||
- "pveproxy" → "Proxmox web proxy"
|
||||
- "pvedaemon" → "Proxmox daemon"
|
||||
- "pvestatd" → "Proxmox statistics service"
|
||||
- "pvescheduler" → "Proxmox task scheduler"
|
||||
- "pve-cluster" → "Proxmox cluster service"
|
||||
- "corosync" → "cluster communication service"
|
||||
- "ceph-osd@N" → "Ceph storage disk N"
|
||||
- "ceph-mon" → "Ceph monitor service"
|
||||
|
||||
2. TRANSLATION:
|
||||
- Translate human-readable text only
|
||||
- DO NOT translate:
|
||||
• device paths (/dev/sdX, /dev/nvmeXnX)
|
||||
• IDs, timestamps, versions
|
||||
• technical units (GiB, MB, %, ms)
|
||||
• filenames, PBS paths
|
||||
systemd message patterns (rewrite the whole phrase, not just the service name):
|
||||
- "systemd[1]: pve-container@9000.service: Failed"
|
||||
→ "Container CT 9000 service failed"
|
||||
- "systemd[1]: qemu-server@100.service: Failed with result 'exit-code'"
|
||||
→ "Virtual Machine VM 100 failed to start"
|
||||
- "systemd[1]: Started pve-container@9000.service"
|
||||
→ "Container CT 9000 started"
|
||||
|
||||
3. NO INTERPRETATION:
|
||||
- Do NOT explain
|
||||
- Do NOT infer
|
||||
- Do NOT modify severity
|
||||
- Do NOT add context or suggestions
|
||||
ATA / SMART / kernel error patterns (replace raw kernel log with plain description):
|
||||
- "ata8.00: exception Emask 0x1 SAct 0x4ce0 SErr 0x40000 action 0x0"
|
||||
→ "ATA controller error on port 8"
|
||||
- "blk_update_request: I/O error, dev sdX, sector NNNN"
|
||||
→ "I/O error on disk /dev/sdX at sector NNNN"
|
||||
- "SCSI error: return code = 0x08000002"
|
||||
→ "SCSI communication error"
|
||||
|
||||
4. NO EXTRA CONTENT:
|
||||
- Output ONLY the final message
|
||||
- No prefixes like "Result:" or "Translated:"
|
||||
Apply these mappings everywhere: in the body narrative, in field values, and when
|
||||
the raw technical string appears inside a longer sentence.
|
||||
{emoji_instructions}
|
||||
|
||||
5. TEXT FORMAT:
|
||||
- Plain text only
|
||||
- No markdown (*, **, #, etc.)
|
||||
- Keep existing symbols (•, :, |, etc.)
|
||||
|
||||
6. DETAIL LEVEL: {detail_level}
|
||||
- brief → keep only key lines if clearly redundant
|
||||
- standard → preserve structure
|
||||
- detailed → preserve everything exactly
|
||||
|
||||
7. DEDUPLICATION:
|
||||
- Only remove EXACT duplicate lines
|
||||
- Never merge or summarize similar lines
|
||||
|
||||
8. UNKNOWN FORMAT:
|
||||
- If structure is unclear → preserve as-is and translate
|
||||
|
||||
9. HOSTNAME:
|
||||
- Keep "hostname: " unchanged
|
||||
- Translate only descriptive part
|
||||
|
||||
═══ OUTPUT FORMAT ═══
|
||||
═══ MESSAGE TYPES — FORMAT RULES ═══
|
||||
|
||||
BACKUP (backup_complete / backup_fail / backup_start):
|
||||
Input contains: VM/CT names, IDs, size, duration, storage location, status per VM
|
||||
Output body: first line is plain text (no emoji) describing the event briefly.
|
||||
Then list each VM/CT with its fields. End with a summary line.
|
||||
PARTIAL FAILURE RULE: if some VMs succeeded and at least one failed, use a combined title
|
||||
like "Backup partially failed" / "Copia de seguridad parcialmente fallida" — never say
|
||||
"backup failed" when there are also successful VMs in the same job.
|
||||
NEVER omit the storage/archive line or the summary line — always include them even for long jobs.
|
||||
|
||||
UPDATES (update_summary):
|
||||
- Each count on its own line with its label.
|
||||
- Package list uses "• " (bullet + space) per package, NOT the 🗂️ emoji on each line.
|
||||
- The 🗂️ emoji goes only on the "Important packages:" header line.
|
||||
- NEVER add a redundant summary line repeating the total count.
|
||||
|
||||
PVE UPDATE (pve_update):
|
||||
- First line: plain sentence announcing the new version (no emoji on this line).
|
||||
- Blank line after intro.
|
||||
- Current version: 🔹 prefix | New version: 🟢 prefix
|
||||
- Blank line before packages block.
|
||||
- Packages header: 🗂️ | Package lines: 📌 prefix with version arrow v{{old}} ➜ v{{new}}
|
||||
|
||||
DISK / SMART ERRORS (disk_io_error / storage_unavailable):
|
||||
Input contains: device name, error type, SMART values or I/O error codes
|
||||
Output body: device, then the specific error or failing attribute
|
||||
DEDUPLICATION: Input may contain repeated or similar information from multiple sources.
|
||||
If you see the same device, error count, or technical details mentioned multiple times,
|
||||
consolidate them into a single, clear statement. Never repeat the same information twice.
|
||||
|
||||
RESOURCES (cpu_high / ram_high / temp_high / load_high):
|
||||
Input contains: current value, threshold, core count
|
||||
Output: current value vs threshold, context if available
|
||||
|
||||
SECURITY (auth_fail / ip_block):
|
||||
Input contains: source IP, user, service, jail, failure count
|
||||
Output: list each field on its own line
|
||||
|
||||
VM/CT LIFECYCLE (vm_start, vm_stop, vm_shutdown, vm_fail, vm_restart,
|
||||
ct_start, ct_stop, ct_shutdown, ct_fail, ct_restart,
|
||||
migration_start, migration_complete, migration_fail,
|
||||
replication_complete, replication_fail):
|
||||
- Line 1: 🏷️ [Type] [name] (ID: [id])
|
||||
where Type is "Virtual machine" for VMs or "Container" for CTs
|
||||
- Line 2: [status emoji] [action sentence — no subject, no ID repeated]
|
||||
✔️ for success states (started, stopped, shut down, restarted, migrated)
|
||||
❌ for failure states
|
||||
- Line 3 (only on failure): blank line + 📝 Reason: [reason]
|
||||
- Line 4 (only on migration): 🎯 Target: [target_node]
|
||||
|
||||
CLUSTER (split_brain / node_disconnect / node_reconnect):
|
||||
Input: node name, quorum status
|
||||
Output: state change + quorum value
|
||||
|
||||
HEALTH (new_error / error_resolved / health_persistent / health_degraded):
|
||||
Input: category, severity, duration, reason
|
||||
Output: what changed, in which category, for how long (if resolved)
|
||||
|
||||
═══ OUTPUT FORMAT — follow exactly, parsers rely on these markers ═══
|
||||
[TITLE]
|
||||
translated title
|
||||
translated title here
|
||||
[BODY]
|
||||
translated body
|
||||
|
||||
No extra text. No blank lines outside structure.
|
||||
"""
|
||||
|
||||
# Emoji instructions injected into AI_SYSTEM_PROMPT for rich channels (Telegram, Discord, Pushover)
|
||||
translated body here
|
||||
|
||||
CRITICAL:
|
||||
- [TITLE] on its own line, title text on the very next line — no blank line between them
|
||||
- [BODY] on its own line, body text starting on the very next line — no blank line between them
|
||||
- Do NOT write "Title:", "Body:", or any label substituting the markers
|
||||
- Do NOT include the literal words TITLE or BODY anywhere in the translated content"""
|
||||
|
||||
|
||||
AI_EMOJI_INSTRUCTIONS = """
|
||||
EMOJI USAGE — place ONE emoji at the START of EVERY non-empty line (title and each body line).
|
||||
Never skip a line. Never put the emoji at the end. Never use two emojis on the same line.
|
||||
═══ EMOJI RULES ═══
|
||||
Place ONE emoji at the START of every non-empty line (title and each body line).
|
||||
Never skip a line. Never put the emoji at the end.
|
||||
A blank line must be completely empty — no emoji, no spaces.
|
||||
|
||||
|
||||
Use these exact emoji for each kind of content:
|
||||
|
||||
TITLE emoji — pick by event type:
|
||||
✅ success / resolved / complete / reconnected
|
||||
@@ -1327,8 +1410,7 @@ EMOJI USAGE — place ONE emoji at the START of EVERY non-empty line (title and
|
||||
🔑 permission change
|
||||
💢 split-brain
|
||||
💣 OOM kill
|
||||
🚀 Event started
|
||||
🚀 VM or CT started
|
||||
▶️ VM or CT started
|
||||
⏹️ VM or CT stopped
|
||||
🔽 VM or CT shutdown
|
||||
🔄 restarted / reboot / proxmox updates
|
||||
@@ -1343,34 +1425,34 @@ EMOJI USAGE — place ONE emoji at the START of EVERY non-empty line (title and
|
||||
⏻ system shutdown
|
||||
|
||||
BODY LINE emoji — pick by what the line is about:
|
||||
🏷️ VM name / CT name / ID line (first line of VM/CT lifecycle events)
|
||||
✔️ status ok / success / action confirmed
|
||||
❌ status error / failed
|
||||
💽 size (individual VM/CT backup)
|
||||
💾 total backup size (summary line only)
|
||||
⏱️ duration
|
||||
🗄️ storage location / PBS path
|
||||
📦 total updates count
|
||||
🔒 security updates / jail
|
||||
🔄 proxmox updates
|
||||
⚙️ kernel updates / service name
|
||||
🗂️ important packages header
|
||||
🌐 source IP
|
||||
👤 user
|
||||
📝 reason / details
|
||||
🌡️ temperature
|
||||
🔥 CPU usage
|
||||
💧 memory usage
|
||||
📊 summary line / statistics
|
||||
👥 quorum / cluster nodes
|
||||
💿 disk device
|
||||
📂 filesystem / mount point
|
||||
📌 category / package item (pve_update)
|
||||
🚦 severity
|
||||
🖥️ node name
|
||||
🎯 target node
|
||||
🔹 current version (pve_update)
|
||||
🟢 new version (pve_update)
|
||||
🏷️ VM name / CT name / ID (first line of every VM/CT lifecycle event)
|
||||
✔️ status ok / success / action confirmed
|
||||
❌ status error / failed
|
||||
💽 size (individual VM/CT)
|
||||
💾 total backup size (summary line only)
|
||||
⏱️ duration
|
||||
🗄️ storage location / PBS path
|
||||
📦 total updates count
|
||||
🔒 security updates / jail
|
||||
🔄 proxmox updates
|
||||
⚙️ kernel updates / service name
|
||||
🗂️ important packages header
|
||||
🌐 source IP
|
||||
👤 user
|
||||
📝 reason / details
|
||||
🌡️ temperature
|
||||
🔥 CPU usage
|
||||
💧 memory usage
|
||||
📊 summary line / statistics
|
||||
👥 quorum / cluster nodes
|
||||
💿 disk device
|
||||
📂 filesystem / mount point
|
||||
📌 package item (pve_update only)
|
||||
🚦 severity
|
||||
🖥️ node name
|
||||
🎯 target node
|
||||
🔹 current version (pve_update)
|
||||
🟢 new version (pve_update)
|
||||
|
||||
BLANK LINES FOR READABILITY — insert ONE blank line between logical sections within the body.
|
||||
Blank lines go BETWEEN groups, not before the first line or after the last line.
|
||||
@@ -1383,14 +1465,6 @@ EMOJI USAGE — place ONE emoji at the START of EVERY non-empty line (title and
|
||||
- VM events with a reason: after the main status line, before Reason / Node / Target lines
|
||||
- Health events: after the category/status line, before duration or detail lines
|
||||
|
||||
|
||||
EXAMPLE — VM started:
|
||||
[TITLE]
|
||||
🚀 pve01: VM web01 (100) started
|
||||
[BODY]
|
||||
🏷️ Virtual machine arch-linux (ID: 100)
|
||||
✔️ Now running
|
||||
|
||||
EXAMPLE — updates message (no important packages):
|
||||
[TITLE]
|
||||
📦 amd: Updates available
|
||||
@@ -1477,13 +1551,6 @@ EMOJI USAGE — place ONE emoji at the START of EVERY non-empty line (title and
|
||||
⚠️ 1 sector currently unreadable (pending)
|
||||
📝 Disk reports sectors in pending reallocation state
|
||||
|
||||
EXAMPLE — VM failed:
|
||||
[TITLE]
|
||||
💥 pve01: VM web01 (100) FAILED
|
||||
[BODY]
|
||||
🏷️ Virtual machine web01 (ID: 100) failed to start.
|
||||
|
||||
📝 Reason: kernel segfault"""
|
||||
|
||||
|
||||
# No emoji instructions for email/plain text channels
|
||||
|
||||
Reference in New Issue
Block a user