1.2k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill xiaomi/mone --skill hera- README.md1.6 KB
- reference.md6.3 KB
- SKILL.md4.1 KB
Overview
This skill provides a compact toolkit for querying Hera log details programmatically by spaceId, storeId, tailName and time range. It exposes a single, easy-to-use function to fetch log entries, filter by search text, and control time ranges. Use it to retrieve recent logs, search for specific messages, or pull logs for a custom interval.
How this skill works
The function constructs a Hera API request using required identifiers (space_id, store_id, tail_name) and optional parameters (input_text, start_time, end_time, api_url). If time range is omitted it defaults to the last hour; api_url can be read from an environment variable or passed directly. The tool validates parameters, performs the HTTP request, parses JSON responses, and surfaces clear error messages for network or parsing failures.
When to use it
- When you need recent application logs for a specific tailName and storeId
- When searching logs for a specific error string or exception text
- When automating log queries inside scripts or CI pipelines
- When extracting logs over a custom millisecond timestamp range
- When you need programmatic access to Hera log details from other services
Best practices
- Always provide space_id, store_id and tail_name—these are required for accurate queries
- Prefer passing start_time and end_time as millisecond timestamps for reproducible queries
- Escape or quote special characters in input_text to avoid unexpected query behavior
- Use the environment variable HERA_LOG_DETAIL_API_URL to centralize endpoint configuration in automation
- Handle and log returned error messages and non-200 HTTP responses for diagnostics
Example use cases
- Fetch the last hour of logs for a service tail to inspect recent failures
- Search logs for the string "ERROR" across a store to identify application exceptions
- Pull logs for a deployment window by specifying start_time and end_time in milliseconds
- Integrate into CI to automatically collect logs when integration tests fail
- Override api_url in tests to use a staging Hera endpoint and validate query logic
FAQ
space_id, store_id and tail_name are required. input_text, start_time, end_time and api_url are optional.
What format should start_time and end_time use?
Use millisecond timestamps as strings. If omitted, the function defaults to querying the last hour.