Custom Sources

Sometimes the default data provided by the source systems may not be enough. In these cases, you can integrate Faros with a custom process you have set up. For example, an application deployment pipeline implemented as a Jenkins job that deploys your application to production. In order to get deployment information to Faros, you can instrument the pipeline by sending events to Faros using either our Events CLI or our Events API.

Using the Events CLI (Recommended)

The events CLI supports multiple event types. Each is used to instrument a different part of your CI/CD pipelines.

CI Event – used to instrument code build pipelines. For example, you can report the result of a successful code compilation and Docker container release.

CD Event – used to instrument deployment pipelines. For example, you can report the result of a successful application deployment to an environment (e.g. Prod). Each CD event corresponds to a single application deployment. If there are multiple applications being deployed from the same artifact repository, there should be multiple deploy events.

Using the Events API

An alternative approach is to use our Events API directly, which supports both CI and CD event types. You can invoke it using simple cURL commands.


Did this page help you?