Repository navigation
docs: explain how to exclude resources from Cloud Capture by tag and set its scan frequency - #462
Merged
Merged
Conversation
The getting-started page said to tag a resource `kosli.capture=false`, which was the plan before cloud-capture#18 settled that customers choose their own tags in the Cloud Capture settings. The section now says where the tags are set, how they are matched (key and value, exactly), which resource they are read on (an ECS cluster with everything in it, a Lambda function on its own), when a change takes effect, and that the published IAM role already grants the permissions to read them; and it shows the settings API body for anyone scripting it. The overview's pointer to the section is reworded to match. Closes kosli-dev/cloud-capture#20 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Claude finished @sami-alajrami's task in 1m 41s —— View job Follow-up review complete
Result: only one line changed in this range — the API paragraph in the Scan frequency section ( Full details: summary comment |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
…ed settings The settings PUT replaces every setting, so the skip-tags API example now tells the reader to read the current configuration and send the other settings back unchanged, as the doc review pointed out a copied example would otherwise reset their regions and interval. Both tabs said Cloud Capture "runs on a five-minute schedule". It does by default, and an admin can now pick another interval on the settings page, so a Scan frequency section explains where, which presets are offered, what the interval means for what Kosli sees, and the API field. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sami-alajrami
changed the title
Whether to offer a shorter interval, and to whom, is not a commitment the docs should make. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The page offers a short list of intervals; the API takes any whole number of minutes, and the page shows a non-preset value as its own option. The doc review read the two sentences as contradicting each other, so the API one now says which is the wider. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
Follow-up review: commit range 73b9f41..5dc1065Only one line changed in this range (
No new bugs, regressions, or inconsistencies found in the changed line — it's a clarification that doesn't contradict the rest of the section. 0 new inline comments beyond the one closing the resolved thread above. |
gsavage
approved these changes
Oct 16, 2026
ToreMerkely
approved these changes
Oct 16, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the fixed
kosli.capture=falsetag in the Cloud Capture getting-started page with how exclusion now works: the customer lists their own skip tags in the Cloud Capture settings, and a resource carrying any one of them is not captured. The section covers where to set them, exact key-and-value matching, which resource the tag is read on, when a change takes effect, and the settings API body. A new Scan frequency section documents the interval an admin can now pick on the settings page, five minutes by default. Pairs with kosli-dev/server#7449 and kosli-dev/cloud-capture#100.Closes kosli-dev/cloud-capture#20
🤖 Generated with Claude Code