Data configuration

• Insight text: The message at the top of a chart, describing the metric’s value and trend
• Insight value: Where the metric is at currently
• Insight trend: Whether the overall trend over the date range has been up, down, or flat over the selected date range. This is indicated by the arrow. The arrow color changes depending on whether the trend is towards the target or away from it (for example, an upward trend for Merge Frequency will be green because more merges are generally better)
• Insight status: A combination of the insight value, trend, and the metric’s target. This is represented by thumb icons (see the top right corner of each metric card in the Trend Summary, or throughout the At a glance section):
  • 

    The insight value is outside of the target and not getting closer to it

  • 

    The insight value is outside of the target zone but trending towards it, or within the target zone but close to the threshold

  • 

    The insight value is well within the target

Any changes to custom targets will immediately affect the insights (text, value, trend, and status) and Actions in the app. Of course, the time range of data will also affect insights and Actions, in this case, it's important to know that the At a glance view and Trend Summary behave differently.

At a glance view

As this view is designed to be a high-level overview, the date range is fixed to the last 6 weeks. The insights and Actions are only affected by changing custom targets.

In other words, changes to selected dates in the Trend Summary section will not affect this view.

Trend Summary

As this view is designed to help teams take action with granular data, the date range can be modified. The insights and Actions are therefore affected by both changing dates and changing custom targets.

1. Settings > Targets page
   

   Navigate to Settings > Targets  or click the “Customize targets” button on the top right of the At a glance section on the My Insights homepage. Customizing a target is as simple as clicking on a target and editing it!
   
   To be clear, in this table:
   

   • Rows represent teams (including a row for the organization as a whole at the top)
   • Columns represent the metrics
   • Each cell represents a target

   
   For a cell with a given team row and metric column, if the text of the cell is colored:

   • Black, this means the current target is unchanged from the industry benchmark (the industry benchmark is shown on the first gray row, for reference)
   • Teal, this means a custom target has been set

   Note that this table currently lets you set targets for 5 of our metrics, Lead Time, Merge Frequency, Change Failure Rate, Out-of-Hours Work, and PR Participation Gap. To set targets on other metrics (or also for these metrics, as a secondary option), see the option below.

2. From a chart legend

   On a metric-specific pages (as accessed from the left hand menu bar), wherever you see a chart with a green target zone, you can customize the target here by going to the legend and clicking on the small target icon next to the “Target” label. This will show a modal from which you can edit the target. Click “Save Changes” to trigger a chart refresh.
   
   Note that if you’ve selected multiple teams or have “All” as the team filter at the top right of the page, the target shown in the legend will be the target for the organization as a whole.

   

• After you click 'Connect' on the Jira card on the Integrations page, on the resulting pop-up click ‘Connect Jira projects’

  

• This opens a new page on Atlassian Marketplace, click ‘Try it free’

  

• This pops up a modal. In this modal, first, select your site; second, click the button to ‘Start free trial’. Don’t worry this integration is not separately charged beyond your instance of Multitudes!

  

• This pops up a new modal, click ‘Get started’

  

• This will close the modals, on the resulting page, a dialog box should pop up on the lower left hand corner indicating that the install is in progress. Once complete, it will show success, from this dialog box, click ‘Get started’

  

• A new tab will open, on this tab, click ‘Allow access’

  

• A new tab will open, scroll to the bottom and click ‘Accept’

  

• This will close the last tab. On the resulting page, click the button ‘Connect with Multitudes’

  

• Now, you should be brought back to our app, where you’ll see a pop-up asking you to link Jira projects to Multitudes teams. First, make the selections as desired. Second click ‘Finish linking teams’

  

• Lastly, you’ll see a success message in the pop-up!

  

1. After you click 'Connect' on the Jira card on the Integrations page, on the resulting pop-up click ‘Continue to set up Linear’

   

2. This opens a new page, click 'Authorize Multitudes'

   

3. Now, you should be brought back to our app, where you’ll see a pop-up asking you to link Linear teams to Multitudes teams. First, make the selections as desired. Second click ‘Finish linking teams’

   

4. Lastly, you’ll see a success message in the pop-up!

   

