Set up Transposit

Note: To use Transposit, please request access. For customers already granted access, please follow the instructions below.

1. Add the Transposit app to your Slack workspace #

Go to Settings > Team and click on “Add to workspace” in the Slack section. Authorize the Slack workspace you want to use with Transposit. Ensure you have permission to install apps in your Slack workspace.

2. Invite team members #

Send the link to the sign in page to your team members. Make sure that your team members select "Sign in with Slack", using the same Slack workspace, and they'll be added to your Transposit team.

3. Add a trigger #

To receive incidents, you'll need to create a trigger. Go to Settings > Triggers and click “Add trigger”. For integrator, choose "A Hello World integrator to get started", and enter a Slack channel. (Note that the Slack channel must already exist; create it before adding the trigger.)

4. Test the trigger #

Copy the Endpoint URL of your trigger to your clipboard, and run curl [endpoint_url] on the command line. This should output a “Hello World” message into the Slack channel which you previously defined for your trigger.

5. Take a look at your first runbook #

Runbooks are step-by-step instructions for incident resolution. A runbook can be browsed directly from an incident message in Slack.

Navigate to Runbooks in Transposit to find your existing runbooks.

Open the “Deploy using AWS Opsworks” runbook to learn how Runbooks are constructed.

Runbooks consist of a title (the top-level heading), any number of steps steps (second-level headings), instructions written in plain text, plus any number of actions.

Click “Edit” to take a look at a runbook's markdown source.

6. Add integrations #

Performing the actions in your runbooks requires setting up the integrations with which your actions interact.

For example, to execute an action that performs a deploy with AWS Opsworks, you'll need to have enabled the AWS Opsworks integration, added authorization, plus any configuration required.

Find integrations at Settings > Integrations, click Enable to add an integration, and then click Connect to add authorization.

7. Test a runbook #

Trigger an alert (see step 4 above). Find the alert message in Slack, and click “Create Incident”.

A new channel for the incident will be created. Click “Runbooks” and browse available runbooks.

Select the new runbook you created in step 7.

The runbook will appear in Slack, and you can click through the different steps and execute the actions you added.

8. Sign in to AWS Sandbox #

Sign in to https://transposit-sandbox-mooreds.signin.aws.amazon.com/console with the test credentials we provided you, and username try-transposit.

Navigate to Opswork and click on “My Sample Stack (Linux)”.

In “Deployments and Commands” you can see that the Node.js app is now deploying.

After a few minutes the status should change to “for-opsworks deployed”.

9. Close incident and check incident timeline #

Congratulations! You resolved your first incident in Transposit. In your Slack incident channel, you can scroll up to the original message, and click on “Close MC Incident”.

The Transposit bot will confirm closure of the incident.

Click on the link to view the incident timeline.

10. Add an integration #

To make Transposit work with your own infrastructure, connect your existing systems with integrations.

Scroll down to AWS Opswork:

Click on Disconnect:

Click on Configuration:

Add your AWS Region (for example, us-east-1) and save.

Click on Connect.

Insert your AWS credentials and save.

11. Update your deploy_opsworks action #

Navigate to Actions and click “deploy_opsworks”.

In order for the action to work with your infrastrcture, you'll need to update the environment variables. Log in to AWS Opsworks, select your Stack and open the Stack Settings. Copy the OpsWorks ID and paste it into the stack_id field.

Navigate to Apps in the AWS Opsworks Stack Settings and select your app. Copy the OpsWorks ID and paste it into the application_id field.

Click Save to update the action. Go back to step 6 above and test the deploy_opswork action from your runbook. Sign in to AWS with your own credentials and verify that the action worked and that the Node.js app is being deployed.

---

Create your own actions and integrations #

1. Add your own action #

To add your own action, first ensure the service you want to use is connected. Navigate to Integrations, enable and connect to Opsgenie.

After OpsGenie is connected, go to the Actions page and create an action.

Click on “Choose Workflow”. For this example, choose “Ack Opsgenie Alert”. If this is your first time using this workflow, pick the most recent version from the version selector. Click on “Save” to create the action.

2. Create a runbook from scratch #

Go to Runbooks and click New Runbook. Enter a name for your runbook and click Create Runbook. Use markdown to write your first runbook.

An first-level markdown heading # defines the runbook title. Use second-level headings ## to define runbook steps.

# Alarm /500/

## Step 1
Look at this alert, see if it belongs to your team. If not, route to @oliver on Slack

## Step 2
If you determined that you should take care of the alert, acknowledge it.

Click “Add action” to insert an action in your runbook.

Select “global_opsegenie” from the dropdown and click Add.

Save the runbook.

---

Create a Opsgenie trigger #

In order for an external service like Opsgenie to trigger an incident in Transposit, set up a webhook between Opsgenie and Transposit.

First, ensure you connected Opsgenie on the integrations page.

Next, create a new trigger.

Click “Add trigger” on the Triggers page. Select “Opsgenie Integrator for Posting Alerts” in the Integrator dropdown. Enter an existing Slack channel and click “Add”.

A new endpoint URL is created. Click to copy the URL and paste it into a webhook in the Opsgenie Integrations settings. Learn more about webhooks and Opsgenie.