This is template project that can be used to do the following with xMatters:

• Backup
• Restore
• Report
• Load
• Synchronize
• Migrate

The source of the data can be:

• A file
• Multiple files
• Another xMatters instance

The included examples are explained below. This project leverages xmtoolbox which is a npm package that makes it simpler to interact with the xMatters APIs and contains some utilities to assist with the movement of xMatters. Please refer to the xmtoolbox documentation available https://xmatters.github.io/xmtoolbox/ for other available functionality. xMatters REST API Documentation is available here https://xmatters.github.io/xmtoolbox/ xmtoolbox API docs | xmtoolbox@npm | xmtoolbox@github

This project can be run locally or deployed to a PaaS solution such as Heroku.

This package has the ability to modify data within your xMatters for good and bad. Please use it responsibly. Test in non-production and don't make unnecessary requests against your xMatters instance. Also be aware that according to xMatters, the inbound events and flow posts share the same bandwidth any interactions with the xMatters APIs, including the ones this package uses, so again please use responsibly. This project is an open source project and is not owned or supported by xMatters directly. If you are having trouble please refer to or open a github issue.

1. Click "Use This Template" from the github page, download, or clone this project to a local directory. git clone https://github.com/brannonvann/xmtoolbox-quick-start.git FOLDER_NAME_HERE
2. Install latest node.js
3. Run npm install from the directory where this was downloaded locally in a MacOS or Linux terminal or Windows command prompt.
4. Rename the provided example.config.js to config.js and updated with your credentials. If you are using environment variables to store your credentials, no further update is needed.
5. Run one of the examples node Backup.js

This project is a node package. To run an example follow the setup as described above and change the 'Backup' in the last step to the name of the example you want to try.

The examples are setup to leverage a config.js file for storing xMatters credentials or accessing your credentials stored in environment variables. If you choose to implement another solution for storing your credentials you will just need to make sure the credentials are passed when creating your environment as the example.config.js demonstrates.

Please keep in mind that this information needs to remain secure. Choose a solution that is secure in your situation. The config.js file is only used to make it easy to try multiple examples. There is no dependency on it, if you choose to configure the credentials or environment another way.

You can update the referenced packages, including xmtoolbox, by using the command npm update.

The examples explained below cover a small subset of the available functionality. There is a lot more data that can be synchronized, migrated, backed-up, restores, and reported on, with a small change to the scripts. These examples have been created to cover the most common situations. Refer to the xmtoolbox documentation for more information on the any of the data modules that are leveraged by this project.

This is an example of sending data to a xMatters Workflow Flow and reporting on data within xMatters. In this case it's looking for groups that contain groups but this could be any supported object and with any qualifiers.

This will extract all groups from your production environment and write the contents to a CSV file containing the group name and the supervisors.

In this script, the xmtoolbox is used to get a single group named "Database Operations" from xMatters and writes to the console.

This is an example of synchronizing a xMatters production environment to non-production xMatters instance. It synchronizes people in non-mirror mode. Data will not be deleted from either environment however where matching records are found it will be updated in the destination. A default supervisor will be used in the event any matching supervisors are not found in non-production.

Running this will remove users and groups contained in the example files. It also will remove any unused sites.

This is an example of extracting data from your xMatters instance. The data will be saved as a single JSON file. This json file can be read in as used to synchronize data into a xMatters instance. An example of that is available in Restore.js.

This demonstrates how to read in a single JSON file that has many data objects represented in it and synchronizing a few of those data elements into an xMatters instance. The file is the same one that is produced in the Backup.js example.

This demonstrates how to read in a csv (Comma Separated Value) file for people and devices and a csv file for groups. Then, synchronizing a that data into an xMatters instance. The referenced example files are included in the example directory of this project.

This is an example of synchronizing the xMatters Users Export formatted file to xMatters. This can be created from scratch or downloaded from xMatters using the Users --> Export.

This will extract all groups from your production environment and write to a very simple HTML page in table form.