Connecting Tools
Logilica ingests data from common DevOps and Platform Engineering products and creates out-of-the-box metrics, dashboards and reports.
To connect your data sources, navigate on the sidebar to Settings -> Integrations.
From there, select the data source you want to connect. Click Install to start the integration process. You will need to authenticate and allow Logilica to access the relevant metadata.
Supported Connectors
Each connector has its own page covering authentication, exactly what data is imported, how it is mapped into Logilica's model, and the configuration a customer needs to get right. Select a platform below for the detail.
Source Code Management
OAuth or Personal Access Token (PAT)
Pull requests, commits, PR reviews and comments, PR state (open/merged/closed), releases, contributor identities
GitHub App installation
Same as GitHub PAT — supports enterprise and self-hosted GitHub via custom URL
GitLab (cloud and self-hosted)
Personal Access Token
Merge requests, commits, MR discussions/notes, approvals, releases, contributor identities
All code connectors also import contributor identities (name, email, username) for identity resolution and team assignment. Logilica also links pull requests to planning tickets — see Linking Pull Requests and Tickets.
Issue Tracking / Project Management
Jira (Cloud and Server 8.x+)
OAuth or API Token
Issues, sprints, epics, issue events (created/assigned/in-progress/resolved), story points, custom fields, labels, issue type hierarchy, assignees, reporters
Personal Access Token
Work items, iterations (sprints), custom fields, work item type icons, assignees
Same as GitHub code connector
GitHub Projects v2 items, custom fields (priority, story points, sprint), issue events, parent/sub-issue relationships
Permanent Token
Issues, sprints, state history, assignee events, custom fields, labels, story points, issue type hierarchy
CI/CD
Enabled via the GitHub/GitHub Apps connector settings
Workflow runs, jobs, steps, build status, start/end timestamps
Enabled via the GitLab connector settings
Pipelines, stages, jobs, status, timestamps
CI/CD data feeds the Build dashboards and is required for DORA metrics.
Code Coverage
API Token
Per-commit coverage data, individual test results (pass/fail/skip/error), test duration, branch, contributor identity
AI Developer Tools
API Token
Daily AI usage per user: lines added/deleted by AI, interaction types (composer, chat, agent, tab completions, command palette), request types, spend data (token counts)
Claude Code (Anthropic)
Admin API Token
Daily AI usage per user: lines added/deleted by AI, sessions, commits and PRs created by Claude Code, tool action accepts/rejects, token counts, estimated cost, most-used model
Enabled via the GitHub/GitHub Apps connector settings
Organisation-level and per-team Copilot metrics, interaction types, usage counts. Data is aggregated — individual per-user usage breakdowns are not available from the Copilot API. Import window is the last 100 days (not 6 months)
AI developer tool data feeds the AI Coding workstream dashboard.
Deployment Platforms
Security Findings (SARIF Upload)
Logilica accepts security scan results via SARIF file upload from your CI/CD pipeline. Any scanner that emits SARIF format is supported — including Snyk, Coverity, CodeQL, AppInspector, and others. Push SARIF files to Logilica's upload API endpoint from your CI pipeline. See Security Findings (SARIF) for the upload format and field mapping.
See the Import API for details on uploading SARIF data via the API.
Authentication Methods
Logilica supports two authentication approaches depending on the data provider:
OAuth-based Access
Logilica will only read the relevant data and will have no write access to your data source. All OAuth authentication is done through your data provider without Logilica storing any passwords.
Token-Based Access
Logilica supports access tokens where the data provider does not support OAuth or where additional token-based access is required.
Connector Settings
Some connectors have additional settings that control what data is imported. For example, GitHub and GitLab connectors include toggles for:
Build information — import CI/CD data (GitHub Actions, GitLab Pipelines)
AI usage data — import GitHub Copilot metrics
Code scanning — import SARIF security findings
Team synchronization — sync platform teams as Logilica teams
These settings are available on the connector's configuration page after installation.
Good to Know
First import covers the last 6 months. Only data updated within the last 6 months is imported on the first scan. Older data that hasn't been touched won't appear. Importing data older than 6 months requires a configuration change by Logilica — contact support.
CI build history imports the last 1000 runs per repository at initial onboarding. Future runs are added automatically.
Issue tracker connectors share a common data model. Regardless of whether you use Jira, GitHub Projects, Azure DevOps Boards, GitLab Issues, or YouTrack, Logilica maps all planning data into a unified model with consistent state categorisation (To Do, In Progress, Done). See each issue tracker's connector page above for its platform-specific mapping rules.
Questions?
If you cannot find your preferred data source or have trouble connecting, reach out to us at support@logilica.com as we may support additional data sources as part of our enterprise plan or in closed beta.
Last updated