feat: add a CloudWatch Logs groups view

Aperta
  • Qualcosa non va?
#132 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
54/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
aws, rust
Ambito
cli, cloud

Direzione di ricerca

Read docs/recipes/README.md and docs/recipes/add-a-service.md first, then follow that recipe to find the existing service implementations and palette entries. The issue also names docs/architecture.md, docs/aws-service-roadmap.md, AGENTS.md, and the README for updates. Done means the Logs view, row actions, status handling, unit tests, and minor changeset meet the listed checks; start after issue #116 is merged.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

size: M

Why

Every ECS service and Lambda writes to a log group. Groups with no retention grow forever and are one of the most common slow cost leaks.

Follow docs/recipes/add-a-service.md.

Steps

  1. Follow docs/recipes/add-a-service.md. New crate aws-sdk-cloudwatchlogs.
  2. Fetch with describe_log_groups and its paginator.
  3. Model LogGroupInfo: name, retention days (Option<i32>, None means never expire), stored bytes, creation time, tags via list_tags_for_resource on the group ARN.
  4. Columns: name, retention (never when None), stored size (human readable, for example 1.2 GB), created.
  5. Console: https://console.aws.amazon.com/cloudwatch/home?region=<region>#logsV2:log-groups/log-group/<url-encoded-name>. CLI: aws logs describe-log-groups --log-group-name-prefix <name> --region <region>.
  6. Palette entry logs with alias log-groups.

Where to look

  • docs/recipes/add-a-service.md

Done when

  • CloudWatch Logs view reachable from the command palette
  • Rows carry tags: Tags
  • Describe, console pivot, and CLI pivot work on the selected row
  • A denied or failed fetch shows a status, not an empty table
  • Unit tests for the model helpers and the DescribableResource URLs and CLI command
  • README, docs/architecture.md, docs/aws-service-roadmap.md, and AGENTS.md updated
  • Changeset added (minor)
  • cargo fmt --all, cargo clippy --all-targets -- -D warnings, and cargo test --all pass, with output pasted in the PR

Check against AWS

Optional. Unit tests are enough for this issue.

Blocked by

#116. Start this after that is merged.

Size: M. Read docs/recipes/README.md before starting.

Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
4h 8m
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fells-code/seamless-glance

Tutte le issue di fells-code/seamless-glance

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.