Guides
Guides
How to connect LevelFour to your CI, your own tools and your chat, plus configuring the PR bot and the comment box on a recommendation.
Most of these guides connect LevelFour to something you already run, from a CI pipeline to your own CLI to a chat channel. The PR bot and the comment box on a savings recommendation are the other kind, surfaces LevelFour runs for you.
Most of the code on these pages needs a LevelFour API key before it runs. Authentication is where keys come from, and Key scopes is the read versus read-write split. The Slack and Google Chat receivers take the webhook signing secret instead, which Webhooks owns.
The guides
- Formatting comments is the Markdown the comment box on a savings recommendation understands, and the GitHub syntax it does not
- Filtering and sorting narrows a cost or recommendation query from the terminal, with the same parameters in the SDKs
- Virtual tags assigns one tag key to every AWS and GCP cost from rules you write, to fix inconsistent tags and split shared costs
- GitHub Actions has whole workflow files that comment a cost summary on a pull request and upload a daily report
- PR bot configuration tunes the bot LevelFour runs on your pull requests, through the optional
.levelfour/config.yml - CI/CD Integration gates a pull request on cloud cost with
l4 estimateandl4 diff, in GitHub Actions or GitLab CI - Integrate the SDK into your CLI embeds the SDK as a library in a CLI your team already ships, for typed objects and language-native errors
- Integrate l4 into your CLI shells out to the
l4binary from scripts, Makefiles and CI runners, with no SDK in the dependency tree - Backstage Plugin builds both halves of a plugin that shows LevelFour cost data in your developer portal
- Slack Integration verifies the signature on a LevelFour webhook and posts the event into a Slack channel
- Google Chat Integration does the same for a Google Chat space
- Scheduled Execution runs an unattended check on cron or a workflow, and says when webhooks beat a schedule
Next
- CLI is the
l4binary several of these call: the command groups, the global flags and the exit codes to script against - SDKs is the Python, TypeScript and Go clients the code samples are built on
- Webhooks is what LevelFour posts to your endpoint, and the signature the chat receivers verify
- API reference is the REST surface underneath all of it