Connectors

Last updated 1 day ago

Your code says what was built. Every tool your factory relies on knows something else: which parts are fragile, which carry vulnerabilities, which tickets drove which change, why a rule exists. Connectors bring all of it onto the same model.

Mobioos does not replace any of these tools. It gives their findings a destination: the part of the product they actually concern.

What a connection gives you

  • An overlay on your model. Pick a measure and the graph colors itself by severity, with counts on every element. See Domain Context.

  • A Data panel per element, aggregating what every connector reports on that part of the domain.

  • A Data item column in the table view, showing coverage at a glance.

  • Context in your editor. Forge's enterprise context distillation brings the same polarized information to the code you are working on. See Forge.

Your scanner already told you which files have problems. None of your tools could tell you which feature is in trouble.

Available connectors

Connector

What it brings

SonarQube

Continuous code quality and security inspection

Aikido Security

Application security, vulnerability detection

GitHub

Commits, issues and activity, with traceability and delivery metrics

Azure DevOps

Commits, work items and activity, with traceability and delivery metrics

Atlassian Jira + Bitbucket

Jira issues and Bitbucket commits, for traceability and delivery metrics

Confluence

Your written knowledge: decisions, specifications, conventions

Endogenous and exogenous

Fusion polarizes what connectors bring in: it filters out the noise and projects what matters onto your ontologies. That information comes in two kinds.

Endogenous information describes the implementation. A SonarQube finding names a file and a line, so it attaches to your code almost immediately.

Exogenous information describes usage and intent. A customer ticket or a Confluence page explaining why a rule exists carries business language with no technical anchor, and has to be reasoned onto the right part of the model. That is where the business signal lives.

The kind depends on the information, not only on the tool. One ticket can hold both a business symptom and a technical diagnosis. Connecting sources of both kinds is what lets a business signal meet the code that implements it.

Adding a connector

  1. Open Project settings from the project bar

  2. Select Service Connections

  3. Pick a service from the grid and authenticate with it

Showing connector data on the graph

The lightning icon on the left of a Domain Context opens the Service Connections panel. Each connector has a toggle to show or hide its data on the graph, and a measure selector to choose what the graph displays.

These toggles control what you see. They do not stop data from being collected.

Scheduling

Each connector runs on a scheduler, Default scheduler (UTC) by default. From the Service Connections panel you can trigger a run immediately or look at its history, which is the first place to check when figures look older than your last deployment.