🔍
Lariat Data
  • 👋Welcome to Lariat Data
  • Overview
    • 💡Video Overview
    • ✨Core Features
    • 🤓Glossary
  • Fundamentals
    • ⚙️Installation & Configuration
    • 📈Working with Datasets and Indicators
    • ☁️Platform Architecture
    • 🔓Your API & Application Keys
  • Integrations (Data Storage)
    • ⏏️S3 Object Storage
    • ⛄Iceberg
    • ⚛️AWS Athena
    • ❄️Snowflake
    • ⏏️GCS Object Storage
    • 🖥️AWS Redshift
    • 🖥️Google BigQuery
  • Integrations (Code)
    • 🐍Python
    • 💫Spark
    • ☕Java/JVM
Powered by GitBook
On this page
  1. Overview

Glossary

Terminology repeatedlly used across our docs and platform

  • Agent: The set of code that runs on a customer's cloud to collect metric data. These are open-source and only collect a metric value, timestamp and additional metadata (like groupings or items to filter on)

  • Dataset: Represents either a tracked database table or a virtual representation of joined tables (like a view) and data collected from streaming agents (like a schema representing the output format of a Prediction API)

  • Indicator: A metric usually representing data health. In Lariat, these are plotted on a time-series so have to have a time dimension associated with it. Indicators can etiher be set up during configuration through a quickstart menu or custom-built with SQL. In either case, there is a SQL representation that backs an Indicator

  • Event: This is generally a streaming event. Examples of this include, ObjectCreated events that write a file to S3, lambda triggers or Kafka writes.

  • Ingest: Represents the first phase of data ingress into a data organization

  • Integration: Refers to an agent integration or an output integration such as sending alert data to PagerDuty, Slack or email or metric data to Datadog, Grafana or Tableau

PreviousCore FeaturesNextInstallation & Configuration

Last updated 1 year ago

🤓