> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashduty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flashduty Monitors FAQ

> Monitors frequently asked questions

<AccordionGroup>
  <Accordion title="Alert rule execution is not as expected, how to debug?">
    On the alert rules list page, there is a **Debug Log Switch** that you can enable. Afterwards, the alert engine process `monitedge` will output detailed execution logs for that rule, making it easier to troubleshoot.

    `monitedge` outputs logs to standard output (`stdout`). The viewing method depends on the deployment method:

    | Deployment Method | View Logs Command                                                 |
    | ----------------- | ----------------------------------------------------------------- |
    | Docker            | `docker logs <container_id>`                                      |
    | Kubernetes        | `kubectl logs <pod_name>`                                         |
    | Linux (systemd)   | `journalctl -u monitedge.service -f` or check `/var/log/messages` |

    <Note>
      `monitedge` follows cloud-native best practices by outputting logs to standard output rather than writing to separate log files, making it convenient for log collection systems to collect, and facilitating rotation and compression.
    </Note>
  </Accordion>

  <Accordion title="What information does the overview dashboard display?">
    **Menu Entry**: Overview

    The overview page provides a global view of alert rules, consisting of the following cards:

    | Card                       | Description                                                                                                                                                                                                                   |
    | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | **Alert rule total trend** | An area chart showing how the total number of alert rules changes over time. The x-axis represents dates and the y-axis represents rule count, helping you track overall growth or reduction trends                           |
    | **Alert rules by channel** | A pie chart showing the distribution of alert rules across channels. The top 10 channels are displayed by default; the remainder are aggregated as "Others." You can click to expand and view all details                     |
    | **System event list**      | Displays system events generated by the alert engine (such as engine disconnection, configuration anomalies, etc.), with pagination and delete support, helping you promptly discover and address infrastructure-level issues |

    <Tip>
      The overview page checks whether you have installed an alert engine. If not, a prompt guides you to the alert engine page to complete installation.
    </Tip>
  </Accordion>

  <Accordion title="How do I quickly clone an alert rule?">
    On the alert rule edit or detail page, you can find the **Clone** action button. Clicking it creates a new rule based on the current rule's configuration, with all settings copied over (except the name), making it easy to quickly create similar alert rules.
  </Accordion>

  <Accordion title="How do I preview query results for an alert rule?">
    When creating or editing an alert rule, after configuring the query conditions, you can click the **Query Preview** button. The system immediately executes a query and displays the results, helping you verify whether the query expression is correct and whether the returned data meets expectations, without waiting for the next detection cycle.

    If the backend returns an unrecognized result format, the preview shows a hint that the frontend and backend versions may be out of sync and to contact the administrator. When debug arguments (debug JSON) for SLS / VictoriaLogs / Loki are invalid or contain nested structures, the preview aborts the query with an error ("Invalid JSON format" / "Nested structures are not supported") instead of silently ignoring them.
  </Accordion>

  <Accordion title="What format does the alert rule notes description support?">
    The notes description supports Markdown format. You can use headings, lists, links, code blocks, and other Markdown syntax to organize content. It also supports variable references, embedding dynamic information such as alert event label values and query results into the notes, making it convenient for responders to quickly understand the alert context.
  </Accordion>
</AccordionGroup>