Machine Agent

This is the Docker image repository for the AppDynamics Machine Agent, the lightweight monitoring agent that infrastructure teams use to collect system and…

  • Infrastructure
  • Monitoring & Logging
  • Tools & Utilities
This is the Docker image repository for the AppDynamics Machine Agent, the lightweight monitoring agent that infrastructure teams use to collect system and application metrics on Docker workloads.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

57/100 Fair

Maintained
No data
Popular
No data
Easy to install
250 install platforms, install notes, Docker image
Light to run
100128 MB minimum RAM, runs on ARM

Based on 2 of 4 factors.

No GitHub repository data collected yet.

Resources & Compatibility

Minimum requirements: 128 MB RAM, 100 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Keep your OS machine ID intact Before starting machine-agent, keep the operating system's existing machine ID intact; it is the built-in label the app uses to recognize your computer. Don't delete or manually change the Linux ID files (/var/lib/dbus/machine-id or /etc/machine-id), the Windows built-in identifier called MachineGuid, or similar system values, because a missing or altered ID can make the app fail to identify the m source
  • The machine ID lookup should not need admin The machine ID can be read without root/admin (superuser) access, so you usually don't need to grant extra permissions just to use machine-agent. If it fails to read the ID, the more likely problem is a missing or unreadable system machine ID file, not that your account lacks special permissions. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to keep the operating system machine ID unchanged before starting machine-agent?

Yes. Keep the existing OS machine ID intact because the app uses it to recognize your computer, and do not delete or manually change the Linux machine ID files or the Windows MachineGuid.

What pitfalls should I watch for when migrating a working pipeline to self-hosted agents?

Expect common issues that appear while moving an existing, working pipeline to self-hosted agents. The goal is to apply the documented mitigations for those migration problems.

What common problems should I check when troubleshooting a self-hosted agent system?

Check GPU memory, model loading, inference performance, container management, and agent behavior. Most issues have straightforward solutions once the root cause is identified.

Answers sourced from devblogs.microsoft.com, docs.rs, www.autolearningagents.com

Community

Collected 48 days ago - public community threads