Repository intelligence

mackerelio/mackerel-container-agent

GitHub

A monitoring agent of Mackerel for containers on container orchestration platforms.

CLOUDM0N decision
REVIEW BEFORE ADOPTION
Trust REVIEW · 80/100
Good fit if

Users who need to monitor containers specifically on container orchestration platforms.

Watch out for

Not intended for non-container environments.

Practical intelligence

What matters before you adopt it

Problem it solves

The need for a dedicated Mackerel monitoring agent tailored specifically for container orchestration platforms.

Best for
Users who need to monitor containers specifically on container orchestration platforms.
Main trade-offs
Not intended for non-container environments.
Why it stands out
Specifically designed and optimized for container environments.
Trust & CVEs

Security evidence without the noise

Trust remains a decision signal; CVEs and scanner evidence explain what is driving the risk.

Security findings
2
CLOUDM0N scanner findings
Critical
0
High
0
Medium
2
Low
0
View trust evidence & security findings
Why this score
No trust rationale was stored for this scan.
CLOUDM0N findings
MEDIUM
Broad permission or elevated-command pattern detected. 1 sample match(es) found.
MEDIUM
Dockerfile does not end with an explicit non-root USER.
Architecture from code16 modules · 0 edges
Structural evidence

Modules and dependency edges extracted from repository code. This is code evidence, not README inference.

Code files
0
Modules
16
Dependency edges
0
Core modules
Dependency flow
No dependency edges were extracted.
Detected languages
Go · Shell
Detected frameworks
Architecture evidence details
flowchart TD
    %% repo — high-level architecture (DRAFT, refine me)
Evidence, security & integrations
Integrations
Mackerel
Security notes
Still unknown
The README does not detail any features, usage instructions, or supported environments, redirecting users to external documentation instead.
No getting started commands, installation scripts, or configuration examples are provided.
Does not discuss operational, scaling, persistence, or security considerations.
Adoption guidance
Adopt if
+ You are using Mackerel and need to monitor containers on a container orchestration platform.
Avoid if
You are monitoring a non-container environment, which requires the standard mackerel-agent instead.
How it works & getting started
How it works
1.Deploys onto container orchestration platforms to act as a monitoring agent of Mackerel.
Getting started
Agent handoff
Use with any agent
JSON API
Alternatives

Nearby repositories worth comparing before adoption.

Compare top options →
signoz
SigNoz/signoz
62
Fit

SigNoz is an open-source, OpenTelemetry-native observability platform for your team and their AI agents. Get logs, metrics, and traces in one tool with features like APM, distributed tracing, log management, infra monitoring, etc. Combined with SigNoz MCP and a native AI teammate (in SigNoz Cloud) it helps you build more resilient apps.

Trust REVIEW · 90
Compare →
Pentest-Swarm-AI
Armur-Ai/Pentest-Swarm-AI
58
Fit

Autonomous penetration testing using a swarm of AI agents. Orchestrates recon, classification, exploitation, and reporting specialists with ReAct reasoning — supports bug bounty, continuous monitoring, and CTF modes. Built with Go, Claude API, and 7+ native security tools.

Trust REVIEW · 65
Compare →
workflow
durable-workflow/workflow
55
Fit

Core package for defining and running durable workflows and activities. Supports long-running persistent workflows, retries, queues, parallel execution, workflow monitoring, dedicated storage connections, and orchestration for microservices, data pipelines, sagas, agentic workflows, and other complex business processes.

Trust REVIEW · 90
Compare →