Connect LogRocket to GitHub Copilot
Give GitHub Copilot governed access to LogRocket’s 3 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add LogRocket to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve LogRocket in Runlayer
Add LogRocket from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches LogRocket’s 3 tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to LogRocket
Sign in the way LogRocket requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use LogRocket from GitHub Copilot
LogRocket’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
3 LogRocket tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call.
List organizations
List organizations the user has access to.
List projects
List projects the user has access to.
Use LogRocket
Run a natural language query against LogRocket.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every LogRocket call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more