Context CLI
graphsignal-context
Section titled “graphsignal-context”CLI for logging in and fetching Graphsignal signal context.
Install as an isolated CLI tool with uv:
uv tool install graphsignal-contextgraphsignal-context login
Section titled “graphsignal-context login”Store your Graphsignal API key in ~/.graphsignal/config.yml.
graphsignal-context loginYou will be prompted for your API key.
Login is not required if the GRAPHSIGNAL_API_KEY environment variable is set.
graphsignal-context guide
Section titled “graphsignal-context guide”Fetch information about signals.
graphsignal-context guideBehavior:
- Requires a saved API key (
graphsignal-context login). - Calls
GET /api/v1/context/guide/onhttps://api.graphsignal.com. - Prints the returned text content to stdout.
graphsignal-context signals
Section titled “graphsignal-context signals”Fetch signal context for a time range.
graphsignal-context signals --start 2026-03-10T00:00:00Z --end 2026-03-12T00:00:00ZOptional --tags filter:
graphsignal-context signals \ --start 2026-03-10T00:00:00Z \ --end 2026-03-12T00:00:00Z \ --tags "env:prod;service:inference"Options:
--start(required): Start of time range in ISO 8601 format (for example,2026-03-10T00:00:00Z).--end(required): End of time range in ISO 8601 format.--tags(optional): Semicolon-separatedkey:valuepairs for exact tag filtering.
Behavior:
- Requires a saved API key (
graphsignal-context login). - Converts
--startand--endinto nanosecond timestamps. - Calls
GET /api/v1/context/signals/onhttps://api.graphsignal.com. - Prints the returned
contextpayload to stdout.
Common errors:
- Not logged in: run
graphsignal-context login. - Invalid datetime format for
--startor--end. --startmust be before--end.- API request errors (for example, invalid API key).