Enterprise scalable realtime graphing

Edit Package graphite-web
https://github.com/graphite-project/graphite-web

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. The web frontend provides user interfaces for visualizing this data in graphs as well as a simple URL-based API for direct graph generation.

Graphite's design is focused on providing simple interfaces (both to users and applications), real-time visualization, high-availability, and enterprise scalability.

Refresh
Refresh
Source Files
Filename Size Changed
1.1.4.tar.gz 0001435791 1.37 MB
README.SUSE 0000000808 808 Bytes
graphite-web-fix_invalide_theme.patch 0000000605 605 Bytes
graphite-web-path.patch 0000009551 9.33 KB
graphite-web-rpmlintrc 0000000118 118 Bytes
graphite-web.changes 0000001470 1.44 KB
graphite-web.spec 0000007601 7.42 KB
Revision 1 (latest revision is 12)
Lars Vogdt's avatar Lars Vogdt (lrupp) accepted request 646036 from Eric Schirra's avatar Eric Schirra (ecsos) (revision 1)
New package need for icingaweb2-module-graphite

- update to 1.1.4
- rebase spec
- drop usr-share.patch because no more need
- add graphite-web-path.patch to preallocate graphite paths.
- use apache.conf from upstream
- change initial database commond to wich are descriped in 
  upstream doc.
- Fix startup error with change of rights for /var/lib/graphite/storage
- Ensure /var/lib/graphite/graphite.db is writable by apache user
- Prefer /usr/share/graphite, /etc/graphite etc. to match python
  site-packages directory naming, and also what calamari-server expects
  (this obsoletes earlier graphite-web change).
- Ensure `manage.py syncdb` is invoked correctly on first install
- Generate random SECRET_KEY on install
- Use /usr/share/graphite-web instead of /usr/share/graphite
- Initial SUSE packaging
Comments 0
openSUSE Build Service is sponsored by