Rich formatting for Logs in Notification Policies
I would love to be able to manipulate the structure of the logs currently being injected by
spacelift::logs::applying
Currently this outputs a very hard to read text block.
- Workaround
- no
- Problem
I would love to be able to manipulate the structure of the logs currently being injected by
spacelift::logs::applying
Currently this outputs a very hard to read text block.
Log in to comment and vote
Comments2
Aleksandra Cieslak
Oct 16
Hi, thanks for the suggestion!
We're closing this one as it hasn't seen further demand and we didn't get a response to our follow-up questions.
If readable notifications are still a challenge for you, feel free to open a new request describing the information you'd want to see, and we'll gladly revisit it. I'm also open to a quick call about this or anything else on your mind: https://calendar.app.google/PRohGgEetKrTK3P37
Black Breeze
May 10, 2025
Hey, appreciate the request! Totally makes sense—nobody wants to squint at raw logs in Slack. That said, this one’s a bit thorny under the hood. Letting notification policies format or restructure logs would mean pulling the whole apply log into the policy engine, which would blow up the sample size and likely cause more problems than it solves (performance, cost, debug-ability).
That said—we’re not against the spirit of it. If we knew more about why you want rich formatting, we might be able to help in a cleaner way. Is it about making alerts more readable? Surfacing key info without clicking through? Something else?
If you can share what you’re trying to get out of this (or how you’re working around it today), we’d love to explore some lower-friction options that still get the job done.