iflytek/astron-agent · info

Trace log functionality not yet implemented - ElasticSearch…

Error message

Trace log functionality not yet implemented - ElasticSearch integration pending

What it means

A warn log stating trace log retrieval is a stub: getBotTrace always returns an empty page because ElasticSearch integration is not implemented. Not an actual failure — a feature-not-yet-built placeholder.

Solutions

  1. Implement the ElasticSearch trace query or route to an existing trace service
  2. Return an explicit 'not implemented' status to clients instead of empty data
  3. Check product roadmap/alternatives before relying on this endpoint

Example fix

// before
log.warn("Trace log functionality not yet implemented - ElasticSearch integration pending");
return PageResponse.of(requestDto.getPage(), requestDto.getPageSize(), 0L, new ArrayList<>());
// after
throw new UnsupportedOperationException("Trace logs require ElasticSearch integration (pending)");
Defensive patterns

Strategy: fallback

When it happens

Trigger: Any call to getBotTrace regardless of input; the endpoint returns an empty paginated result every time.

Common situations: Frontend trace-view page shows no logs; users expect trace data but the ES backend was never wired up.

Related errors


AI-assisted analysis of iflytek/astron-agent@5e758547a8 (2026-09-12). Data as JSON: /api/errors/d11e98bfd0206e8e. Report an issue: GitHub.

Appendix: source

Thrown at console/backend/hub/src/main/java/com/iflytek/astron/console/hub/service/publish/impl/BotPublishServiceImpl.java:475

    // ==================== Trace Log Management ====================

    @Override
    public PageResponse<Object> getBotTrace(String uid, Integer botId, BotTraceRequestDto requestDto, Long spaceId) {
        log.info("Getting trace logs for bot: botId={}, uid={}, spaceId={}, request={}",
                botId, uid, spaceId, requestDto);

        // TODO: Implement actual trace log retrieval logic when ElasticSearch is available
        // This is a placeholder implementation until ES integration is ready
        //
        // When implementing:
        // 1. Validate bot permissions (check if user has access to this bot)
        // 2. Get bot flow ID from bot configuration
        // 3. Query trace logs from ElasticSearch with time range and filters
        // 4. Apply additional filters (logLevel, keyword, traceId, sessionId)
        // 5. Return paginated results

        log.warn("Trace log functionality not yet implemented - ElasticSearch integration pending");

        // Return empty result for now
        return PageResponse.of(requestDto.getPage(), requestDto.getPageSize(), 0L, new ArrayList<>());
    }

    // ==================== Publish Prepare Data Management ====================

    @Override
    public UnifiedPrepareDto getPrepareData(Integer botId, String type, String currentUid, Long spaceId) {
        log.info("Getting prepare data: botId={}, type={}, uid={}, spaceId={}", botId, type, currentUid, spaceId);

        try {
            // Validate publish type
            ReleaseTypeEnum publishTypeEnum = ReleaseTypeEnum.getByName(type);
            if (publishTypeEnum == null) {
                return createErrorPrepareResponse("Invalid publish type: " + type);
            }

View on GitHub (pinned to 5e758547a8)