Skip to content

fix(last9-cloudwatch): name the averaging window for MSK throughput #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
prathamesh-sonpatki merged 2 commits into from
Sep 10, 2026
Merged

fix(last9-cloudwatch): name the averaging window for MSK throughput #18

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3332f9c
fix(last9-cloudwatch): name the averaging window for MSK throughput
prathamesh-sonpatki Sep 10, 2026
6a5ec42
fix(last9-cloudwatch): state what a selector without a range returns
prathamesh-sonpatki Sep 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion skills/last9-cloudwatch/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Installed schemas take precedence over this reference:
| `prometheus_instant_query` | `query`, `datasource`, `time_iso` |
| `prometheus_range_query` | `query`, `datasource`, `start_time_iso`, `end_time_iso` |

Discover names with `label: "__name__"`. Do not invent a `step` parameter. Distinguish raw range selectors evaluated once from repeatedly evaluated charts.
Discover names with `label: "__name__"`. Do not invent a `step` parameter. Distinguish raw range selectors evaluated once from repeatedly evaluated charts. A selector carrying no range returns only the latest period, so any total, average, or coverage claim about a whole interval needs a range selector spanning that interval; before claiming one, check that the returned sample count matches the periods the interval should contain.

## Discover and execute efficiently

Expand Down
2 changes: 1 addition & 1 deletion skills/last9-cloudwatch/references/msk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Broker metrics, cluster aggregates, and topic breakdowns are not interchangeable

## Throughput and lag

- `BytesInPerSec`, `BytesOutPerSec`, and `MessagesInPerSec` already describe rates. Use the requested level or average; applying `rate()` again changes the quantity. Combining broker/topic rows needs a verified non-overlapping population.
- `BytesInPerSec`, `BytesOutPerSec`, and `MessagesInPerSec` already describe rates, so applying `rate()` again changes the quantity. Match the average to the requested window: for the latest period use that matched Sum/SampleCount pair; for a mean over the requested interval use total Sum / total SampleCount across the disjoint periods, read from the raw companion series over that window rather than a single instant query returning only the last period. Combining broker/topic rows needs a verified non-overlapping population.
- `MaxOffsetLag` is the maximum offset lag across the applicable partitions; `SumOffsetLag` is a different aggregate. Neither is a count of unique messages processed during the observation window.
- `EstimatedMaxTimeLag` is in seconds. An offset count cannot be converted to time without additional evidence.

Expand Down
Loading