Skip to content
/ smetrics Public

Smetrics - use Google Sheets to store metrics data over time

License

Notifications You must be signed in to change notification settings

uglow/smetrics

Repository files navigation

smetrics

NPM Version semantic-release Coverage Status Dependencies status Dev-dependencies status Commitizen friendly

Records metrics to your Google Sheets spreadsheet

smetrics is designed to persist metrics (test runs, test coverage, build times, load times, etc) using Google Sheets. Google Sheets provides cloud-storage for the data, allowing you to see the changes in the metrics over time (and graph them yourself).

Install

npm install smetrics --dev

Usage

// File: processMetrics.js
// Lets say you've just built your code, run your unit and performance tests.
// Now you want to persist the results somewhere so you can see the changes over time.

import fs from 'fs';
import * as smetrics from '../src/index.js';

// See Authentication section for how to generate this information
const creds = fs.readFileSync('./google-generated-creds.json').toString();
// OR, if you cannot save the file locally (like on heroku)
const options = {
  clientEmail: process.env.SMETRICS_GOOGLE_SERVICE_ACCOUNT_CLIENT_EMAIL,
  privateKey: process.env.SMETRICS_GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY,
  dateTimeFormat: 'googleDate', // defaults to 'milliseconds',
  filePath: '/tmp/yourfile.json' // defaults to CWD + 'smetrics.json'
}

// Gather all the metrics then commit them to Google Sheets
addUnitTestMetrics();

// Commit the changes (async - returns a promise)
smetrics.commit('<spreadsheet key>', options)
  .catch((err) => {
    console.log(err);
  });


function addUnitTestMetrics() {
  const stats = { numTotalTests: 100, numPassedTests: 99 };
  const tabName = 'My Stats';
  
  smetrics.addMetric(tabName, 'Total tests', stats.numTotalTests);
  smetrics.addMetric(tabName, 'Passed tests', stats.numPassedTests);
}

Important

The order that metrics are added is significant. If you decide to change the order that you add metrics, you should open the corresponding Google Sheet and change the column-order to match your new metric-capturing order.

Usage within AWS Lambda functions

Because this library persists state to a file, you need to specify the filePath when calling addMetric and commit with a path underneath the /tmp directory:

import fs from 'fs';
import * as smetrics from '../src/index.js';

// NOTE: filePath is specified explicitly, under the '/tmp' folder
smetrics.addMetric(tabName, 'Total tests', stats.numTotalTests, { filePath: '/tmp/smetrics.json' });

// See Authentication section for how to generate this information
const creds = fs.readFileSync('./google-generated-creds.json').toString();
// OR, if you cannot save the file locally (like on heroku)
const options = {
  clientEmail: process.env.SMETRICS_GOOGLE_SERVICE_ACCOUNT_CLIENT_EMAIL,
  privateKey: process.env.SMETRICS_GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY,
  dateTimeFormat: 'googleDate',

  // NOTE: filePath is specified explicitly:
  filePath: '/tmp/smetrics.json'
}
smetrics.commit('<spreadsheet key>', options); // Async - returns a promise 

API

addMetric(sheetName, column, value, options) : object

Adds a metric to the temporary metric-file

  • sheetName The name of the sheet within the spreadsheet
  • column The name of the column within the sheet
  • value The value to store
  • options (optional):
    • timestamp The timestamp to associate with the metric. Defaults to the current time.
    • filePath The file path to write the metric data to. Defaults to current working directory 'smetrics.json'

    commit(spreadsheetKey, options) : void

    • spreadsheetId The SpreadsheetId

    Reads the metrics in the metric-data file ('smetrics.json') and persists it to the designated Google Sheet.

    • sheetName The name of the sheet within the spreadsheet
    • options :
      • clientEmail This value is available in the JSON file that you can download when setting up Authentication with a service account.
      • privateKey This value is available in the JSON file that you can download when setting up Authentication with a service account.
      • dateFormat <string|function> Default value 'milliseconds'.

      The default format for DateTime columns is milliseconds, which is the number of milliseconds since the epoch (e.g. 1537165777561, which is equivalent to Mon Sep 17 2018 16:29:37 GMT+1000 (Australian Eastern Standard Time)).

      Alternately, you can specify the format as googleDate, which formats the date as dd-mon-yyyy hh:mm:ss. Google sheets interprets this string as a date, and can be used correctly when the data is charted. You may need to manually format the DateTime column as a 'Date Time' in the Google Sheet (once-only).

      Lastly, you can supply a function for dateFormat, which has the signature (timeMillis: Number) => any.

      How it works

      Every time a metric is added, a temporary file (smetrics.json, example) is created/updated in your current working directory with the metric name and a value:

      // smetrics.json:
      [
        [
          { metric: 'Test Time (s)', value: 26 }, 
          { metric: 'Time to Interactive (ms)', value: 503 },
          // ...
        ]
      ]

      When commit(spreadsheet, creds) is called, the smetrics.json file is appended to the specified spreadsheet as a new row, with the first column containing a date-time stamp (generated using Date.now()).

      Hacking smetrics

      Since this package ultimately processes a file called smetrics.json when smetrics.commit(...) is called, you are welcome to write to this file yourself, rather than call smetrics.addMetric(...). If you stick to the same format as this example, and follow the authentication process, you may even add multiple rows of metrics in one go (Why would you want to? I'm not sure).

      Authentication

      Service Account (recommended method)

      This is a 2-legged OAuth method and designed to be "an account that belongs to your application instead of to an individual end user". Use this for an app that needs to access a set of documents that you have full access to. (read more)

      Setup Instructions

      1. Go to the Google Developers Console
      2. Select your project or create a new one (and then select it)
      3. Enable the Drive API for your project
        1. In the sidebar on the left, expand APIs & auth > APIs
        2. Search for "sheets"
        3. Click on "Google Sheets API"
        4. Click the blue "Enable API" button
      4. Create a service account for your project:
        1. In the sidebar on the left, expand IAM & Admin > Service Accounts
        2. Click "Create Service Account" button
        3. Enter the service account name & a description for step 1 and press Create.
        4. Skip steps 2 & 3 by pressing Cancel
        5. In the Service Accounts panel, select Actions > Manages Key
        6. Press Add Key > Create New Key
        7. Select the "JSON" key type option
        8. Click blue "Create" button.

      Your JSON key file is generated and downloaded to your machine (it is the only copy!) note your service account's email address (also available in the JSON key file) Share the doc (or docs) with your service account using the email noted above.

      The private_key field in the JSON file that is the private key.

      Sharing the sheet with the service account

      1. Open the Google Sheet
      2. Press the Share button.
      3. In the Share dialog, type the service accounts email: your-service-account-name@google-app.iam.gserviceaccount.com
      4. Press Send.

      Spreadsheet ID

      The Spreadsheet ID can be found in the URL of the spreadsheet.

      E.g. docs.google.com/spreadsheets/d/:spreadsheetID:/edit#gid=0

      Graphing the results

      Once you have the data in your spreadsheet, you can provide read-access to allow other tools

      Contributing

      See CONTRIBUTING.md.

      License

      This software is licensed under the MIT Licence. See LICENSE.

About

Smetrics - use Google Sheets to store metrics data over time

Resources

License

Stars

Watchers

Forks

Packages

No packages published