Ylem documentation
  • 🗒️General information
    • Introduction to Ylem
    • Quick start guide
    • Release notes
  • 🔬Open-source edition
    • Installation
    • Usage of Apache Kafka
    • Task processing architecture
    • Configuring integrations with .env variables
  • 💡Integrations
    • Connecting an integration
    • Library of integrations
      • Amazon Redshift
      • Apache Kafka
      • APIs
      • Atlassian Jira
      • AWS Lambda
      • AWS RDS
      • AWS S3
      • ClickHouse
      • ElasticSearch
      • E-mail
      • Google Big Query
      • Google Cloud SQL
      • Google Pub/Sub
      • Google Sheets
      • Immuta
      • Incident.io
      • Jenkins
      • Hubspot
      • Microsoft Azure SQL
      • MySQL
      • OpenAI ChatGPT
      • Opsgenie
      • PostgreSQL
      • PlanetScale
      • RabbitMQ
      • Salesforce
      • Slack
      • Snowflake
      • Tableau
      • Twilio. SMS
      • WhatsApp (through Twilio)
    • Initial demo data source
  • 🚡Pipelines
    • Pipeline management
    • Tasks
      • Aggregator
      • API Call
      • Code
      • Condition
      • External trigger
      • Filter
      • For each
      • GPT
      • Merge
      • Notification
      • Query
      • Pipeline runner
      • Processor
      • Transformer
    • Running and scheduling pipelines
    • Library of templates
    • Environment variables
    • Mathematical functions and operations
    • Formatting of messages
  • 📈Statistics and profiling
    • Statistics of runs
    • Slow tasks
  • 📊Metrics
    • Metric management
    • Using previous values of a metric
  • 💼Use cases, patterns, templates, examples
    • Use cases
    • Messaging patterns
      • Datatype Channel
      • Message Dispatcher
      • Messaging Bridge
      • Message Bus
      • Message Filter
      • Message Router
      • Point-to-Point Channel
      • Publish-Subscribe Channel
      • Pull-Push
    • Functional use cases
      • Streaming from Apache Kafka and messaging queues
      • Streaming from APIs
      • Streaming from databases
      • Data orchestration, transformation and processing
      • Usage of Python and Pandas
      • KPI Monitoring
      • OKRs and custom metrics
      • Data Issues & Incidents
      • Reporting
      • Other functional use cases
    • Industry-specific use cases
      • Finance and Payments
      • E-commerce & Logistics
      • Customer Success
      • Security, Risk, and Anti-Fraud
      • Anti-Money Laundering (AML)
  • 🔌API
    • OAuth clients
    • API Reference
  • 👁️‍🗨️Other resources
    • FAQ
    • Our blog on Medium
Powered by GitBook
On this page
  • General KPI monitoring
  • AVG, SUM, MIN, MAX, and other aggregated monitoring
  • ARR Monitoring
  • MRR monitoring
  • Stream sales or other revenue KPIs
  • Monitor average value per customer

Was this helpful?

Edit on GitHub
  1. Use cases, patterns, templates, examples
  2. Functional use cases

KPI Monitoring

PreviousUsage of Python and PandasNextOKRs and custom metrics

Last updated 8 months ago

Was this helpful?

General KPI monitoring

Ylem provides an extremely powerful way of calculating various KPIs from commonly known metrics (ARR, MRR, LTV, etc) to custom ones, that you can define on your own.

Metrics can be calculated in the itself or using an .

Typically the result is compared with a certain target and sent as a notification to Slack or channels afterward.

AVG, SUM, MIN, MAX, and other aggregated monitoring

The pipeline above can be used for monitoring different KPIs represented by mathematical functions such as average values, number of items, minimal and maximal values, etc.

ARR Monitoring

MRR monitoring

Stream sales or other revenue KPIs

Sales or other Revenue teams are the most KPI-driven in an organization. Ylem allows easy monitoring of their KPIs, comparing with a target, and taking different actions depending on whether it is already achieved or not yet:

Monitor average value per customer

Ylem allows easy monitoring of average values (amounts, orders, bank transfers, contract values) per customer. As an example the following pipeline represents the calculation of an average amount per customer and taking actions for different sizes of it:

More information about using them in and tasks can be found on a .

💼
Condition
Aggregator
special separate page
Query
Aggregator
Potential pipeline
Potential pipeline
Potential data extraction
Potential pipeline
Potential data extraction
Pipeline example for Sales KPIs
Pipeline example
Possible SQL query
Possible filter task