GitHub

Integrate Olly with your GitHub repositories to understand code changes, investigate issues, and speed up delivery — from commit to production.

Overview

The GitHub integration allows Olly to use code context when answering questions, running investigations, and performing root cause analysis. By connecting your repositories, Olly can link logs, errors, and alerts directly to the relevant code, highlighting the exact files and lines involved and guiding you toward the right fix.

Why connect GitHub

Enabling GitHub helps Olly move investigations to source code:

• Reduce manual debugging by tracing errors and anomalies directly to code
• Speed up investigations and RCA with file- and line-level context
• Understand what changed and why an issue started
• Get targeted, actionable fix suggestions instead of high-level explanations

Example questions Olly can answer

• "Where in the code does this log/error originate?"
• "Show me what changed before this spike."
• "Which lines are responsible for this issue and how do I fix it?"
• "What's causing the latency increase in my checkout service?"
• "What's the root cause of this anomaly?"
• "Why did error rates spike between 10-11 AM?"

Before you start

• A user with the required Coralogix permissions to manage integrations must enable the integration.
• The GitHub app must be installed in your GitHub organization by either:
  • A GitHub organization owner, or
  • A user who is an admin of at least one repository in the organization (or when the organization has at least one public repository)
• Coralogix recommends that a GitHub organization owner perform the installation. If you are not a GitHub organization admin, you can still initiate the installation.
• Currently, Olly supports one GitHub integration per organization.

Install the GitHub integration

Installing the GitHub integration authorizes the Olly app in your GitHub organization. This allows Olly to access the repositories and permissions required to use code context during investigations and root cause analysis.

1. In the Coralogix navigation, go to Integrations.
2. Find Olly - GitHub Integration and select Connect to GitHub.
3. Complete the GitHub authentication flow.

Disconnect GitHub

To disconnect the GitHub integration:

1. In the Coralogix navigation, go to Integrations.
2. Find Olly - GitHub Integration and select Disconnect GitHub.
3. Confirm the disconnection.

After disconnecting, GitHub repositories are no longer available as context in Olly. You can reconnect at any time by repeating the installation steps.

Connect GitHub as an individual user

After the integration is enabled by an admin, each user must individually authenticate with GitHub to connect it as a data source.

1. In the Olly chat, select the + icon in the chat input, then select Connect GitHub account.
2. Complete the GitHub authentication flow to authorize your account.
3. Select a repository from the dropdown. The repository you select appears as a blue badge below the chat input. You can select only one repository at a time — selecting a different one replaces the previous selection.

To grant Olly access to additional repositories, select Connect GitHub account from the repository dropdown. This redirects to GitHub, where you can authorize the Olly app for any repositories you have sufficient permissions for.

How repository access works

When the GitHub app is installed:

• The app automatically receives access to all public repositories in the organization.
• It also receives access to any private repositories for which the installing user has sufficient permissions (for example, if they are an admin or owner of that repository).

Repository access is managed in GitHub. After installation, repository admins or owners can grant or revoke access to the Olly app from GitHub settings.

If there are repositories you can access in GitHub that do not appear in the repository selection dropdown, select Connect GitHub account to authorize them, or contact a repository admin or organization owner to grant the Olly app access.

Access behavior for non-owners

If you do not have organization owner rights or admin rights on at least one repository in the GitHub organization, GitHub submits an installation request rather than completing it immediately. The integration tile shows a Pending Approval status until a GitHub organization owner approves.

• The user needs to have the appropriate Coralogix permissions to manage integrations.
• You have immediate access to the public repositories you selected in the GitHub organization.
• Access to private repositories is managed in GitHub and may require approval from a GitHub organization owner.

Once the GitHub organization owner approves the request, the integration activates automatically — no further action is needed in Coralogix.

Use GitHub context in the Olly chat

GitHub context is available only in Focus mode. You can select only one repository at a time.

1. Open the Olly chat and switch to Focus mode.
2. Select the + icon in the chat input and add a GitHub repository. The selected repository appears as a blue badge below the chat input.
3. Ask your question. Olly automatically uses code context when relevant.

To switch repositories, select the + icon again and pick a different one. The blue badge updates to show the new selection.

Olly can search and analyze your repository when code context is relevant, for example when:

• You ask about specific code behavior
• Olly is conducting an investigation
• Olly is performing root cause analysis

Olly always works with the most up-to-date version of the repository and can analyze specific commits or points in time, making it easier to:

• Compare production vs. staging behavior
• Identify regressions
• Understand why an issue happens now but did not before

Insights and fixes

When code context is used, Olly can:

• Highlight exact file paths and line ranges
• Explain why those lines matter
• Suggest targeted fixes or code changes

Security and data handling

Olly handles GitHub access and code context in accordance with Data Processing, Privacy, and Compliance policies.

• Code accessed through the integration is never used to train AI models
• Code is never shared across tenants
• Coralogix does not assume any ownership, title, or interest in the code or documentation accessed through this integration

Next steps

Bring Olly into your team conversations in Slack.