Connecting External Data into Your Dashboards

Group Mappings in Insights NX let you bring in data from external sources (CI/CD tools, cloud providers, ticketing systems, etc.) and map them to the KPIs you track on your dashboards.

How it works:

• You group all AWS build stages in Opsera and connect this group to your KPI filters (like Deployment Frequency and Lead Time).

• Opsera automatically collects and displays the relevant data from AWS.

• Your dashboard now shows up-to-date deployment metrics for all build stages, letting you monitor performance and identify trends.

Result: You get accurate, real-time insights into your AWS deployments, helping your team improve delivery speed and quality with minimal setup.

Key Values

• Automate Data Ingestion The system will know exactly which external data points belong to that group and feed them to the appropriate KPI.

• Consistent Filtering Mapping ensures that every time a new change, it auto-maps—no manual intervention.

• Simplify Dashboards Group Mappings allow you to collapse them under one meaningful “label” (e.g., “AWS Build Stage”). Your dashboard panels stay neat, and you still have drill-down capability.

• Reusability Across Teams Once you define a group mapping, any team member viewing the Deployment Frequency widget sees exactly the same set of pipelines.

Pre-Requisites

Permissions

• You must have the necessary role access to Opsera.

Configured Data Connectors

• Ensure that your tools/connectors are already set up and authorized. If, for example, you have not yet connected your AWS account, you won’t see “AWS” as a Tool Type.

Consistent Naming Conventions

• To make filters easy to define, agree on a naming standard for your pipelines/projects/repositories.

Basic KPI Definitions

• Make sure your organization has already defined which KPI you want to measure.

Who can Configure Group Mappings?

• DevOps/Platform Engineers Tasked with organizing dozens (or hundreds) of pipelines, repos, or build jobs into meaningful buckets.

• Engineering Managers & Leads Who want to ensure that the team’s dashboards show consistent, pre-approved data sources.

• DevEx/Analytics Engineers Responsible for maintaining Insights NX dashboards, ensuring that “all production pipelines” or “all feature repos” are consistently mapped.

• Security/Compliance Leads Who need to group together all scan jobs, so their Security Posture widget pulls data only from approved pipelines.

Creating a New Group Mapping

Step 1: Navigate to Group Mappings

• Login to Opsera.

• From the left navigation bar select Unified Insights > Overview.

• In the home page, select + Create New > Mappings.

• You arrive at a table (Flat View by default) showing existing mappings.

• In the top-right corner, click the yellow + New Group button.

• A slide-in or modal appears (depending on your tenant version), prompting you to fill out the mapping details.

1. Select Organization (Required)

   • From the dropdown, choose which Organization this mapping applies to (e.g., AWS Pipeline org, GitHub CorpOrg, Jira Engineering).

   • If your account has multiple organizations connected, type the first few letters to filter the list.

2. Select Project (Required)

   • Once you pick an organization, choose a specific Project under that org (e.g., AQP Proj, DevEx Team, Frontend Releases).

   • If you want the mapping to apply to every project in that organization, select the special “All Projects” entry (if enabled for your tenant).

3. Define Your KPI (Required)

• From the KPI dropdown, select the metric you want to drive with this group. Common options include:

  • Deployment Frequency

  • Lead Time for Changes

  • Change Failure Rate

  • Mean Time to Restore (MTTR)

  • Static Scan Findings (code quality, security posture, etc.)

  • Sprint Velocity

• Tip: If you don’t see your KPI of interest, double-check that it’s been created as a KPI widget in your dashboard. Only defined KPIs appear here.

1. Choose Tool Type (Required)

• Select where Insights NX should look for this data. Options vary depending on your tenant setup, but might include:

  • AWS

  • GitHub

  • Jenkins

  • Azure DevOps

  • GitLab

  • Jira

  • Snyk, SonarQube

• Once you pick a tool type, Insights NX automatically knows which fields it can query.

1. Click "Preview" to view the Group Mappings. Use the Preview tab to instantly see all your tool mappings and their statuses in one place. It highlights pending tasks and clarifies relationships between configurations, speeding up reviews and reducing errors.

1. Enter Filter Name and Filter Value(s)

   • Choose the values based on the data you wish to retrieve.

2. Save the Mapping.

Flat View vs. Hierarchy View

When you land on Insights NX → Group Mappings, you can toggle between:

• Flat View

  • Shows each “Organization → Project → [Expanded list of KPI mappings]” as a single, scrollable table.

  • Good when you have only a few groups and want a quick glance at all entries.

• Hierarchy View

  • Collapsible tree:

    1. Organization (e.g., AWS Pipeline org)

    2. → Project (e.g., AQP Proj)

    3. → KPI (e.g., Deployment Frequency)

    4. → Filter Name (e.g., Deployment Stages)

    5. → Tool Type / Filter Value (e.g., AWS / BUILD)

  • Click the small “+” or “–” icon to expand/collapse each level.

  • Ideal when you have many nested mappings and want to drill into a specific organization or project without scrolling through everything.

Apply Role Based Access for Group Mappings

Role-Based Access Control (RBAC) for Group Mappings delivers enhanced security and a personalized experience across your dashboards and data filters. These role-based restrictions ensure only authorized users can access project-level data, supporting compliance and granular data visibility.​

How to Configure RBAC in Group Mappings

1. Go to Group Mappings.​

2. Click the hamburger icon for your target group mapping.​

3. Select Configure RBAC.​

4. Choose the Access Control Type, then select the appropriate user name/group or site role.​

5. Select the Role Type.

   
6. Click + Add Role to assign multiple roles as needed.​

7. Click Save Changes to apply role restrictions to your group mapping.​

Only authorized users can create, edit, or delete mappings and dashboards according to their role’s access level.​

Role Permissions Overview

Role	Dashboard/Mapping Access	Visibility Scope	Edit/Delete Permissions for Mapping
Administrator	Create and Edit all dashboards	All dashboards​	Yes​
User	Create, and edit - Own/assigned only​	Non-RBAC dashboards​	Yes ​
Guest	View only	Non-RBAC dashboards​	No​

Editing & Deleting Group Mappings

Editing a Mapping

1. Locate the mapping you want to change.

2. Click the Edit (✏️) icon in the Actions column for that Project row.

3. Modify any changes.

4. Click Save.

5. The Last Edited On timestamp updates, and the table reflects any changed values.

Deleting a Mapping

1. In the table (Flat or Hierarchy), locate the mapping row you wish to delete.

2. Click the Delete icon.

3. The mapping disappears immediately.