Connect LogRocket to Gumloop
Give Gumloop governed access to LogRocket’s 3 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add LogRocket to Gumloop in four steps
Admins approve the server once. Everyone in Gumloop 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 Gumloop to Runlayer
Users add the Runlayer Plugin to Gumloop by following Runlayer’s setup guide. Gumloop reaches LogRocket’s 3 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Gumloop 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 Gumloop
LogRocket’s approved tools appear in Gumloop. Every call is checked against policy and recorded.
Tools
3 LogRocket tools in Gumloop
Runlayer policy decides which of these Gumloop 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 Gumloop
Some controls apply to every client at the gateway. Others depend on what Gumloop exposes to Runlayer.
Gateway policy (available)
Every LogRocket call from Gumloop passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Gumloop as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Gumloop yet, so control happens at the gateway.
Frequently asked questions
Connect more