跳转至

Core concepts（核心概念）

This page provides an introduction to the core concepts underlying monitoring views.

  • Metric: Resources emit metrics, or logs. Monitors are created on top of these metrics to set a user’s standards of performance on a given resource.
  • Resource: A “thing” in Foundry that can be monitored, including datasets, agents, schedules, objects, and link types.
  • Scope: A scope is the boundary around the set of resources on which your thresholds are set. Scopes can be static or dynamic:
  • Static scopes monitor a fixed resource that you explicitly select:
    • Single: The monitor is only applied to that specific resource.
  • Dynamic scopes automatically update as resources are added or removed, without requiring manual changes to the monitor:
    • Folder: The monitor is applied to resources of the specified type in the scoped folder, not including subfolders.
    • Project: The monitor is applied to any resources of the specified type in the project or multiple projects.
    • Workflow Lineage: For function and action type monitors, the monitor is applied to all functions or actions used by a Workflow Lineage.
    • Workshop: For function and action type monitors, the monitor is applied to all functions or actions used by a Workshop application.
    • OSDK application: For function and action type monitors, the monitor is applied to all functions or actions used by an OSDK application.
  • Monitoring rule: A threshold or set of thresholds put on the metrics of a resource within a given scope and contain:
  • Resource type
  • Metric threshold tolerances
  • Severity level assignment
  • Monitoring view: A collection of monitoring rules that a group of subscribers care about.
  • Subscriber: A user subscribed to a monitoring view.
  • Alerts: Notifications that can have low, medium, or high assignments and are sent to subscribers.
  • Severity: A label assigned to a monitoring rule that classifies the urgency of alerts it produces. Monitoring views support three severity levels: LOW, MEDIUM, and HIGH. Severity acts as a routing mechanism: in-Foundry notifications and each external integration are configured against a specific severity level, and only alerts matching that severity trigger the integration. You can map severity levels to notification channels in whatever way fits your team's workflow — for example, a team running a critical pipeline might route HIGH to an on-call paging tool while sending MEDIUM and LOW to the same review queue, whereas a team monitoring a low-stakes resource might direct all three severities to a single chat channel.

中文翻译

核心概念

本文档介绍监控视图（monitoring views）所涉及的核心概念。

  • 指标（Metric）： 资源会发出指标或日志。监控器（monitors）基于这些指标创建，用于设定用户在特定资源上的性能标准。
  • 资源（Resource）： Foundry 中可被监控的"对象"，包括数据集（datasets）、代理（agents）、调度（schedules）、对象（objects）和链接类型（link types）。
  • 范围（Scope）： 范围是围绕资源集合的边界，您在此边界内设置阈值。范围可以是静态或动态的：
  • 静态范围（Static scopes） 监控您明确选定的固定资源：
    • 单一（Single）： 监控器仅应用于该特定资源。
  • 动态范围（Dynamic scopes） 会在资源添加或移除时自动更新，无需手动修改监控器：
    • 文件夹（Folder）： 监控器应用于指定范围内文件夹中特定类型的资源，不包括子文件夹。
    • 项目（Project）： 监控器应用于单个或多个项目中指定类型的任何资源。
    • 工作流血缘（Workflow Lineage）： 对于函数和操作类型的监控器，监控器应用于工作流血缘所使用的所有函数或操作。
    • Workshop： 对于函数和操作类型的监控器，监控器应用于 Workshop 应用程序所使用的所有函数或操作。
    • OSDK 应用程序（OSDK application）： 对于函数和操作类型的监控器，监控器应用于 OSDK 应用程序所使用的所有函数或操作。
  • 监控规则（Monitoring rule）： 针对给定范围内资源指标设置的一个或多个阈值，包含：
  • 资源类型
  • 指标阈值容差
  • 严重级别分配
  • 监控视图（Monitoring view）： 一组订阅者关注的监控规则集合。
  • 订阅者（Subscriber）： 订阅了监控视图的用户。
  • 警报（Alerts）： 可分配为低、中或高严重级别的通知，并发送给订阅者。
  • 严重级别（Severity）： 分配给监控规则的标签，用于对其产生的警报进行紧急程度分类。监控视图支持三个严重级别：LOW、MEDIUM 和 HIGH。严重级别充当路由机制：Foundry 内部通知以及每个外部集成均针对特定严重级别进行配置，只有匹配该严重级别的警报才会触发集成。您可以根据团队的工作流程将严重级别映射到通知渠道——例如，运行关键管道的团队可能将 HIGH 路由到值班寻呼工具，同时将 MEDIUM 和 LOW 发送到同一个审查队列；而监控低风险资源的团队则可能将所有三个严重级别都导向同一个聊天频道。