pinpoint-apm/pinpoint · info

- agentId: {}

Error message

- agentId: {}

What it means

WARN log line from dumpAgentOption printing the agentId taken from the agent's ObjectName. It is part of the standard startup option dump, not an error. It exists so operators can verify which agentId the profiler actually resolved from config/system properties.

Source

Thrown at agent-module/profiler/src/main/java/com/navercorp/pinpoint/profiler/DefaultAgent.java:137

            System.err.printf("ObjectName validation failed %s %s", e.getAgentIdType(), e.getMessage());
            throw e;
        }
    }

    protected AgentContextOption buildContextOption(AgentOption agentOption, ObjectName objectName, ProfilerConfig profilerConfig) {
        return AgentContextOptionBuilder.build(agentOption, objectName, profilerConfig);
    }

    private AgentSystemConfig agentSystemConfig(ObjectName objectName) {
        AgentSystemConfig agentSystemConfig = new AgentSystemConfig(objectName.getAgentId(), Version.VERSION);
        agentSystemConfig.dump(System.getProperties());
        return agentSystemConfig;
    }

    private void dumpAgentOption(AgentContextOption agentOption) {
        final ObjectName objectName = agentOption.getObjectName();
        logger.warn("AgentOption : {}", objectName.getClass().getSimpleName());
        logger.warn("- agentId: {}", objectName.getAgentId());
        logger.warn("- agentName: {}", objectName.getAgentName());
        logger.warn("- applicationName: {}", objectName.getApplicationName());
        if (objectName instanceof ObjectNameV4) {
            ObjectNameV4 v4 = (ObjectNameV4) objectName;
            logger.warn("- serviceName: {}", objectName.getServiceName());
            logger.warn("- apikey: {}", MaskUtils.masking(v4.getApiKey(), 2));
        }
        logger.info("- instrumentation: {}", agentOption.getInstrumentation());
    }


    private LoggingSystem newLoggingSystem(Path agentPath) {
        return Log4j2LoggingSystem.searchPath(agentPath);
    }

    protected ApplicationContext newApplicationContext(AgentContextOption agentOption) {
        Objects.requireNonNull(agentOption, "agentOption");
        ProfilerConfig profilerConfig = Objects.requireNonNull(agentOption.getProfilerConfig(), "profilerConfig");

View on GitHub (pinned to 744c3d3075)

Solutions

1. No action needed if the agentId shown is correct.
2. If the agentId is wrong, fix agentId in pinpoint.config or -Dpinpoint.agentId and restart.
3. Ensure agentId is unique per JVM instance to avoid collector-side overwrites.

// check resolved agentId at startup
String agentId = System.getProperty("pinpoint.agentId");
if (agentId == null || agentId.isEmpty()) { /* fix pinpoint.config */ }

When it happens

Trigger: Agent startup; always printed right after the 'AgentOption :' header line.

Common situations: Checking logs to confirm the agent registered under the expected agentId; diagnosing duplicate-agent-id conflicts with the collector.

Related errors

• - agentName: {}
• - applicationName: {}
• Unknown AgentType:
• Failed to detect pinpoint profile. Please add -Dpinpoint.act
• 'log4j2-agent.xml' not found. agentPath:${profilePath}

AI-assisted analysis of pinpoint-apm/pinpoint@744c3d3075 (2026-09-07). Data as JSON: /api/errors/2b8479ccbf5401c6. Report an issue: GitHub.