Integrate your Tools¶
DataOps Observability supports integrating with a wide array of data tools so you can monitor your data operations with end-to-end visibility.
Warning
This step requires technical knowledge about your tools. A Developer, DevOps Engineer, DataOps Engineer, or Data Engineer may be needed. And don't forget, we're always here to help. Follow along with our step-by-step help documents and walkthroughs or contact DataKitchen if you have more questions.
Integration methods¶
Observability receives, aggregates, and displays event information sent by your tools and data assets (i.e. components). The system does so by exposing a REST API—the Event Ingestion API—where the events are received and ingested in real time.
Each of the integration methods described in this table links to more details. The table is ordered from least to most integration effort.
| Integration method | Details | Best for |
|---|---|---|
| Observability agent | Observed components expose or publish events in a way that an agent can forward them to Observability through the Event Ingestion API. DataKitchen provides ready-made agents for common data science and DataOps tools. | A large number of components are being observed and augmentation to send events is difficult. Users who don't want to make changes to their existing data estate. |
| Event Ingestion API | Observed components use a client library or script to send events directly to the Event Ingestion API. DataKitchen provides a pre-built Python package and a walkthrough on how to post events. | A small number of components that are easy to augment in order to publish events. Users who prefer to code and customize their integration. |