Puppet dashboard manual

Skip to content. Star 7. Branches Tags. Could not load branches. Could not load tags. Latest commit. Git stats commits. Failed to load latest commit information. View code. The value should match a time interval, such as 5s , 10m , or 1h. Determining where Telegraf runs Telegraf can be configured to run on the Dashboard node, or on each Puppet Infrastructure node. Please verify its path and try again. About A module for managing the installation and configuration of metrics dashboards for Puppet services.

Resources Readme. Code of conduct. Releases 3 v2. Nov 4, Packages 0 No packages published. Contributors If your infrastructure is big the database will eventually become very large more than 50GB. The Puppet Dashboard manual is an extracted version of the Puppet Dashboard documentation which was hosted on the Puppetlabs homepage.

This project uses the Silk icons by Mark James. Thank you! Skip to content. Star The Puppet Dashboard is a web interface providing node classification and reporting features for Puppet, an open source system configuration management tool View license.

Branches Tags. Could not load branches. Could not load tags. Latest commit. The best way to install Dashboard is with Puppet Labs' official package repositories. This will automatically handle Dashboard's dependencies, and will make for easier upgrades when new versions are released. Before installing, follow the instructions here to enable the Puppet Labs package repository for your system.

If you're unable to use the Dashboard packages on your system, the next best way to install Dashboard is from the Puppet Labs Git repo. The advantage of using Git is that you have an easier upgrade path: you don't have to manually remember which files to preserve when upgrading, and the actual process of upgrading is much simpler.

The disadvantage is that it basically turns Git into another dependency. See [upgrading][] for more details. If you haven't installed Dashboard from a package, you must create a user and group for Dashboard and chown all its files to be owned by that user and group:. If you prefer not to use Git, you can simply download the most recent release of Puppet Dashboard and extract it into your install location:.

If you haven't installed Dashboard from a package, you must create a user and group for Dashboard and chown all its files to be owned by that user and group. This file should be a YAML hash with one key for each of the standard Rails environments: production, development, and test. You will likely only ever be using the production environment. You should not use the same database for the test environment, as it gets destroyed every time the tests are run. Each environment in the database.

At the moment, adapter can only be mysql , and encoding should always be utf8. Do not give Dashboard the keys to MySQL's root user account create a new database user for it preferably named "dashboard" and choose a secure password. Since the database. If you've created the file while logged in as a normal user, be sure to chown it to the Dashboard user. The general settings file should be a YAML hash. When first configuring Dashboard, you should simply make a copy of settings.

Dashboard needs a user, a password, and at least one database. Create these using the names and passwords you chose in your database. This will require that you use some external MySQL administration utility; 1 in the standard command-line mysql client, the commands will look something like this:. See the MySQL manual for more information. After creating the database and user, you'll need to configure MySQL's maximum packet size to permit larger rows in the database.

Either restart the MySQL server for this setting to take effect, or run the following command from the mysql client:. Once Dashboard has its database, it can create its tables, but this has to be done manually with the db:migrate rake task.

For typical use with the production environment:. For developing the software using the development and test environments:. This will start a Dashboard instance on port using the "production" environment.