Skip to content

docs: clarify API token can be Secure or Monitor#78

Merged
tembleking merged 2 commits into
mainfrom
docs/clarify-api-token-monitor
Apr 21, 2026
Merged

docs: clarify API token can be Secure or Monitor#78
tembleking merged 2 commits into
mainfrom
docs/clarify-api-token-monitor

Conversation

@tembleking
Copy link
Copy Markdown
Member

Either a Sysdig Secure or Monitor API token works against SYSDIG_MCP_API_TOKEN. README prose and placeholder (<your_sysdig_secure_api_token><your_sysdig_api_token>) previously implied Secure-only.

Copilot AI review requested due to automatic review settings April 21, 2026 15:18
@tembleking tembleking requested a review from a team as a code owner April 21, 2026 15:18
airadier
airadier previously approved these changes Apr 21, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the README to clarify that SYSDIG_MCP_API_TOKEN can be either a Sysdig Secure or Sysdig Monitor API token, and adjusts placeholders/text that previously implied Secure-only usage.

Changes:

  • Generalizes “Sysdig Secure” wording to “Sysdig instance” where appropriate in the Quickstart and configuration guidance.
  • Renames the token placeholder from <your_sysdig_secure_api_token> to <your_sysdig_api_token> across example configs/CLI snippets.
  • Updates the required env var descriptions to explicitly allow Secure or Monitor tokens.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
Comment thread README.md
@tembleking tembleking merged commit 1939af0 into main Apr 21, 2026
4 of 5 checks passed
@tembleking tembleking deleted the docs/clarify-api-token-monitor branch April 21, 2026 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants