graphite-web-0.9.15/ 0000755 0001750 0001750 00000000000 12626126564 013204 5 ustar jonas jonas graphite-web-0.9.15/PKG-INFO 0000644 0001750 0001750 00000000423 12626126564 014300 0 ustar jonas jonas Metadata-Version: 1.0 Name: graphite-web Version: 0.9.15 Summary: Enterprise scalable realtime graphing Home-page: http://graphite.readthedocs.org Author: Chris Davis Author-email: chrismd@gmail.com License: Apache Software License 2.0 Description: UNKNOWN Platform: UNKNOWN graphite-web-0.9.15/INSTALL 0000644 0001750 0001750 00000013717 12626124266 014243 0 ustar jonas jonas ExtJS ------------------------------------------------------------------------------- Graphite used to require an external Ext installation but now Ext is bundled with Graphite as allowed by the Ext FLOSS license exemption described here: http://extjs.com/products/floss-exception.php Run check-dependencies.py ------------------------------------------------------------------------------- This will check for graphite's runtime dependencies and let you know which you are missing. Download and install these modules and re-run check-dependencies.py until it detects all the required modules. Graphite requires: python2.4 or greater (python 2.5 or greater is required for AMQP support) whisper (available for download on the graphite project page) pycairo (with PNG backend support) django json (standard in python2.6) or simplejson mod_wsgi (optional, recommended) or mod_python (optional) python-ldap (optional - needed for ldap-based webapp authentication) python-memcached (optional - needed for webapp caching, big performance boost) python-sqlite2 (optional - a django-supported database module is required) Run setup.py ------------------------------------------------------------------------------- First take a look at the 'prefix' option in the setup.cfg file. This specifies where the graphite application will be installed. Note that if you plan on installing carbon on the same server you should use the same prefix for it. The prefix where graphite is installed under where be referred to as $GRAPHITE_ROOT from here on. Also, do NOT change the 'install-lib' option unless you really know what you are doing. Initialize the Database ------------------------------------------------------------------------------ Once you have installed graphite you must initialize its database like so: export PYTHONPATH=$PYTHONPATH:$GRAPHITE_ROOT/webapp cd $GRAPHITE_ROOT/webapp/graphite/ sudo python manage.py syncdb Note that if you wish to use a custom database setup (like MySQL or Postgres) you will need to make those configuration changes first. See the "Custom Database Configuration" section below for details. Setup Filesystem Ownership ------------------------------------------------------------------------------ The user that apache runs as will need write access to the following directories: $GRAPHITE_ROOT/storage/ $GRAPHITE_ROOT/storage/log/webapp/ As well as write access to the following files: $GRAPHITE_ROOT/storage/graphite.db The apache user must also have read access to $GRAPHITE_ROOT/storage/whisper/ Apache Configuration ------------------------------------------------------------------------------- When using apache there are two modules available to provide support for python web application. Graphite currently provides example configurations for both of these modules. Of the two mod_wsgi is the most up to date and actively maintained so it's highly recommended if you are starting afresh. Apache Configuration for Mod_wsgi (recommended) ------------------------------------------------------------------------------- If you are using mod_wsgi, Apache has to have mod_wsgi configured, this is usually done by including a line like the following in your httpd.conf: LoadModule wsgi_module modules/mod_wsgi.so Apache Configuration for Mod_python ------------------------------------------------------------------------------- If you choose to use mod_python, Apache has to have mod_python configured, this is usually done by including a line like the following in your httpd.conf: LoadModule python_module modules/mod_python.so General Apache Configuration ------------------------------------------------------------------------------- Once you have configured the apache module you are using you should configure a vhost for graphite (technically it doesn't have to be a vhost but its good practice). This can be done one of two ways. The first way (highly preferred) is to include independent vhost configs. # This goes in httpd.conf Include /usr/local/apache2/conf/vhosts.d/*.conf Then simply drop your graphite vhost conf file into the vhosts.d/ directory (or whatever directory your system uses) and apache is ready. You can use either of the example vhost confs as a starting point (See the examples directory of this package and choose the correct one based on whether you are using mod_wsgi or mod_python.) The second approach is to copy the contents of your chosen graphite vhost conf file and insert it down at the end of your httpd.conf. Custom Database Configuration ------------------------------------------------------------------------------- By default, the graphite webapp uses a sqlite database. As long as you have the appropriate sqlite module installed, you should not need to do any additional database configuration. But if you wish to use a different database such as MySQL or Postgres, read on. After you setup your database server, create a database and a user with full privileges on that database. Now we put that information into the graphite webapp local_settings.py file. Edit the $GRAPHITE_ROOT/webapp/graphite/local_settings.py In particular you will need to uncomment and modify all of the settings that begin with "DATABASE_". Once you have done this, we need to tell Django to create our tables. cd $GRAPHITE_ROOT/webapp/graphite/ sudo python manage.py syncdb # you will be prompted to create an admin user, this is a good idea Restart apache and you should see the graphite webapp on the main page. If you encounter problems, you can increase the verbosity of error output by adding a "DEBUG = True" line to local_settings.py Next Steps - setup the backend (carbon) ------------------------------------------------------------------------------- Now you have finished installing the graphite webapp, the next thing to do is put some real data into it. This is accomplished by running the carbon-cache.py daemon and send it some data as demonstrated in the included ./examples/example-client.py Instructions for doing this in the README file. graphite-web-0.9.15/setup.cfg 0000644 0001750 0001750 00000000500 12626126564 015020 0 ustar jonas jonas [bdist_rpm] requires = Django => 1.1.4 django-tagging carbon whisper mod_wsgi pycairo pycairo-devel python-simplejson python-sqlite2 python-hashlib post-install = distro/redhat/misc/postinstall provides = graphite obsoletes = graphite <= 0.9.9 [install] prefix = /opt/graphite install-lib = %(prefix)s/webapp graphite-web-0.9.15/webapp/ 0000755 0001750 0001750 00000000000 12626126564 014462 5 ustar jonas jonas graphite-web-0.9.15/webapp/content/ 0000755 0001750 0001750 00000000000 12626126564 016134 5 ustar jonas jonas graphite-web-0.9.15/webapp/content/html/ 0000755 0001750 0001750 00000000000 12626126564 017100 5 ustar jonas jonas graphite-web-0.9.15/webapp/content/html/timeHelp.html 0000644 0001750 0001750 00000017547 12626124247 021547 0 ustar jonas jonas
Graphite uses an at-style time specification similar to that used by RRDTool. The specification is called ``at-style'' after the Unix command at(1)
that has moderately complex ways to specify time to run your job at a certain date and time. The at-style specification consists of two parts: the TIME REFERENCE specification and the TIME OFFSET specification.
The time reference specification is used, well, to establish a reference moment in time (to which the time offset is then applied to). When present, it should come first, when omitted, it defaults to now. On its own part, time reference consists of a time-of-day reference (which should come first, if present) and a day reference.
The time-of-day can be specified as HH:MM, HH.MM, or just HH. You can suffix it with am or pm or use 24-hours clock. Some special times of day are understood as well, including midnight (00:00), noon (12:00) and British teatime (16:00).
The day can be specified as month-name day-of-the-month and optional a 2- or 4-digit year number (e.g. March 8 1999). Alternatively, you can use day-of-week-name (e.g. Monday), or one of the words: yesterday, today, tomorrow. You can also specify the day as a full date in several numerical formats, including MM/DD/[YY]YY, DD.MM.[YY]YY, or YYYYMMDD.
NOTE1: this is different from the original at(1)
behavior, where a single-number date is interpreted as MMDD[YY]YY.
NOTE2: if you specify the day in this way, the time-of-day is REQUIRED as well.
Finally, you can use the words now, start, or end as your time reference. Now refers to the current moment (and is also the default time reference). Start (end) can be used to specify a time relative to the start (end) time for those tools that use these categories.
Month and day of the week names can be used in their naturally abbreviated form (e.g., Dec for December, Sun for Sunday, etc.). The words now, start, end can be abbreviated as n, s, e.
The time offset specification is used to add/subtract certain time intervals to/from the time reference moment. It consists of a sign (+ or -) and an amount. The following time units can be used to specify the amount: years, months, weeks, days, hours, minutes, or seconds. These units can be used in singular or plural form, and abbreviated naturally or to a single letter (e.g. +3days, -1wk, -3y). Several time units can be combined (e.g., -5mon1w2d) or concatenated (e.g., -5h45min = -5h-45min = -6h+15min = -7h+1h30m-15min, etc.)
NOTE3: If you specify time offset in days, weeks, months, or years, you will end with the time offset that may vary depending on your time reference, because all those time units have no single well defined time interval value (1 year contains either 365 or 366 days, 1 month is 28 to 31 days long, and even 1 day may be not equal to 24 hours twice a year, when DST-related clock adjustments take place). To cope with this, when you use days, weeks, months, or years as your time offset units your time reference date is adjusted accordingly without too much further effort to ensure anything about it (in the hope that mktime(3)
will take care of this later). This may lead to some surprising (or even invalid!) results, e.g. 'May 31 -1month' = 'Apr 31' (meaningless) = 'May 1' (after mktime(3)
normalization); in the EET timezone '3:30am Mar 29 1999 -1 day' yields '3:30am Mar 28 1999' (Sunday) which is an invalid time/date combination (because of 3am -> 4am DST forward clock adjustment, see the below example).
In contrast, hours, minutes, and seconds are well defined time intervals, and these are guaranteed to always produce time offsets exactly as specified (e.g. for EET timezone, '8:00 Mar 27 1999 +2 days' = '8:00 Mar 29 1999', but since there is 1-hour DST forward clock adjustment that occurs around 3:00 Mar 28 1999, the actual time interval between 8:00 Mar 27 1999 and 8:00 Mar 29 1999 equals 47 hours; on the other hand, '8:00 Mar 27 1999 +48 hours' = '9:00 Mar 29 1999', as expected)
NOTE4: The single-letter abbreviation for both months and minutes is m. To disambiguate them, the parser tries to read your mind :) by applying the following two heuristics:
Final NOTES: Time specification is case-insensitive. Whitespace can be inserted freely or omitted altogether. There are, however, cases when whitespace is required (e.g., 'midnight Thu'). In this case you should either quote the whole phrase to prevent it from being taken apart by your shell or use '_' (underscore) or ',' (comma) which also count as whitespace (e.g., midnight_Thu or midnight,Thu).
Oct 12 -- October 12 this year
-1month or -1m -- current time of day, only a month before (may yield surprises, see NOTE3 above).
noon yesterday -3hours -- yesterday morning; can also be specified as 9am-1day.
23:59 31.12.1999 -- 1 minute to the year 2000.
12/31/99 11:59pm -- 1 minute to the year 2000 for imperialists.
12am 01/01/01 -- start of the new millennium
end-3weeks or e-3w -- 3 weeks before end time (may be used as start time specification).
start+6hours or s+6h -- 6 hours after start time (may be used as end time specification).
931225537 -- 18:45 July 5th, 1999 (yes, seconds since 1970 are valid as well).
19970703 12:45 -- 12:45 July 3th, 1997 (my favorite, and its even got an ISO number (8601)).
graphite-web-0.9.15/webapp/content/html/completerHelp.html 0000644 0001750 0001750 00000001611 12626124247 022564 0 ustar jonas jonaslfs busy