fspringveldt/silverstripe-module-metrics

Experimental module which provides metrics on SilverStripe modules in use

dev-master 2017-11-10 02:44 UTC

Requires

• maciejczyzewski/bottomline: dev-master
• silverstripe/framework: ^3

BSD-3-Clause

• cms
• silverstripe
• module metrics

README

This module aims to supply dev-ops teams with information related to SilverStripe module usage across many sites. It does this by analysing a modules DataObjects and DataExtension classes.

1. DataObjects: if at least one of them has rows, it assumes the module is in use
2. DataExtensions: if any new columns are introduced by these with non-null values, it assumes the module is in use.

NB: DataExtension::augmentDataBase() also mutates the database (see Versioned or Translatable), but there is no structured way to determine what those mutations are. For these modules some analysis at a module-level is required to determine which table's existence can reliably determine the module's usage.

Requirements

• SilverStripe ^3.1

Installation and setup

1. Clone down the repository to your /tmp/ss-module-metrics directory

git clone https://github.com/fspringveldt/silverstripe-module-metrics /tmp/ss-module-metrics

1. Create an simple text file in the same directory you cloned this project to (i.e. /tmp/ss-module-metrics), into which you put paths to all the SilverStripe directories you would like to include in your scan. An example below of a file called input.txt, with the following content:

$HOME/www/ss-site-1
$HOME/www/ss-site-2

1. Run the following from your bash command prompt to output its results:

cd /tmp/ss-module-metrics/ && >output.txt && awk '{printf "php cli-module-metrics.php %s >> output.txt\n", $0}' input.txt | sh

N.B. By including the manifest-like SilverStripe files (Core.php) from your script you introduce a possibility of having cache files re-generated, which could cause problems for these websites to frontend users. Care must therefore be taken to ensure that the script is run as the web server's user.

1. This command runs the module-usage inspector on all the sites specified in input.txt, sends the output in JSON format to a file called /tmp/ss-module-metrics/output.txt. The below fields are output per site, per module. This file can be imported to MySQL for further analysis.

[
  {
      "Site": "http:\/\/dev.ss3.local",
      "ModuleName": "userforms",
      "InUse": 1,
      "UsageType": "DataObject",
      "RecordsFound": 2,
      "FieldInUse": null,
      "TableInUse": "EditableCheckbox",
      "LastEdited": "2017-08-01 23:24:32"
  }
]

Field descriptions

• Site: The output of Director::baseURL()
• ModuleName: The actual module
• InUse: Either 0, 1 or 2. A value of 2 indicates the module has no Database interaction
• UsageType: Can be one of either
  • Extension - an extension column introduced by this module has valid data (i.e. not null and <> 0)
  • DataObject - a dataobject introduced byt this module has data
  • AugmentDatabase - rows were found in a table introduced through DataExtension::augmentDatabase()
  • NoDBInteraction - no database interaction was found within this module
• RecordsFound: The number of records found in the case of a DataObject
• FieldInUse: The first DataExtension field found with a non-null value.
• TableInUse: The first database table found with a row
• LastEdited: The LastEdited column in the table

Sample results formatted as table

License

See License

We have included a 3-clause BSD license you can use as a default. We advocate for the BSD license as it is one of the most permissive and open licenses.

Feel free to alter the license.md to suit if you wan tto use an alternative license. You can use choosealicense.com to help pick a suitable license for your project.

Maintainers

• Franco Springveldt [e-mail]

Bugtracker

Bugs are tracked in the issues section of this repository. Before submitting an issue please read over existing issues to ensure yours is unique.

If the issue does look like a new bug:

• Create a new issue
• Describe the steps required to reproduce your issue, and the expected outcome. Unit tests, screenshots and screencasts can help here.
• Describe your environment as detailed as possible: SilverStripe version, Browser, PHP version, Operating System, any installed SilverStripe modules.

Please report security issues to the module maintainers directly. Please don't file security issues in the bugtracker.

Development and contribution

If you would like to make contributions to the module please ensure you raise a pull request and discuss with the module maintainers.