feat:增加日志导出功能

[lmccyf]

日志模块新增导出日志为 CSV 文件的功能，覆盖前后端全链路：

后端：新增两个 POST 接口，接收筛选条件 JSON，查询数据库后直接以 CSV 流响应，最大导出 10000 条防止内存溢出。

前端：在日志列表页操作栏新增「导出 CSV」按钮，携带当前所有筛选条件（时间、模型、令牌、渠道、分组、Request ID、日志类型等）发起请求，Blob 流触发浏览器下载，含 Loading 状态、成功提示、空数据提示和错误提示。

相关议题：#1778

Summary by CodeRabbit

Release Notes

• New Features
  • CSV export functionality for logs now available with customizable filtering; admins can export all logs and users can export their own
  • New "Export CSV" button added to the logs interface for convenient access
  • Comprehensive multi-language support added for all export features and related messages

[coderabbitai]

Walkthrough

Adds CSV export functionality for usage logs across backend and frontend. Introduces new export endpoints in the API layer, corresponding data retrieval functions in the model layer, and integrates export UI controls and download logic in the frontend, along with supporting translations across multiple language locales.

Changes

Cohort / File(s)	Summary
Backend Export API controller/log.go, router/api-router.go	Adds ExportLogsRequest struct and two export handlers (ExportAllLogs, ExportUserLogs) with CSV streaming via writeLogCSV. Routes /api/log/export (admin) and /api/log/self/export (user) added.
Backend Data Retrieval model/log.go	Introduces GetAllLogsForExport and GetUserLogsForExport functions with optional filtering (logType, timestamps, modelName, username, tokenName, channel, group, requestId) and a maxExportCount constant (10,000 limit).
Frontend Export UI web/src/components/table/usage-logs/UsageLogsFilters.jsx	Adds exportLoading and exportLogs props to LogsFilters component; new "导出 CSV" button with download icon.
Frontend Export Logic web/src/hooks/usage-logs/useUsageLogsData.jsx	Introduces exportLoading state and exportLogs function; handles request building, blob/JSON response detection, browser download triggering, and success/error messaging.
Internationalization web/src/i18n/locales/*	Adds two translation keys across all locale files (en, fr, ja, ru, vi, zh-CN, zh-TW, zh): "导出 CSV" (export button label) and "暂无数据，无法导出" (no data message). Chinese locale (zh.json) also adds "导出日志失败" and "日志导出成功".

Sequence Diagram(s)

sequenceDiagram
    participant Browser as Browser / Client
    participant UI as Frontend Component
    participant Hook as useUsageLogsData Hook
    participant API as Backend API
    participant Model as Model Layer
    participant DB as Database

    Browser->>UI: Click "Export CSV" button
    UI->>Hook: Call exportLogs()
    Hook->>Hook: Collect form values & build request body
    alt Admin Export Path
        Hook->>API: POST /api/log/export (admin context)
    else User Export Path
        Hook->>API: POST /api/log/self/export (user context)
    end
    
    API->>Model: GetAllLogsForExport() or GetUserLogsForExport()
    Model->>DB: Query logs with filters (logType, timestamps, etc.)
    DB-->>Model: Return log records
    Model->>Model: Format logs & cap at maxExportCount
    Model-->>API: Return filtered log slice
    
    alt Logs Found
        API->>API: writeLogCSV() - build CSV with BOM & headers
        API-->>Hook: Return CSV blob (Content-Type: text/csv)
    else No Logs
        API-->>Hook: Return JSON error (Content-Type: application/json)
    end
    
    Hook->>Hook: Detect response Content-Type
    alt CSV Blob
        Hook->>Browser: Trigger download via blob URL
        Browser->>Browser: Save CSV file
        Hook->>Browser: Revoke blob URL
        Hook->>UI: Display success message
    else JSON Error
        Hook->>UI: Parse & display error message
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fix(i18n): fill missing translations in i18n. #2314: Both PRs modify the same i18n locale files (web/src/i18n/locales/*) by adding or updating translation key entries.

Poem

🐰 Nibbling on CSV dreams so sweet,
Logs exported, complete and neat!
With filters fine and downloads bright,
Export CSV makes users' day right! 🐇✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 62.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat:增加日志导出功能' (Add log export feature) directly and clearly summarizes the main change - introduction of CSV export functionality for logs across backend and frontend.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 5

🧹 Nitpick comments (2)

model/log.go (1)

386-388: Align modelName filtering behavior with user export path.

Line 387 uses raw LIKE ?, while GetUserLogsForExport escapes user input. This can make admin export results inconsistent with user export/search semantics when %/_ appear.

🔧 Suggested refactor

-	if modelName != "" {
-		tx = tx.Where("logs.model_name like ?", modelName)
-	}
+	if modelName != "" {
+		modelNamePattern, err := sanitizeLikePattern(modelName)
+		if err != nil {
+			return nil, err
+		}
+		tx = tx.Where("logs.model_name LIKE ? ESCAPE '!'", modelNamePattern)
+	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@model/log.go` around lines 386 - 388, The modelName filter uses a raw LIKE
which differs from the escaped semantics in GetUserLogsForExport; update the
filter in the code that sets tx (when modelName != "") to apply the same
escaping and pattern construction used by GetUserLogsForExport (e.g., call the
same EscapeLike helper or escape '%' and '_' then surround with '%' as that
function does) and pass the escaped pattern into tx.Where (and include the same
ESCAPE clause if used) so admin exports/searches behave identically to user
exports.

web/src/i18n/locales/fr.json (1)

1103-1103: Prefer more natural French wording for the export label.

Line 1103 would read more idiomatically as Exporter en CSV.

💡 Suggested wording tweak

-    "导出 CSV": "Exporter CSV",
+    "导出 CSV": "Exporter en CSV",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/i18n/locales/fr.json` at line 1103, The French translation for the
key "导出 CSV" is slightly unnatural; update its value in the fr.json locale so
the pair reads "导出 CSV": "Exporter en CSV" (replace "Exporter CSV" with
"Exporter en CSV") to match idiomatic French.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@controller/log.go`:
- Around line 253-289: The CSV writer calls are currently ignoring errors;
update the export logic around w := csv.NewWriter(c.Writer) and each
w.Write(...) plus w.Flush() to check returned errors (from w.Write and after
w.Flush via w.Error() or the returned error), handle them by logging the error
and terminating the loop/returning an appropriate HTTP error or aborting the
response to avoid producing incomplete CSVs; ensure you handle the initial
c.Writer.Write(BOM) error as well and use the unique identifiers log loop,
w.Write calls, w.Flush(), and c.Writer to locate and implement these checks.
- Around line 264-285: The CSV export writes untrusted text fields directly (in
the loop calling w.Write) which can trigger Excel formula injection; add a
helper function sanitizeCSVCell(s string) string that returns the original s
unless it begins with one of the dangerous prefixes ('=', '+', '-', '@'), in
which case it returns a safe-prefixed value (e.g., prepend a single quote) and
then call sanitizeCSVCell on all user-controlled fields used in the Write
call—specifically Username, TokenName, ModelName, ChannelName, Group, Ip,
RequestId, and Content—so those values are sanitized before being passed to
w.Write.

In `@model/log.go`:
- Around line 379-413: GetAllLogsForExport currently fetches logs without
loading ChannelName, so exported CSV shows an empty "渠道名称"; modify
GetAllLogsForExport to include the channel name by joining or preloading the
channel data: either add a LEFT JOIN on the channels table and select
channels.name AS channel_name (or the correct column) so GORM scans it into
Log.ChannelName, or Preload("Channel") and after Find iterate logs to set
Log.ChannelName = log.Channel.Name; update the tx query (in GetAllLogsForExport)
to include this join/select or the Preload call and ensure the selected alias
matches the Log.ChannelName field.

In `@web/src/hooks/usage-logs/useUsageLogsData.jsx`:
- Around line 779-781: The catch block in useUsageLogsData.jsx currently
replaces the caught error with a generic t('导出日志失败') string (catch (err) {
showError(t('导出日志失败')); }), losing structured error information; change the
catch to pass the original error to showError (e.g., showError(err)) or at
minimum include err details (showError(err?.message || t('导出日志失败'))) so
status-based handling and backend-provided details are preserved; update the
catch in the export-related function where showError and t are used.

In `@web/src/i18n/locales/vi.json`:
- Around line 1095-1097: The translation for export-related keys contains
English text; update the i18n entries "导出日志失败" (currently "Failed to export
logs") and the other export keys at the same group (also referenced around lines
with keys for exporting at 1540-1541) to complete Vietnamese translations so the
export flow shows consistent Vietnamese copy; locate the keys "导出 CSV",
"导出日志失败", and "导出配置" in vi.json and replace the English value(s) with
appropriate Vietnamese strings (e.g., "导出日志失败" -> "Xuất nhật ký thất bại")
ensuring all export-related keys in that file are translated.

---

Nitpick comments:
In `@model/log.go`:
- Around line 386-388: The modelName filter uses a raw LIKE which differs from
the escaped semantics in GetUserLogsForExport; update the filter in the code
that sets tx (when modelName != "") to apply the same escaping and pattern
construction used by GetUserLogsForExport (e.g., call the same EscapeLike helper
or escape '%' and '_' then surround with '%' as that function does) and pass the
escaped pattern into tx.Where (and include the same ESCAPE clause if used) so
admin exports/searches behave identically to user exports.

In `@web/src/i18n/locales/fr.json`:
- Line 1103: The French translation for the key "导出 CSV" is slightly unnatural;
update its value in the fr.json locale so the pair reads "导出 CSV": "Exporter en
CSV" (replace "Exporter CSV" with "Exporter en CSV") to match idiomatic French.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ae1c8e4 and e185184.

📒 Files selected for processing (13)

• controller/log.go
• model/log.go
• router/api-router.go
• web/src/components/table/usage-logs/UsageLogsFilters.jsx
• web/src/hooks/usage-logs/useUsageLogsData.jsx
• web/src/i18n/locales/en.json
• web/src/i18n/locales/fr.json
• web/src/i18n/locales/ja.json
• web/src/i18n/locales/ru.json
• web/src/i18n/locales/vi.json
• web/src/i18n/locales/zh-CN.json
• web/src/i18n/locales/zh-TW.json
• web/src/i18n/locales/zh.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Handle CSV write errors instead of discarding them.

Lines 253, 262, 265, and 288 currently ignore write/flush errors, which can silently produce incomplete downloads on client disconnect or stream failures.

🔍 Suggested fix

-	_, _ = c.Writer.Write([]byte{0xEF, 0xBB, 0xBF})
+	if _, err := c.Writer.Write([]byte{0xEF, 0xBB, 0xBF}); err != nil {
+		_ = c.Error(err)
+		return
+	}
@@
-	_ = w.Write(headers)
+	if err := w.Write(headers); err != nil {
+		_ = c.Error(err)
+		return
+	}
@@
-		_ = w.Write([]string{
+		if err := w.Write([]string{
 			...
-		})
+		}); err != nil {
+			_ = c.Error(err)
+			return
+		}
 	}
 
 	w.Flush()
+	if err := w.Error(); err != nil {
+		_ = c.Error(err)
+	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@controller/log.go` around lines 253 - 289, The CSV writer calls are currently
ignoring errors; update the export logic around w := csv.NewWriter(c.Writer) and
each w.Write(...) plus w.Flush() to check returned errors (from w.Write and
after w.Flush via w.Error() or the returned error), handle them by logging the
error and terminating the loop/returning an appropriate HTTP error or aborting
the response to avoid producing incomplete CSVs; ensure you handle the initial
c.Writer.Write(BOM) error as well and use the unique identifiers log loop,
w.Write calls, w.Flush(), and c.Writer to locate and implement these checks.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Prevent CSV formula injection in exported fields.

Lines 271-285 write untrusted text cells directly. If a value starts with =, +, -, or @, opening the CSV in Excel-like tools can execute formulas.

🛡️ Suggested fix

 func writeLogCSV(c *gin.Context, logs []*model.Log) {
@@
 	for _, log := range logs {
 		_ = w.Write([]string{
 			strconv.Itoa(log.Id),
@@
-			log.Username,
-			log.TokenName,
-			log.ModelName,
+			sanitizeCSVCell(log.Username),
+			sanitizeCSVCell(log.TokenName),
+			sanitizeCSVCell(log.ModelName),
@@
-			log.ChannelName,
-			log.Group,
-			log.Ip,
-			log.RequestId,
-			log.Content,
+			sanitizeCSVCell(log.ChannelName),
+			sanitizeCSVCell(log.Group),
+			sanitizeCSVCell(log.Ip),
+			sanitizeCSVCell(log.RequestId),
+			sanitizeCSVCell(log.Content),
 		})
 	}
@@
 }
+
+func sanitizeCSVCell(v string) string {
+	if v == "" {
+		return v
+	}
+	switch v[0] {
+	case '=', '+', '-', '@':
+		return "'" + v
+	default:
+		return v
+	}
+}

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	for _, log := range logs {
	_ = w.Write([]string{
	strconv.Itoa(log.Id),
	// Leading tab forces Excel to treat this cell as text, preventing
	// the datetime auto-detection that causes "####" in narrow columns.
	"\t" + time.Unix(log.CreatedAt, 0).Format("2006-01-02 15:04:05"),
	strconv.Itoa(log.Type),
	log.Username,
	log.TokenName,
	log.ModelName,
	strconv.Itoa(log.PromptTokens),
	strconv.Itoa(log.CompletionTokens),
	strconv.Itoa(log.Quota),
	strconv.Itoa(log.UseTime),
	strconv.FormatBool(log.IsStream),
	strconv.Itoa(log.ChannelId),
	log.ChannelName,
	log.Group,
	log.Ip,
	log.RequestId,
	log.Content,
	})
	for _, log := range logs {
	_ = w.Write([]string{
	strconv.Itoa(log.Id),
	// Leading tab forces Excel to treat this cell as text, preventing
	// the datetime auto-detection that causes "####" in narrow columns.
	"\t" + time.Unix(log.CreatedAt, 0).Format("2006-01-02 15:04:05"),
	strconv.Itoa(log.Type),
	sanitizeCSVCell(log.Username),
	sanitizeCSVCell(log.TokenName),
	sanitizeCSVCell(log.ModelName),
	strconv.Itoa(log.PromptTokens),
	strconv.Itoa(log.CompletionTokens),
	strconv.Itoa(log.Quota),
	strconv.Itoa(log.UseTime),
	strconv.FormatBool(log.IsStream),
	strconv.Itoa(log.ChannelId),
	sanitizeCSVCell(log.ChannelName),
	sanitizeCSVCell(log.Group),
	sanitizeCSVCell(log.Ip),
	sanitizeCSVCell(log.RequestId),
	sanitizeCSVCell(log.Content),
	})
	}
	}
	func sanitizeCSVCell(v string) string {
	if v == "" {
	return v
	}
	switch v[0] {
	case '=', '+', '-', '@':
	return "'" + v
	default:
	return v
	}
	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@controller/log.go` around lines 264 - 285, The CSV export writes untrusted
text fields directly (in the loop calling w.Write) which can trigger Excel
formula injection; add a helper function sanitizeCSVCell(s string) string that
returns the original s unless it begins with one of the dangerous prefixes ('=',
'+', '-', '@'), in which case it returns a safe-prefixed value (e.g., prepend a
single quote) and then call sanitizeCSVCell on all user-controlled fields used
in the Write call—specifically Username, TokenName, ModelName, ChannelName,
Group, Ip, RequestId, and Content—so those values are sanitized before being
passed to w.Write.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

ChannelName will be empty in admin CSV export output.

writeLogCSV outputs a "渠道名称" column, but GetAllLogsForExport (Lines 379-413) does not populate Log.ChannelName. This makes exported data incomplete.

💡 Suggested fix

 func GetAllLogsForExport(logType int, startTimestamp int64, endTimestamp int64, modelName string, username string, tokenName string, channel int, group string, requestId string) ([]*Log, error) {
 	var tx *gorm.DB
@@
 	var logs []*Log
-	err := tx.Order("logs.id desc").Limit(maxExportCount).Find(&logs).Error
+	err := tx.
+		Select("logs.*, channels.name AS channel_name").
+		Joins("LEFT JOIN channels ON channels.id = logs.channel_id").
+		Order("logs.id desc").
+		Limit(maxExportCount).
+		Find(&logs).Error
 	return logs, err
 }

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	func GetAllLogsForExport(logType int, startTimestamp int64, endTimestamp int64, modelName string, username string, tokenName string, channel int, group string, requestId string) ([]*Log, error) {
	var tx *gorm.DB
	if logType == LogTypeUnknown {
	tx = LOG_DB
	} else {
	tx = LOG_DB.Where("logs.type = ?", logType)
	}
	if modelName != "" {
	tx = tx.Where("logs.model_name like ?", modelName)
	}
	if username != "" {
	tx = tx.Where("logs.username = ?", username)
	}
	if tokenName != "" {
	tx = tx.Where("logs.token_name = ?", tokenName)
	}
	if requestId != "" {
	tx = tx.Where("logs.request_id = ?", requestId)
	}
	if startTimestamp != 0 {
	tx = tx.Where("logs.created_at >= ?", startTimestamp)
	}
	if endTimestamp != 0 {
	tx = tx.Where("logs.created_at <= ?", endTimestamp)
	}
	if channel != 0 {
	tx = tx.Where("logs.channel_id = ?", channel)
	}
	if group != "" {
	tx = tx.Where("logs."+logGroupCol+" = ?", group)
	}
	var logs []*Log
	err := tx.Order("logs.id desc").Limit(maxExportCount).Find(&logs).Error
	return logs, err
	func GetAllLogsForExport(logType int, startTimestamp int64, endTimestamp int64, modelName string, username string, tokenName string, channel int, group string, requestId string) ([]*Log, error) {
	var tx *gorm.DB
	if logType == LogTypeUnknown {
	tx = LOG_DB
	} else {
	tx = LOG_DB.Where("logs.type = ?", logType)
	}
	if modelName != "" {
	tx = tx.Where("logs.model_name like ?", modelName)
	}
	if username != "" {
	tx = tx.Where("logs.username = ?", username)
	}
	if tokenName != "" {
	tx = tx.Where("logs.token_name = ?", tokenName)
	}
	if requestId != "" {
	tx = tx.Where("logs.request_id = ?", requestId)
	}
	if startTimestamp != 0 {
	tx = tx.Where("logs.created_at >= ?", startTimestamp)
	}
	if endTimestamp != 0 {
	tx = tx.Where("logs.created_at <= ?", endTimestamp)
	}
	if channel != 0 {
	tx = tx.Where("logs.channel_id = ?", channel)
	}
	if group != "" {
	tx = tx.Where("logs."+logGroupCol+" = ?", group)
	}
	var logs []*Log
	err := tx.
	Select("logs.*, channels.name AS channel_name").
	Joins("LEFT JOIN channels ON channels.id = logs.channel_id").
	Order("logs.id desc").
	Limit(maxExportCount).
	Find(&logs).Error
	return logs, err
	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@model/log.go` around lines 379 - 413, GetAllLogsForExport currently fetches
logs without loading ChannelName, so exported CSV shows an empty "渠道名称"; modify
GetAllLogsForExport to include the channel name by joining or preloading the
channel data: either add a LEFT JOIN on the channels table and select
channels.name AS channel_name (or the correct column) so GORM scans it into
Log.ChannelName, or Preload("Channel") and after Find iterate logs to set
Log.ChannelName = log.Channel.Name; update the tx query (in GetAllLogsForExport)
to include this join/select or the Preload call and ensure the selected alias
matches the Log.ChannelName field.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Do not collapse export failures to a generic string.

At Line 780, replacing the caught error with t('导出日志失败') drops existing structured error behavior (including status-based handling) and backend-provided details.

🛠️ Suggested fix

-    } catch (err) {
-      showError(t('导出日志失败'));
+    } catch (err) {
+      const blob = err?.response?.data;
+      if (blob instanceof Blob && blob.type?.includes('application/json')) {
+        try {
+          const text = await blob.text();
+          const json = JSON.parse(text);
+          showError(json.message || t('导出日志失败'));
+          return;
+        } catch (_) {
+          // ignore parse error
+        }
+      }
+      showError(err);
     } finally {
       setExportLoading(false);
     }

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	} catch (err) {
	showError(t('导出日志失败'));
	} finally {
	} catch (err) {
	const blob = err?.response?.data;
	if (blob instanceof Blob && blob.type?.includes('application/json')) {
	try {
	const text = await blob.text();
	const json = JSON.parse(text);
	showError(json.message || t('导出日志失败'));
	return;
	} catch (_) {
	// ignore parse error
	}
	}
	showError(err);
	} finally {
	setExportLoading(false);
	}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/hooks/usage-logs/useUsageLogsData.jsx` around lines 779 - 781, The
catch block in useUsageLogsData.jsx currently replaces the caught error with a
generic t('导出日志失败') string (catch (err) { showError(t('导出日志失败')); }), losing
structured error information; change the catch to pass the original error to
showError (e.g., showError(err)) or at minimum include err details
(showError(err?.message || t('导出日志失败'))) so status-based handling and
backend-provided details are preserved; update the catch in the export-related
function where showError and t are used.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

vi 导出提示存在中英混用，建议补齐越南语文案。

Line 1096 和 Line 1540 仍是英文，会导致导出流程提示在越南语界面下出现混合语言。

🌐 Suggested i18n fix

-    "导出日志失败": "Failed to export logs",
+    "导出日志失败": "Xuất nhật ký thất bại",
...
-    "日志导出成功": "Logs exported successfully",
+    "日志导出成功": "Xuất nhật ký thành công",

Also applies to: 1540-1541

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@web/src/i18n/locales/vi.json` around lines 1095 - 1097, The translation for
export-related keys contains English text; update the i18n entries "导出日志失败"
(currently "Failed to export logs") and the other export keys at the same group
(also referenced around lines with keys for exporting at 1540-1541) to complete
Vietnamese translations so the export flow shows consistent Vietnamese copy;
locate the keys "导出 CSV", "导出日志失败", and "导出配置" in vi.json and replace the
English value(s) with appropriate Vietnamese strings (e.g., "导出日志失败" -> "Xuất
nhật ký thất bại") ensuring all export-related keys in that file are translated.

[seefs001]

暂时不考虑增加对日志的这种批量导出功能，如果有需要可以自己连接数据库去导报表。

PR被关闭的原因是昨天进行了force push，Github这边自动操作的close，可以按照新的模版再提交一份，未来如果有考虑增加这个功能可能会看一下这个PR。