Saravanan666/pypi-org huggingface dataset:
Package: collectd-csv
CollectD-CSV is a small project providing utilities for analyzing CollectD
CSV data locally.CollectD_CSV module provides functions for fetching data with a specified
time interval and regular expressions matching the end of the path excluding
the datestamp. The fetched data can be saved into files or returned as an
ordered dictionary.fetchCSV.py script can be used to fetch the data matching the given parameters
and save to files in a specified directory.monitorCSV.py script calculates the minimum, average and maximum values of
specified resources on one host from the last XX minutes.Typical usage of the module looks like this:#!/usr/bin/env python

import CollectD_CSV
from collections import OrderedDict

regexps = ["myhost/load.*", "myotherhost/memory.*"]

#fetch the data into an ordered dictionary
resultdirct = CollectD_CSV.fetchData(123456789, 123498765, regexps,
                                     "/var/lib/collectd", destdir=None)See more information about the usage in the comments of CollectD_CSV.py.
For complete usage examples, see bin/fetchCSV.py and bin/monitorCSV.py.
For help in using the scripts use the “-h” command line option.
Package: collectd-cvmfs
Collectd Module for CvmFSConfigurationExample:TypesDB "/usr/share/collectd/collectd_cvmfs.db"
<Plugin "python">
  Import "collectd_cvmfs"
  <Module "collectd_cvmfs">
    Repo "alice.cern.ch" "atlas.cern.ch"
    Repo "ams.cern.ch"
    MountTime True
    MountTimeout 10
    Memory True
    Attribute ndownload nioerr
    Attribute usedfd
    Verbose False
    Interval "300"
  </Module>
</Plugin>TypesDB: types used by the plugin and shipped with the package.Repo: cvmfs repository to monitor.MountTime: boolean value to specify whether mount time should be reported or not.MountTimeout: timeout in seconds while trying to mount the repositories.Memory: boolean value to specify whether the memory footprint should be reported or not.Attribute: attribute to monitor on the given repositories. You can get the list from of valid attributes from the type db inresources/collectd_cvmfs.db.Interval: interval in seconds to probe the CVMFS repositories.Verbose: boolean value to produce logs more verbosed in collectd. It is false by default.The plugin allows multiple instances for different configurations. This allows probing different repos at different intervals or probing different attributes depending on the repository.MetricsThe metrics are published in the following structure:Plugin: cvmfs
PluginInstance: <repo>
Type: {<Attribute>|MountTime|Memory|Mountok}

# Only with Memory:
TypeInstance: [rss|vms]Example:lxplus123.cern.ch/cvmfs-lhcb.cern.ch/mounttime values=[0.000999927520751953]
lxplus123.cern.ch/cvmfs-lhcb.cern.ch/nioerr values=[0]
lxplus123.cern.ch/cvmfs-lhcb.cern.ch/memory-rss values=[31760384]
lxplus123.cern.ch/cvmfs-repo.domain.ch/mountok values=[1]News1.3.3
* Release date: 15-Apr-2021
* Fix psutil call for read memory metrics #17
1.3.0
* Release date: 8-Jul-2020
* Success of mount now confirmed checking attribute fqrn
* Pip requirements corrected to require pyxattr and not xattr1.2.0
* Release date: 25-Jul-2019
* New metric MountOK with value 0 (no) 1 (yes)
* Mounts now use scandir to avoid hanging.1.1.0Release date: 13-May-2019remove memory type definition1.0.3Release date: 18-Oct-2017Make collectd aware of explicit interval so
that it does not flush the value to soon.Documentation about TypesDB file.1.0.2Release date: 25-May-2017Correct name of type database.1.0.1Release date: 25-May-2017First release
Package: collectd-eos
Collectd plugin to collectEOSmetrics.
Connects to a mgm instance using eos client and publishes node, fs and space metrics.Collectd config section example:<Plugin python>
    Import collectd_eos
    <Module collectd_eos>
        instance example root://eos.example
        instance another root://another.eos.instance.example
        instance third root://third.mgm.intance.example
        interval 60
        eos_client_command ssh client.host.example eos
    </Module>
