Fix ansible handler timeouts for alloy and loki restarts #12

Merged
eblume merged 4 commits from fix/ansible-handler-timeouts into main 2026-01-15 13:56:12 -08:00
Owner

Summary

  • Use async with poll: 0 for alloy and loki restart handlers
  • Fire-and-forget approach prevents ansible from hanging on graceful shutdown

Test plan

  • Manually verified brew services restart grafana-alloy works
  • Run full ansible playbook and verify it completes without timeout

🤖 Generated with Claude Code

## Summary - Use async with poll: 0 for alloy and loki restart handlers - Fire-and-forget approach prevents ansible from hanging on graceful shutdown ## Test plan - [x] Manually verified `brew services restart grafana-alloy` works - [x] Run full ansible playbook and verify it completes without timeout 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Use async with poll: 0 to fire-and-forget service restarts.
These services have graceful shutdown periods that can exceed
ansible's default command timeout.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
eblume force-pushed fix/ansible-handler-timeouts from f78567798c to acff29f554 2026-01-15 13:06:27 -08:00 Compare
- Fetch transmission list once and parse locally instead of calling
  transmission-remote for each archive (43 calls -> 1 call)
- Only recheck torrent status if new torrents were actually added
- Use set_fact to merge initial/recheck status for downstream tasks

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Migration complete - no longer need to stop node_exporter on each run.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Change "Chunks in Memory" to "Total Stored" using loki_ingester_chunk_stored_bytes_total
  (loki_ingester_memory_chunks_bytes doesn't exist)
- Update "Memory Usage Over Time" to "Storage Over Time" with correct metric

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Author
Owner

also a bunch of other cleanup stuff, nbd

also a bunch of other cleanup stuff, nbd
eblume merged commit 2a1359a3b6 into main 2026-01-15 13:56:12 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!12
No description provided.