Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Elastic Agent - single, unified way to add monitoring for logs, metrics, and other types of data to a host.
| Date | Stars |
|---|---|
| 2026-07-31 | 269 |
| 2026-08-04 | 269 |
| 2026-08-06 | 269 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
35.0
growth rate 0.00%/day
# Elastic Agent [](https://buildkite.com/elastic/elastic-agent) ## Architecture and Internals - [Agent architecture](docs/architecture.md) - [Component spec files](docs/component-specs.md) - [Policy configuration](docs/agent-policy.md) ## Official Documentation See https://www.elastic.co/guide/en/fleet/current/index.html. The source files for the official Elastic Agent documentation are currently stored in the [ingest-docs](https://github.com/elastic/ingest-docs/tree/main/docs/en/ingest-management) repository. ## Contributing See [CONTRIBUTING.md](CONTRIBUTING.md). ## Developing The following are exclusively focused on getting developers started building code for Elastic Agent. ### Development Installations > :warning: Development installations are not officially supported and are intended for Elastic Agent developers. If you are an Elastic employee, you already have an Information Security managed Elastic Agent installed on your machine for endpoint protection. This prevents you from installing the Elastic Agent a second time for development without using a VM or Docker container. To eliminate this point of friction, Elastic Agent has a development mode that permits installing the Elastic Agent on your machine a second time: ```sh # All other arguments to the install command are still supported when --develop is specified. sudo ./elastic-agent install --develop # The run command also supports the --develop option to allow running without installing when there is another agent on the machine. ./elastic-agent run -e --develop ``` Using the `--develop` option will install the agent in an isolated `Agent-Development` agent directory in the chosen base path. Development agents enrolled in Fleet will have the `Development` tag added automatically. Using the default base path on MacOS you will see: ```sh sudo ls /Library/Elastic/ Agent Agent-Development ``` The `elastic-agent` command in the shell is replaced with `elastic-development-agent` to interact with the development agent: ```sh # For a privileged agent sudo elastic-development-agent status # For an unprivileged agent sudo -u elastic-agent-user elastic-development-agent status ``` The primary restriction of `--develop` installations is that they cannot run Elastic Defend. Defend requires the agent to be in the default path, the same restrictions applies for the `--base-path` option. All other integrations should be usable provided conflicting configurations are changed ahead of time. For example two agents cannot bind to the same `agent.monitoring.http.port` to expose their monitoring servers. ### Test Framework In addition to standard Go tests, changes to the Elastic Agent are always installed and tested on cross-platform virtual machines. For details on writing and running tests see the [Test Framework Developer Guide](docs/test-framework-dev-guide.md). ### Changelog The changelog for the Elastic Agent is generated and maintained using the [elastic-agent-changelog-tool](https://github.com/elastic/elastic-agent-changelog-tool). Read the [installation](https://github.com/elastic/elastic-agent-changelog-tool/blob/main/docs/install.md) and [usage](https://github.com/elastic/elastic-agent-changelog-tool/blob/main/docs/usage.md#im-a-developer) instructions to get started. The changelog tool produces fragment files that are consolidated to generate a changelog for each release. Each PR containing a change with user impact (new feature, bug fix, etc.) must contain a changelog fragment describing the change. There is a GitHub action in CI that will fail if a PR does not contain a changelog fragment. For PRs that should not have a changelog entry, use the "skip-changelog" label to bypass this check. A simple example of a changelog fragment is below for reference: ```yml kind: bug-fix summary: Fix a panic caused by a race condition when installing the Elastic A
Excerpt of 13,205 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
Not classified yet. Classification runs as part of npm run ingest.