</Plugin>instanceexpects 2 values:EOS instance name / plugin instance nameEOS MGM URLintervaloverrides the default collection intervaleos_client_commandis used when there is no eos client on the collectd node,
and ssh or docker are needed to run eos, especially during plugin developmentIf there are no instances defined in config and $EOS_MGM_URL is set,
it is used as the default url with the instance name set to the hostname portion.If there are no instances defined in config and $EOS_MGM_URL is unset,
the current hostname is used as the instance name and url.TestingTest in virutalenv:virtualenv venv
. venv/bin/activate
pip install -r build-requirements.txt -r test-requirements.txt
pip install -e .
pytest
python setup.py sdist bdist_wheel
twine check dist/*
toxUse collectd.conf or collectd.docker.conf for functional testing: does the plugin cope with real metrics?On a host with eos:$ collectd -Tf -C collectd.confDocker can be used for the eos client:$ docker run --name eos_client --rm -itd gitlab-registry.cern.ch/dss/eos:4.4.10
<container id output>
$ docker exec -it eos_client kinit <username>@CERN.CH
<password prompt>
$ collectd -Tf -C collectd.docker.conf
<check collectd log for errors>
$ docker stop eos_clientChangelogAll notable changes to this project will be documented in this file.The format is based onKeep a Changelog,
and this project adheres toSemantic Versioning.0.2.1- 2019-02-28AddedMore testingMore documentationFixedReadme needed one more newline at the end to be used as the package descriptionRemovedPython 2.6 support no longer promised, attempted, or tested.0.2.0- 2019-02-27Addedpyproject.toml to define build requirements as perPEP-518build-requirements.txt and build-requirements.26.txt to document build requirements
in a more realistic, backwards-compatible way.ChangedConfiguration section format. mgm_url key is removed
EOS instances are now defined by the key “instance” which expects two values:instance name, must be unique,
defines the collectd plugin instance name reported with the metricsmgm_url, the url eos client will query for dataFixedDon’t sent interval of -1 to collectd, it does not interpret it as default0.1.0- 2019-02-26AddedREADME.rst and CHANGELOG.rstpackage sources src/collectd_eosunit tests in tests/ and tox.inicollectd.conf and collectd.docker.conf for testing with collectdeos.types.db to define eos time-series datasets for collectdLICENSE Apache 2
Package: collectd-gnocchi
This is an output plugin forcollectdthat send metrics toGnocchi. It
will create a resource type named _collectd_ (by default) and a new resource
for each of the host monitored.Each host will have a list of metrics created dynamically using the following
name convention:plugin-plugin_instance/type-type_instance-value_numberIn order for the metric to be created correctly, be sure that you have matchingarchive policies rules.InstallationThis is a regular Python package that you can install viaPyPIusing:pip install collectd-gnocchiOr from sources using:pip install .In order to use this plugin you will need a server running theGnocchi 3.1or greater.ConfigurationOnce installed, you need to enable it in yourcollectd.conffile this way:.. include:: collectd-gnocchi.confYou can also copy the providedcollectd-gnocchi.conffrom this repository in
e.g./etc/collectd.dif your distribution supports it.
Package: collectd-gnocchi-status
OverviewThis plugin provides valuable insight into your metrics and measures
backlog of Gnocchi when installed in an OpenStack environment. It costs
an API call to Gnocchi status API every $interval (set in the collectd
config file per the plugin). Gnocchi is a component of the OpenStack
Telemetry project for Metric-as-a-Service.Sample GraphConfigurationAssuming you have collectd installed already, append the following
plugin details to your collectd.conf config file```
<LoadPlugin python>
  Globals true
</LoadPlugin>

<Plugin python>
  LogTraces true
  Interactive false
  Import "collectd_gnocchi_status"
  <Module collectd_gnocchi_status>
    interval 30
  </Module>
</Plugin>
```Setup your environment variables in the collectd systemd unit file```
# Populate the following variables with your stackrc/overcloudrc or openstackrc file
# Tenant v1&v2 api, project for v3 api
Environment=OS_TENANT_NAME=admin
Environment=OS_PROJECT_NAME=admin

Environment=OS_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxxxx
Environment=OS_USERNAME=admin
Environment=OS_AUTH_URL=http://x.x.x.x:5000/v2.0
Environment=OS_CLOUDNAME=overcloud
Environment=OS_NO_CACHE=True
# End Environment variables to configure
```Install plugin```
[root@overcloud-controller-0 ~]# pip install collectd-gnocchi-status
```Reload Systemd units[root@overcloud-controller-0 ~]# systemctl daemon-reloadRestart collectd[root@overcloud-controller-0 ~]# systemctl restart collectdView metrics on Gnocchi in your TSDBGraphite storage-aggregation.conf ExampleIncluded in the repo is an example Graphite storage-aggregation.conf
(sample-storage-aggregation.conf) to ensure that your Gnocchi status
metrics are not lost due to your retention sizing (Ex.
10s:7d,60s:90d,1h:180d) < the interval (30s) this plugin is set to
collect and publish samples. Simply copy and paste the example, into
your /etc/carbon/storage-aggregation.conf file on your Graphite server
prior to pushing these metrics and restart carbon-cache to reload this
configuration. If the metrics have already been pushed, you must either
use whisper-resize (included with Graphite) or remove the corresponding
whisper files after restarting carbon-cache to allow carbon to rebuild
them with the new parameters in storage-aggregation.conf.ResourcesGnocchi.xyzCollectd.org
Package: collectd-haproxy
A plugin forcollectdto gather metrics for a localHAProxyinstance, with a
focus on easy installation and configuration.(graphs made withGrafana)InstallationThe project is onPyPIso installation is a simplepipcommand:pip install collectd-haproxyNoteIf collectd is running with a virtualenv activated (under an isolatedsupervisordsetup, for instance) make sure thecollectd-haproxypackage
is installed and available in the virtualenv’s module path or collectd will
run into anImportError.In order to function properly, the local HAProxy instance will need to have
the “stats socket” enabled, details about how to do that can be foundhere.ConfigurationThe most basic configuration is to specify where the HAProxy socket file is
located:LoadPlugin "python"

<Plugin python>
    Import "collectd_haproxy"

    <Module haproxy>
      Socket "/var/run/haproxy.sock"
    </Module>
</Plugin>For details on all of the options available,read the docs!DevelopmentThe code is hosted onGitHubTo file a bug or possible enhancement see theIssue Tracker, also found
on GitHub.License(c) 2015-2016 William Glasscollectd-haproxy is licensed under the terms of the MIT license.  See theLICENSEfile for more details.
Package: collectd-ipa
Collectd plugin for IPAA Collectd plugin to extract metrics from IPACurrently supported metrics:groups: the number of groupsusers: the number of users, active or disabledusers_rate: the rate at which the number of users is changing (registered
users and deletions)staged_users: the number of staged users (users in the process of
registering for an account), split by their spam detection status.InstallationOn the IPA host:install the python module where Collectd's python plugin can see itrunmake installOn the host where the collectd server is running:runmake install-dataappend the content ofcollection.confto your/etc/collection.confConfigurationThecollectd.d/ipa.conffile has an example of the available configuration
values that you can adjust, in theModule collectd_ipablock.It contains descriptions of what the configuration variables mean and their
default values.LicenseLicensed underlgpl-3.0
Package: collectd-ntp
A collectd plugin to fetch NTP offsets from a pool.The default update interval is 60 seconds.InstallationThe latest stable version can be installed fromPyPI:$pipinstallcollectd-ntpConfigurationTo configure the plugin:<LoadPluginpython>Globalstrue</LoadPlugin><Pluginpython>Import"ntpoffset"<Module"ntpoffset">#NTPpooladdresspool"pool.ntp.org"</Module></Plugin>
Package: collectd-plugin-VMG1312-xDSL
collectd-plugin-VMG1312-B30A-xDSLSupported hardwareThis is acollectdplugin for monitoring the
xDSL status of Zyxel VMG1312 VDSL/VDSL2 modems/routers.I developed and tested it with the B30A-version (a VDSL2-Vectoring modem
for Germany) of this modem, but it might work as well with other
variants.Supported parametersThis plugin reads thexDSL-status only!For reading things like interface-counters etc. the modem has anSNMP-serverthat can be used. Unfortunately this SNMP-server does
not serve the xDSL-status (facepalm!), that's where this plugin comes
into place.If your modem has a page like the one shown below, this plugin will
probably be able to read all status parameters of the first three
sections. The "VDSL Counters" section won't be a read - I don't see much
use in reading these.Dependenciescollectd 4.9+Installationpip3 install collectd-plugin-VMG1312-xDSLConfigure the plugin as shown belowRestart collectdConfigurationLoadPlugin python 
<Plugin python>
    Import "VMG1312_xDSL"

    <Module VMG1312_xDSL>
        URL "http://<ip_of_your_modem>"
        User "admin"
        Password "1234"
    </Module>
</Plugin>LicenseThis project is licensed under the terms of the GPLv3 license.Buildpython setup.py sdisttwine upload dist/*
Package: collectd-plugin-VMG3006-xDSL
collectd-plugin-VMG3006-D70A-xDSLSupported hardwareThis is acollectdplugin for monitoring the
xDSL status of Zyxel VMG3006 VDSL/VDSL2-supervectoring modems.I developed and tested it with the D70A-version (a VDSL2-Vectoringsupervectoring modem for Germany) of this modem, but it might work aswell with other variants.Supported parametersThis plugin reads thexDSL-status only!It does not support reading things like interface-counters etc.If your modem has a page like the one shown below, this plugin will
probably be able to read all status parameters of the paragraphs
"Data rate" , "Operation data / defect indication" and
"Error indicators".Dependenciescollectd 4.9+Installationpip3 install collectd-plugin-VMG3006-xDSLConfigure the plugin as shown belowRestart collectdConfigurationLoadPlugin python 
<Plugin python>
    Import "VMG3006_xDSL"

    <Module VMG3006_xDSL>
        URL "http://<ip_of_your_modem>"
        User "admin"
        Password "1234"
    </Module>
</Plugin>LicenseThis project is licensed under the terms of the GPLv3 license.Buildpython setup.py sdisttwine upload dist/*
Package: collectd-prometheus
collectd-prometheusA collectd Python plugin to read Prometheus metrics endpointsInstallationFind out which version of Python your collectd is built against to know
which python/pip binary to use. So e.g. with Debian:$ dpkg -S python.so | grep collectd
collectd-core: /usr/lib/collectd/python.so
$ ldd /usr/lib/collectd/python.so | grep python
libpython2.7.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 (0x00007f953a5c2000)
$which uses Python 2.7 still so I need to usepip2when installing the
dependencies.Installcollectd-prometheus:# pip2 install collectd-prometheusUsageCreate a collectd configuration e.g./etc/collectd/collectd.conf.d/prom-service.confLoadPluginpython<Pluginpython>Import"collectd_prometheus"<Module"collectd_prometheus">Interval30#Howoftentoscrapemetrics.Thisisthedefault,canbeomitted<Process>Process"mycoolservice"#Namethisinstance,e.g.afterwhatserviceyou'rescrapingProtocol"http"#Thisisdefault,canbeomittedHost"127.0.0.1"#Thisisdefault,canbeomittedPort"8080"#Thisisdefault,canbeomittedFilter"only|these"#AregexwhichmatchesthenamesofthemetricsyouonlywanttoincludeFilter"metrics"#Youcanevenspecifymultipleregexes</Process># Scrape another another service as well, e.g.<Process>Process"anothercoolservice"# This time we use the defaults, except PortPort"8081"</Process></Module></Plugin>Using a virtualenvIn Python, using a virtual environmentis the
recommendedway to isolate your
applications dependencies from other applications. To use a virtualenv with
collectd we have to create one, activate it, install our package into it.Using the steps listedInstallationfigure out which Python
version collectd uses.If python3 usevenvwhich is included in Python 3. When using Python 2.7,
we have toinstall
virtualenvwhich
can be packaged in your OS/distribution (python-virtualenvin Debian) or
you install it manually, see the linked documentation.Create your virtualenv where you want to store it, e.g:# python -m virtualenv /usr/lib/collectd/promActivate it and install our package, e.g.:# source /usr/lib/collectd/prom/bin/activate
(prom) # pip install collectd-prometheusFind your virtualenvs site-packages folder, e.g:# find /usr/lib/collectd/prom/ -type d -iname "site-packages"
/usr/lib/collectd/prom/lib/python2.7/site-packagesConfigure collectd to look forcollectd-prometheusand it's dependencies
in the directory that you found in step 5. E.g:LoadPluginpython<Pluginpython>ModulePath"/usr/lib/collectd/prom/lib/python2.7/site-packages"#RighthereImport"collectd_prometheus"[…]
Package: collectd-puppet
ConfigurationTypesDB"/usr/share/collectd/puppet_types.db"<LoadPluginpython>Globalstrue</LoadPlugin><Plugin"python">LogTracestrueInteractivefalseImport"puppet"PATH"/opt/puppetlabs/puppet/cache/state/last_run_summary.yaml"MaxRetention21600</Plugin>TheMaxRetentionsetting represents, in seconds, for how long the value of
the metrics will be retained if there’s no fresh data to publish during the
Collectd loop. Be aware that this setting depends on the globalTimeout. For
instance, if you want a retention of 6 hours and the Collectd timeout is set to
2 then you’ll have to halve value and set it to(6*60*60)/2.Generated dataThe plugin parses/opt/puppetlabs/puppet/cache/state/last_run_summary.yamland reports
several single values extracted from there.It will only send data if there has been a Puppet run after the last
time Collectd polled. This is monitored using a state file located in/var/lib/collectd/puppet.state. To force a data point just delete
it.These are the values that are currently being dispatched:puppet/boolean-compiled (flag denoting if the catalog compiled (1 or 0))puppet/seconds-config_retrievalpuppet/seconds-total_timepuppet/resources-changedpuppet/resources-corrective_changepuppet/resources-failedpuppet/resources-failed_to_restartpuppet/resources-out_of_syncpuppet/resources-restartedpuppet/resources-scheduledpuppet/resources-skippedpuppet/resources-totalpuppet/time_ref-last_run (epoch of last puppet run (seconds))AuthorsSteve Traylen <steve.traylen@cern.ch>
Nacho Barrientos <nacho.barrientos@cern.ch>Copyright2018 CERNLicenseApache-II LicenseDevelopment notesDon’t forget to bump theschema_versionif you modify the data format.
Package: collectd-rabbitmq
“A collected plugin, written in python, to collect statistics from RabbitMQ.”Free software: Apache licenseDocumentation:https://collectd-rabbitmq.readthedocs.org.For the older single file version seehttps://github.com/NYTimes/collectd-rabbitmq/tree/0.1.1FeaturesSupport queue, exchange, and node stats,ConfigurationThis plugin supports a small amount of configuration options:Username: The rabbitmq user. Defaults toguestPassword: The rabbitmq user password. Defaults toguestRealm: The http realm for authentication. Defaults toRabbitMQ ManagementScheme: The protocol that the rabbitmq management API is running on. Defaults tohttpHost: The hostname that the rabbitmq server running on. Defaults tolocalhostPort: The port that the rabbitmq server is listening on. Defaults to15672ValidateCerts: You can ignore verifying the SSL certificate if you set it tofalse. Defaults totrueVHostPrefix: Arbitrary string to prefix the vhost name with. Defaults to NoneIgnore: The queue to ignore, matching by Regex.  See example.Seethis examplefor further details.NodesFor each node the following statistics are gathered:disk_free_limitfd_totalfd_usedmem_limitmem_usedproc_totalproc_usedprocessorsrun_queuesockets_totalsockets_usedQueuesFor each queue in each vhost the following statistics are gathered:
_NOTE_: The/vhost name is sent asdefaultmessage_statsdeliver_getdeliver_get_detailsrategetget_detailsratepublishpublish_detailsrateredeliverredeliver_detailsratemessagesmessages_detailsratemessages_readymessages_ready_detailsratemessages_unacknowledgedmessages_unacknowledged_details
* ratememoryconsumersconsumer_utilisationExchangesFor each exchange in each vhost the following statistics are gathered:
_NOTE_: The/vhost name is sent asdefaultdisk_freedisk_free_limitfd_totalfd_usedmem_limitmem_usedproc_totalproc_usedprocessorsrun_queuesockets_totalsockets_usedCreditsThis package was created withCookiecutterand thecookiecutter-pypackageproject template.History0.1.0 (2014-09-18)First public release.
Package: collectd-rabbitmq-monitoring
OverviewThis plugin provides metrics from a running Rabbitmq cluster via
the rabbitmq management plugin API.Sample GraphConfigurationAssuming you have collectd installed already, append the following
plugin details to your collectd.conf config file.  Adjust the
configuration items (interval, host, port, username, password,
message_count) as you see fit.```
<LoadPlugin python>
  Globals true
</LoadPlugin>

<Plugin python>
  LogTraces true
  Interactive false
  Import "collectd_rabbitmq_monitoring"
  <Module collectd_rabbitmq_monitoring>
    # Adjust these parameters for your install:
    interval 10
    host "overcloud-controller-0.internalapi.localdomain"
    port 15672
    username guest
    password guest
    # Omit message_count if you do not want to count any messages on
    # specific queues.
    message_count "metering.sample" "notifications.info"
  </Module>
</Plugin>
```Install the Rabbitmq management plugin```
[root@overcloud-controller-0 ~]# rabbitmq-plugins enable rabbitmq_management
```Install plugin```
[root@overcloud-controller-0 ~]# pip install collectd-rabbitmq-monitoring
```Restart collectd[root@overcloud-controller-0 ~]# systemctl restart collectdView metrics on Rabbitmq in your TSDBResourcesRabbitmq.comCollectd.org
Package: collectd-swift-stat
OverviewThis plugin uses the swift client in order to issue aswift statagainst a
specific swift account.Sample GraphsMetricsswift_stat/gauge-$PREFIX-bytesswift_stat/gauge-$PREFIX-containersswift_stat/gauge-$PREFIX-objects$PREFIX will be the configured Prefix value in the plugin configuration in
collectd.confInstall / ConfigurationAssuming you have collectd installed already, append the following
plugin details to your collectd.conf config file.  Adjust the
configuration items as you see fit.  The plugin must be able to
subprocess the ceph and rados commands.<LoadPlugin python>
  Globals true
</LoadPlugin>

<Plugin python>
  LogTraces true
  Interactive false
  Import "collectd_swift_stat"
  <Module collectd_swift_stat>
    Interval 30
    Prefix "gnocchi"
    User "gnocchi"
    Password "xxxxxxxxxxxxxxxxxxxxxxxxx"
    AuthURL "http://172.21.0.10:5000/v3"
    AuthVersion "3.0"
    Project "service"
  </Module>
</Plugin>Install plugin[root@overcloud-controller-0 ~]# pip install collectd-swift-statRestart collectd[root@overcloud-controller-0 ~]# systemctl restart collectdView metrics on the configured Swift account in your TSDBResourceswiki.openstack.org/wiki/SwiftCollectd.org