Skip to main content

Plugin Configuration

Some plugins may require additional configuration, e.g. they require reference to additional files.  An example of this is the CSV plugin by Marcus Olsson.

When selecting the CSV Plugin as a Data Source, the path to the CSV file is required, with a choice of HTTP or Local:


Local Data Source

By default, local data sources are not allowed.  It is possible to overcome this via the Grafana 'ini' file, however this has limitations.

The FileWave Grafana 'ini' file is defined as:


Enablement of Local files is achieved by adding the following into this file:

allow_local_mode = true

After doing so, the server service should be restarted:

fwcontrol server restart

Local files may now be accessed with this plugin.  However, the caveat is that this file is overwritten by the FileWave installer on each upgrade.  The outcome is the file must therefore be edited on each upgrade attempt.

HTTP Data Source

HTTP Data Source has no similar caveat.  If there is already an available HTTP share in-house, this could be utilised.  However, the FileWave Server could have the apache configuration adapted to include such files.

Configure Apache

This process will rely on Apache having access to a directory which serves these files.  This could either be one that already exists or configuration could be used to add a new directory to serve just the required files.

Recommendation would be to create a new directory.

This is editing FileWave Server files and folders.  FileWave upgrades can overwrite files, folders or expansion of product may include new files and folders.  Consider using a directory that is unlikely to clash with future updates.

In this example, the new chosen folder is:


'grafana_plugins_custom' does not yet exist.  Rather than just creating one custom plugin folder for all possible plugin use, in this example a subdirectory for the CSV files has been created.  Additional plugins that also required http file shares could use the same parent, but have their own subfolder.

The Apache file that can be edited to create new http file shares is:


As a FileWave Custom file, this will persist with Filewave upgrades.

Alias /plugins_custom /usr/local/filewave/grafana_plugins_custom/csv
<Directory "/usr/local/filewave/grafana_plugins_custom/csv">
Options Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all

Full details on each option can be found in the Apache Documentation

However, to highlight two key aspects.


This is the newly created directory from which the files may be shared from


When accessing the files from a URL, this is essentially a shortcut for the URL, which will be redirected internally to this folder on access.  In this instance, the alias (shortcut link) is:


Other options should be configured as required.

FileWave Server process should be restarted once configured:

fwcontrol server restart

Downloading CSV files

Once configured, CSV files may be populated into the newly created document.  For example:

# ls -l /usr/local/filewave/grafana_plugins_custom/csv
total 184
-rw-r--r--  1 root  _www  14425 Aug  3 17:06 admin.csv
-rw-r--r--  1 root  _www  19364 Aug  3 17:06 data.csv
-rw-r--r--  1 root  _www  36694 Aug  3 17:06 paint.csv
-rw-r--r--  1 root  _www  19345 Aug  3 17:06 video.csv

Test download may be achieved by way of the server URL appended with the alias.  For example if the server were called '', then the URL from the above configuration would be:

However, a file should be addressed directly.  Taking the paint.csv as an example:

Accessing this URL in a browser should show the contents or download the file.

Plugin Data Source

Now an Apache share has been created with populated files, a Data Source may be configured to use HTTP for access to the files.


Other Data Source settings should be configured as desired.