You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/ai-sre/sessions.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,8 @@ Sessions are isolated from one another: context, bound team, and environment do
27
27
28
28
The left sidebar is the single entry point for sessions. Click **New Chat** to start a fresh session. The list is sorted by most recent activity in descending order; only the most recent entries are shown initially, and older history is revealed incrementally with **Show more**.
29
29
30
+
In a blank AI SRE session, four scenario suggestion cards appear above the composer: **Investigate an incident**, **Query data with natural language**, **Reduce alert noise**, and **Schedule an automated inspection**. Selecting a card only fills the composer; it does not send the prompt. You can edit it before pressing Enter.
31
+
30
32
### Search and Filter
31
33
32
34
<Steps>
@@ -100,7 +102,7 @@ Type a message in the input box at the bottom and press Enter to send. The input
100
102
Click the plus button at the lower left of the input box to choose files, or paste images directly. Supported formats include images, PDFs, text / Markdown / CSV, and Office documents (Word / Excel / PowerPoint), up to **20 MB** per file. A single message can carry at most **9 attachments**, and the total size of all attachments in one message cannot exceed **50 MB**; exceeding either limit shows a corresponding message. Screenshots can be pasted directly into the chat.
101
103
</Accordion>
102
104
<Accordiontitle="Context references"icon="link">
103
-
When you enter AI SRE from an incident, alert, monitor rule, or host page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, or host — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time.
105
+
When you enter AI SRE from an incident, alert, monitor rule, or host page, the related object is embedded into the input box as a **reference capsule** — a small inline tag indicating the kind of object referenced — an incident, alert event, alert, monitor rule, host, or on-call analytics — that travels with the message so the agent can start its analysis from that object directly. Click the capsule to open the referenced object in a new tab, or click its close button to remove the reference before sending. A single message can carry multiple references. Besides objects carried in automatically from a related page, you can also type `@` directly in any session's input box to trigger an incident search dropdown (supporting fuzzy keyword search and a list of recent incidents); selecting one inserts the same kind of reference capsule — a standalone entry point available at any time.
104
106
</Accordion>
105
107
<Accordiontitle="Knowledge and skills"icon="book">
106
108
When a session starts, the knowledge packs and skills for the bound team are loaded automatically. See <ahref="/en/ai-sre/knowledge">Knowledges</a> and <ahref="/en/ai-sre/skills">Skills</a> for details.
Other available subcommands: `change-delete`, `change-info`, `change-list`, `change-timeline-delete`, `change-timeline-update`, `change-update`, `component-upsert`, `component-delete`, `section-upsert`, `section-delete`, `info`, `subscriber-list`, `subscriber-import`, `subscriber-export`, `template-list`, `template-upsert`, `template-delete`.
222
222
223
-
### rum — RUM application management
223
+
### rum — RUM applications and session replay
224
224
225
-
Use these commands to manage RUM applications themselves, rather than querying individual RUM events. The current surface covers application detail, batch reads, listing, webhook testing, and create/update/delete operations.
225
+
Use these commands to manage RUM applications and export session replay data. The application commands cover detail, batch reads, listing, webhook testing, and create/update/delete operations.
226
226
227
227
```bash
228
228
flashduty rum application-info <application-id># Get one application's detail
@@ -260,6 +260,33 @@ Core fields for `application-create` / `application-update`:
260
260
`application-webhook-test` returns `ok`, `status_code`, and `message`, which makes it suitable for verifying that a RUM alert webhook really accepts a sample delivery from Flashduty.
261
261
</Note>
262
262
263
+
#### Session replay
264
+
265
+
```bash
266
+
flashduty rum session-replay-metadata <session-id># Get the application, device, session-boundary, and view metadata for a replayable session
267
+
flashduty rum session-replay-segments <session-id># Read session replay segments
268
+
```
269
+
270
+
For `session-replay-metadata`, use `--ts` to supply the session-start Unix timestamp in milliseconds when you need to disambiguate a reused session ID from different time windows.
271
+
272
+
Common `session-replay-segments` flags:
273
+
274
+
| Flag | Description |
275
+
|------|-------------|
276
+
|`--limit`| Number of segments to return, from 1 to 99; default: 20. |
277
+
|`--search-after-ctx`| Pagination cursor from the previous page. In URL mode, read `search_after_ctx`; in streaming mode, read the `X-Search-After-Ctx` response header. |
278
+
|`--ts`| Without `--search-after-ctx`, begin at the most recent full-snapshot segment at or before this timestamp. |
279
+
|`--url-mode`| When `true`, return JSON containing presigned download URLs. By default it is `false` and streams segment bytes directly. URLs are valid for one hour. |
280
+
|`--view-id`| Return segments for one view only; omit it to page through the whole session. |
281
+
282
+
### oncall — On-call licenses
283
+
284
+
```bash
285
+
flashduty oncall license-list # List people with active On-call licenses in the current account
286
+
```
287
+
288
+
This read-only command returns each person's ID, name, and license type: `fixed` is explicitly assigned, while `temporary` is active for the current temporary-license window.
Copy file name to clipboardExpand all lines: en/monitors/data-sources/data-sources.mdx
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,6 +106,28 @@ Self-signed certificate and TLS client authentication configurations are also su
106
106
107
107
These data sources have connection configurations similar to Prometheus, including server address, authentication, and TLS settings. The default server address for VictoriaLogs is `http://localhost:9428`. Refer to the creation form for specific parameters.
108
108
109
+
## Reference credentials locally in Edge
110
+
111
+
With Edge `v0.46.0` or later, you can use environment variable references in supported data-source connection fields instead of placing credentials directly in the data-source configuration. Edge resolves each reference in its local process; the resolved credential is never written back to the synced data-source configuration, debug output, or API payloads.
112
+
113
+
<Steps>
114
+
<Steptitle="Set environment variables for the Edge process">
115
+
Set credentials in the environment of every Edge process that queries this data source. For example, set `SLS_ACCESS_KEY_ID` and `SLS_ACCESS_KEY_SECRET` for SLS. Restart the Edge process after changing its environment so the new values take effect.
116
+
</Step>
117
+
<Steptitle="Enter references in the data-source form">
118
+
When editing a data source, enter `${env:VARIABLE_NAME}` in a supported authentication or connection field. For example, enter `${env:SLS_ACCESS_KEY_ID}` for the SLS **AccessKey ID** and `${env:SLS_ACCESS_KEY_SECRET}` for the **AccessKey Secret**.
119
+
</Step>
120
+
<Steptitle="Save and test">
121
+
Save the data source, then use **Test** to verify the connection. Each referenced variable must exist in the corresponding Edge process environment.
122
+
</Step>
123
+
</Steps>
124
+
125
+
Variable names must start with an uppercase letter or underscore and may then contain only uppercase letters, digits, or underscores, such as `SLS_ACCESS_KEY_SECRET`.
126
+
127
+
<Warning>
128
+
Environment variable references are not supported in the data-source **address**. They are also not supported in **Params** for Prometheus, Loki, or VictoriaLogs. Use this syntax only in supported authentication and connection fields.
129
+
</Warning>
130
+
109
131
## Test a data source
110
132
111
133
In the data source list, click the **Test** button for the corresponding data source to open a query preview window, verify the connection, and preview query results.
Copy file name to clipboardExpand all lines: en/monitors/targets/install-agent.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Prepare the following information before installation:
13
13
| Item | Description |
14
14
|---|---|
15
15
| Agent package download URL |`https://static.flashcat.cloud/monitagent/monitagent-v0.0.20-linux-amd64.tar.gz`. For ARM CPUs, replace `amd64` with `arm64`. |
16
-
| Edge address | For example, `ws://edge.example.com:6868` or `wss://edge.example.com:6868`. Edge version must be `>= v0.44.0`. View the Edge list and installation method [here](https://console.flashcat.cloud/monit/engine/list). |
16
+
| Edge address | For example, `ws://edge.example.com:6868` or `wss://edge.example.com:6868`. Edge version must be `>= v0.46.0`. View the Edge list and installation method [here](https://console.flashcat.cloud/monit/engine/list). |
17
17
| Local host object address | Use the current host's fixed private IP or DNS name, such as `10.0.1.12`. If omitted, the Agent uses the IP address associated with the local default route. |
18
18
| Read-only accounts for databases and middleware | To diagnose MySQL, Redis, PostgreSQL, MongoDB, Kafka, Elasticsearch, and other services, prepare read-only accounts and credentials in advance. |
Copy file name to clipboardExpand all lines: en/rum/explorer/data-query.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,10 @@ When you do not want to write DQL by hand, let AI turn a natural-language reques
42
42
Time expressions such as “last hour,” “yesterday,” and “past 7 days” update the Explorer time picker; they are not written as DQL conditions such as `client_time`. Performance-duration conditions remain DQL, for example `view_loading_time:>2s`.
43
43
</Note>
44
44
45
+
<Note>
46
+
AI natural-language queries support a maximum time range of **14 days**. If the requested range is longer, the preview indicates that it has been truncated to the most recent 14 days; after you apply it, the time picker uses that truncated range. A relative range becomes the past 14 days, while an absolute range keeps the requested end time and starts 14 days earlier.
0 commit comments