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.
Multi-Plugin python-based Agent for NewRelic's Platform
| Date | Stars |
|---|---|
| 2026-07-31 | 425 |
| 2026-08-05 | 425 |
| 2026-08-06 | 425 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
NewRelic Plugin Agent
=====================
An agent that polls supported backend systems and submits the results to the
NewRelic platform. Currently supported backend systems are:
- Alternative PHP Cache
- Apache HTTP Server
- CouchDB
- Elasticsearch
- HAProxy
- Memcached
- MongoDB
- Nginx
- pgBouncer
- PHP FPM
- PostgreSQL
- RabbitMQ
- Redis
- Riak
- uWSGI
Base Requirements
-----------------
The agent requires Python 2.6 or 2.7 and ``pip`` for installation. Individual plugin backends may require additional libraries and are detailed below.
Configuration File Note
-----------------------
The configuration file uses YAML as its format. Most tickets for non-working installs are due to configuration file formatting errors. Please make sure you are properly formatting your configuration file prior to submitting a ticket. YAML is a whitespace dependent markup format. More information on writing proper YAML can be found at http://yaml.org.
Installation Instructions
-------------------------
1. Install via ``pip`` *:
::
$ pip install newrelic-plugin-agent
* See ``pip`` installation instructions at http://www.pip-installer.org/en/latest/installing.html
2. Copy the configuration file example from ``/opt/newrelic-plugin-agent/newrelic-plugin-agent.cfg`` to ``/etc/newrelic/newrelic-plugin-agent.cfg`` and edit the configuration in that file.
3. Make a ``/var/log/newrelic`` directory and make sure it is writable by the user specified in the configuration file
4. Make a ``/var/run/newrelic`` directory and make sure it is writable by the user specified in the configuration file
5. Run the app:
::
$ newrelic-plugin-agent -c PATH-TO-CONF-FILE [-f]
Where ``-f`` is to run it in the foreground instead of as a daemon.
Sample configuration and init.d scripts are installed to ``/opt/newrelic-plugin-agent`` in addition to a PHP script required for APC monitoring.
Installing Additional Requirements
----------------------------------
To use the MongoDB the ``mongodb`` library is required. For the pgBouncer or PostgreSQL plugin you must install the ``psycopg2`` library. To easily do
this, make sure you have the latest version of ``pip`` installed (http://www.pip-installer.org/). This should be done after installing the agent itself:
::
$ pip install newrelic-plugin-agent[mongodb]
or::
$ pip install newrelic-plugin-agent[pgbouncer]
or::
$ pip install newrelic-plugin-agent[postgresql]
If this does not work for you, make sure you are running a recent copy of ``pip`` (>= 1.3).
Plugin Configuration Stanzas
----------------------------
Each plugin can support gathering data from a single or multiple targets. To support multiple targets for a plugin, you create a list of target stanzas:
::
plugin_name:
- name: target_name
host: localhost
foo: bar
- name: target_name
host: localhost
foo: bar
While you can use the multi-target format for a plugin's configuration stanza like:
::
plugin_name:
- name: target_name
host: localhost
foo: bar
You can also use a single mapping like follows:
::
plugin_name:
name: target_name
host: localhost
foo: bar
The fields for plugin configurations can vary due to a plugin's configuration requirements. The name value in each stanza is only required when using multiple targets in a plugin. If it is only a single target, the name will be taken from the server's hostname.
APC Installation Notes
----------------------
Copy the ``apc-nrp.php`` script to a directory that can be served by your web server or ``php-fpm`` application. Edit the ``newrelic-plugin-agent`` configuration to point to the appropriate URL.
Apache HTTPd Installation Notes
-------------------------------
Enable the HTTPd server status page in the default virtual host. The following example configuration snippet for Apache HTTPd 2.2 demonstrates how to do this:
::
<Location /server-status>
SetHandler serverExcerpt of 14,598 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.