Set up our GitHub Actions integration to get insights like Deployment Frequency , Lead Time through to deploy, Deploy Time, and Deployment Failure Rate.

NOTE: You can use either our Deployments API or our GitHub Actions integration to provide us with data about deployments. If you already have our Deployments API integration configured, you will need to revoke that action token before connecting with our GitHub Actions integration.

1. In the Multitudes app, go to Settings > Integrations and click on the Connect button in the Github and Github Actions card

   

2. On the resulting modal, click to configure Github Actions data
   

   

3. On the next page of the modal, you can choose either the “Environment/Deployments” or “Workflows” option, based on how you use GitHub Actions. See details below the image.
   

   

   
   Don't know what to pick? Here are some common scenarios:

   • “I have one workflow that deploys to multiple environments

     • This sounds like you are using GitHub Action’s “Environments” feature, and therefore their “Deployments” feature, so you would select "Environment/Deployments"
     • In your case, the best way for us to track a “deployment” is for you to tell us which Environment is the one referring to your production environment in each repository. You'll see this in the next step
     • Note that within one workflow run, you can have more than 1 successful deployment (e.g., you could use the same workflow to deploy to dev, staging, and prod). Therefore it’s important to understand how we calculate deployment metrics when you’ve selected this option.

     • A note on historical data availability: Due to constraints on GitHub’s API, we will not be able to fetch historical deployment data for this option.

       • This is only an issue if you onboarded to Multitudes recently (i.e., if you onboarded to Multitudes a while ago but didn't configure GitHub Actions until today, then today we can still access your historical deployment data).
       • While most charts will have 6 weeks of historical data from before you onboarded onto Multitudes to get you started, charts relating to deployments will only have data from onboarding onwards.
       • Also note that it might look like your Lead Time increases from the date that you onboard, because from that point onwards, lead time will include deploy time based on your deployments data.

       • Here's a concrete example

         • You onboard onto Multitudes (install our GitHub app) on 1 June, from this point on we start accumulating real-time events data
         • We also pull 6 weeks of historical data, back to 16 May, to get you started
         • On 8 June, you configure GitHub Actions
         • We will only show deployment data from June 1 to June 8

   • “I have a specific workflow that deploys only to prod”

     • This sounds like you are not using GitHub Action’s “Environments” feature
     • In your case, the best way for us to track a “deployment” is for you to tell us which Workflow is the one that deploys to your production environment for each repository. You'll see this in the next step
     • A note on historical data availability:  we will have access to historical data (the 6 weeks of data from before you onboarded onto Multitudes), but only the latest attempt in the historical data. This means that for example, if an attempt to deploy to production succeeded at 12pm, but for some reason you re-ran the workflow again successfully at 1pm, 1pm will be what is captured as the Deploy Time for that PR, even though it actually got deployed earlier at 12pm. This is a constraint on the historical data from the GitHub API

   With respect to data availability in either case, once you have integrated GitHub Actions, we will have real-time data, and will take the first successful attempts to deploy to production going forward (since that is when the change is first available to customers).

4. Once you’ve made a selection, the following page of the modal will prompt you for further configuration. In either case you will:
   

   • First identify which repository
   • Then within that repository, select either relevant environment or workflow
   • Click the "Save" button

   Screenshot for if you selected “Environment/Deployments”

   

   Screenshot for if you selected “Workflows”

   

5. All done!

   

• In the Multitudes app, go to Settings > Integrations and click on the connect Opsgenie card. This should direct you to your Opsgenie instance (otherwise click here)
• On Opsgenie navigate to settings > API key management > add a new API key
  
• Once you click add a new API key, you should get a pop-up. Proceed to do 3 things in the pop-up
  
  1. Select both the "Read" and “Configuration access” access scopes
  2. Copy the key - we also recommend you store this API access key in a secure location
  3. Click  "Add API Key" to finalize
• Back on Multitudes, paste the previously-copied API key into the text field and click save
• You will then be prompted to link your Opsgenie teams to Multitudes teams, this is so that you can use the team filters. If you do not link any Opsgenie teams all data will be returned unfiltered
• All done! Multitudes will now start to track your incidents and calculate Mean Time to Restore