Introduction

When performance issues arise in Weaver E10 (e10 / Weaver OA), operations and development teams typically receive a diagnostic package exported from the server rather than a simple error message. The filename often follows the format “downLog.zip from [IP]” or may simply be a .log file. This package is packed with metrics regarding CPU, JVM/GC, memory, database connection pools, concurrency, and disk I/O, alongside middleware exception logs and JVM thread dumps.

The most time-consuming part of troubleshooting these issues is not reading the logs, but organizing thousands of lines of metrics into comparable curves and identifying bottlenecks within thread dumps. Manual log inspection often leads to oversights and makes conclusions difficult to reproduce. The Skill introduced below delegates this step to an Agent.

What is This

“Weaver E10 Performance Log Analysis” is a log analysis Skill designed for Weaver E10 / eBuilder / Weaver OA, identified by the coordinates @user_f6995a55/e10-perf-log-analysis. Published and maintained by community developer user_f6995a55, the current version is 1.0.1. It is sourced from the community, categorized under it-ops-security, and does not require an API Key (requires_api_key=false).

It solves a specific problem: given a Weaver E10 performance log archive or a single .log file, the Skill parses the contents and generates a visualized HTML report, rather than simply returning the raw logs to the user.

Core Functions

The Skill’s coverage is divided based on the structure of official Weaver diagnostic packages, handling three types of input:

  1. Metric Logs: Includes six categories of metrics—CPU, JVM/GC, memory, database connection pools, concurrency, and disk I/O—corresponding to the performance counter exports included in the package.
  2. Middleware Exception Logs: Error and alert records from the server-side middleware layer.
  3. JVM Thread Dumps: Used to identify thread blocking, deadlocks, or hotspot methods.

The output is a unified, visualized HTML report, suitable for direct distribution to operations colleagues or attachment to work tickets. These three content types are standard components of Weaver E10 downLog packages; the Skill’s role is parsing and visualization, without performing additional data collection.

Installation and Activation

The official page does not provide a standalone installation command or configuration file path. Based on the general SKILL.md format, this Skill is executed by the Agent runtime according to the instructions within the SKILL.md. In Agent environments that support Skills (such as Cursor, Codex CLI, Claude Code, etc.), it can be imported using the respective platform’s Skill addition methods. Specific commands should follow the corresponding platform’s documentation.

It is important to note that the content of the SKILL.md was not provided in the source material, so assumptions about internal scripts or dependencies are not made here. It is recommended to open the official page to confirm prerequisites before use. The author has also noted in the introduction, “Please contact the author if you have any questions.”

Typical Usage

Usage is driven by direct conversation. The user provides the diagnostic package to the Agent and states their intent, for example:

  • “This is a downLog.zip exported from 10.x.x.x. Please perform a performance analysis and identify the bottlenecks.”
  • “The system is lagging heavily; here is the .log file. Please generate a health report.”

Upon receipt, the Skill completes the parsing and chart generation, returning an HTML report. The analysis scope, conclusions, and recommendations are all based on the content existing within the package.

Use Cases and Notes

Suitable scenarios: Initial localization of server-side performance issues in Weaver E10 / eBuilder / Weaver OA, periodic health checks, and situations where analysis reports need to be presented to business stakeholders.

Limitations to note:

  • Only processes server-exported downLog.zip or .log files; it does not replace monitoring instrumentation or stress testing, nor does it collect real-time metrics.
  • The quality of conclusions depends on the completeness of the logs within the package. If the log time span is too short or thread dumps are missing, bottleneck judgments may rely more on speculation.
  • Maintained by the community; ratings and download counts (Score: 100000, Downloads: 1210, Installs: 0) are SkillHub page data and do not represent official support levels.

Conclusion

The value of this Skill lies in standardizing the repetitive work of “unpacking archives, reading logs, plotting curves, and writing conclusions,” allowing the Agent to directly produce deliverable HTML reports. If you regularly handle Weaver E10 performance tickets, it is worth adding to your toolchain for a trial run.

Official URL: https://api.skillhub.cn/user_f6995a55/e10-perf-log-analysis
SkillHub Page: https://www.skillhub.cn/skills/user_f6995a55/e10-perf-log-analysis