---
icon: material/lightning-bolt-outline
---

Triggers execute the 10x Engine in response to an event within an environment such as file uploads or GitHub commits.

:material-ice-cream: This launcher employs the [Compiler flavor](https://doc.log10x.com/engine/flavors/#compiler).

***Use-case***:

[:material-bucket-outline: Index](https://doc.log10x.com/run/input/objectStorage/index) modules execute the runtime when a file containing log/trace events is uploaded or deleted from an object storage (e.g., S3).

[:material-cogs: Compile](https://doc.log10x.com/compile/) pipelines can execute as a CI/CD post-build to generate [symbol library](https://doc.log10x.com/compile/link/#symbol-library) files.

Once processing is complete, the compiler can [push](https://doc.log10x.com/compile/push/) output symbol unit files to GitHub to accelerate subsequent iterations, avoiding pulling and processing unchanged input files.

Cloud/edge apps can [pull](https://doc.log10x.com/config/github/) the latest symbol library files at startup or on remote updates, or load them from a [Kubernetes ConfigMap](https://doc.log10x.com/config/k8s/) with the same reload-on-update behavior.