Skip to main content
Book a demo

Connect Chronosphere to Glean

Give Glean governed access to Chronosphere’s 31 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Glean setup guide

Set up

Add Chronosphere to Glean in four steps

Admins approve the server once. Everyone in Glean then gets it through the same governed connection.

  1. 1

    Add Chronosphere to Runlayer

    Chronosphere isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Glean to Runlayer

    Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Chronosphere’s 31 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Glean setup guide
  3. 3

    Sign in to Chronosphere

    Sign in the way Chronosphere requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Chronosphere from Glean

    Chronosphere’s approved tools appear in Glean. Every call is checked against policy and recorded.

Tools

31 Chronosphere tools in Glean

Runlayer policy decides which of these Glean users can call.

  • Get dashboard

    Get dashboards resource

  • Get drop rule

    Get drop-rules resource

  • Get events metadata

    List properties you can query on events

  • Get log

    Get a full log message by its ID.

  • Get log histogram

    Get histogram of logs from a given query

  • Get mapping rule

    Get mapping-rules resource

  • Get monitor

    Get monitors resource

  • Get notification policy

    Get notification-policies resource

See all 31 Chronosphere tools

Control

What Runlayer can see and stop in Glean

Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.

  • Gateway policy (available)

    Every Chronosphere call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.

  • OTLP telemetry (available)

    Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.

In Glean

  • Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.

Frequently asked questions

Connect more

Find another combination