Data configuration

What insights and metrics does Multitudes provide?

We go into detail on our metrics & insights here: What We Measure and Why

How do we integrate with OpsGenie?

Some insights on Multitudes, such as Mean Time to Restore (MTTR) require your organization to install an integration with OpsGenie. After you’ve installed OpsGenie, you’ll be able to see insights for more metrics!

  • 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
    Screenshot with instructions
    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 calculateMean Time to Restore

Note: Multitudes tracks MTTR by looking at your Opsgenie <code-text>incidents<code-text>. It does not look at Opsgenie <code-text>alerts<code-text>. The Opsgenie <code-text>incidents<code-text> feature is only available to paying Opsgenie customers.

My commits don’t seem to be appearing in Multitudes – what’s going on?

Check that the email address that is in your local git config (<code-text><code-text> when you do <code-text>git config -l<code-text>) matches the email address(es) that are linked to your GitHub account. You can change this by either changing git config to match an email that’s in GitHub, or by adding your git config email address to your GitHub account under If the emails are different, GitHub won’t know how to match your commits to your GitHub login (although it still links it to the account because of your SSH keys).

How do I change the standard working hours?

Multitudes uses people’s working hours to calculate out-of-hours work. We have a default setting for this (Mon-Fri, 9 am - 5 pm in the timezone of your company’s headquarters), but because people work flexibly, we strongly recommend that you configure this for your individual preferences.To change the working hours for you or a teammate, go to Settings > Team Members, and select the person you want to adjust. Scroll down to the “Working Times” section, make changes as needed to the Timezone, Work days, or Working hours, and then choose “Confirm.”

How do I back-date a team member's working hours?

Some insights on Multitudes, such as out-of-hours work, are based on a team member’s working times. These are individually configurable but we start with the following defaults:

  • Timezone: The organization’s timezone
  • Working days: Monday to Friday
  • Working hours: 8am to 5pm

If you have a team member who works different hours or in a different timezone, you will likely want to update the default settings and back-date the changes so that person's historical data matches their actual working hours. To do that, follow the steps below.

First, go to Settings > Team Members, and select the person you want to adjust. Scroll down to the “Working Times” section and make changes as needed to the Timezone, Work days, or Working hours.

After you make changes to the "Working Times" section, a banner will appear (see screenshot below). Choose “Yes, back-date these changes”.

Screenshot of the working times settings in the Multitudes app, with a banner asking whether to back-date changes.

This will back-date your current working time settings, applying the current settings to the last 12 months of data for this person. This includes recalculating metrics that use these settings, such as Out-of-Hours work.

If you do not want to back-date the changes to Working Times, click “No, update from today” and the app will apply your settings from that point onwards, just like any other setting.

What if we have people who work on multiple teams? Or people who don’t work on any specific teams?

We’ve left the team structure flexible so it can meet your needs: We allow people to be on multiple teams, or on no teams at all.

However, if someone is not on any team, then they won’t appear in our graphs (since our tool is focused on helping teams work better together). As soon as you add them to at least one team, then they will be included in our insights.

Can’t find what you are looking for?

Contact us