Source: graphite-api
Section: web
Priority: optional
Maintainer: Debian Graphite Group <team+debian-graphite-team@tracker.debian.org>
Uploaders: Vincent Bernat <bernat@debian.org>
Build-Depends: debhelper (>= 9),
               dh-python,
               python3,
               python3-flask,
               python3-cairocffi,
               python3-xcffib,
               python3-pyparsing,
               python3-tz,
               python3-tzlocal,
               python3-yaml,
               python3-six,
               python3-structlog (>= 19.2.0),
               python3-setuptools,
               python3-sphinx, python3-sphinx-rtd-theme
Standards-Version: 3.9.8
Homepage: https://github.com/brutasse/graphite-api/
Vcs-Git: https://salsa.debian.org/debian-graphite-team/graphite-api.git
Vcs-Browser: https://salsa.debian.org/debian-graphite-team/graphite-api

Package: graphite-api
Architecture: all
Depends: ${misc:Depends},
         ${python3:Depends},
         ${sphinxdoc:Depends},
         adduser
Suggests: gunicorn3 | uwsgi-plugin-python3 | libapache2-mod-wsgi-py3
Description: Enterprise Scalable Realtime Graphing (API-only frontend)
 Graphite consists of a storage backend and a web-based visualization
 frontend. Client applications send streams of numeric time-series
 data to the Graphite backend (called carbon), where it gets stored in
 fixed-size database files similar in design to RRD.
 .
 Graphite-API is an alternative to Graphite-web, without any built-in
 dashboard. Its role is solely to fetch metrics from a time-series
 database and rendering graphs or JSON data out of these time
 series. It is meant to be consumed by any of the numerous Graphite
 dashboard applications.