working-with-resources

Enrich events with mutable resource state using OPAL temporal joins.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rustomax/observe-community-mcp --skill working-with-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: working-with-resources
Source: https://github.com/rustomax/observe-community-mcp/tree/main/skills/working-with-resources
Command: npx skills add https://github.com/rustomax/observe-community-mcp --skill working-with-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to enrich events and intervals with mutable resource state over time, using OPAL temporal joins to attach contextual state into analysis workflows and cross-dataset queries.

Core Features & Use Cases

  • Temporal joins: connect Resources to events using lookup, join, and follow to bring state changes over time.
  • Automatic field matching: align fields across datasets without manual ON clauses.
  • Mutable state tracking: work with Resources having Valid From/To timestamps to model state changes.
  • Use cases include enriching spans with service metadata, tracking resource evolution, and navigating between related datasets.

Quick Start

Use the working-with-resources skill to enrich a sample set of events with Resource context using the three join verbs (lookup, join, and follow).

Frequently Asked Questions about working-with-resources

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enrich observability events with mutable resource state over time?

You can enrich observability events with mutable resource state using temporal joins that automatically match fields and handle Valid From/To timestamps without explicit ON clauses.

What are OPAL temporal joins and how do they work for dataset navigation?

OPAL temporal joins connect Resources to events using three verbs—lookup, join, and follow—automatically aligning fields across datasets to bring state changes over time.

How do I track resource evolution when Valid From and To timestamps change?

Tracking resource evolution is handled by applying temporal joins to Resources with Valid From/To timestamps, attaching contextual state changes directly into cross-dataset queries.

Can I join datasets automatically without writing manual ON clauses?

Automatic field matching aligns fields across datasets without manual ON clauses, allowing you to attach and navigate resource context over time using lookup, join, and follow verbs.

Does this approach work for enriching spans with service metadata?

Enriching spans with service metadata is a supported use case, applying temporal joins to attach mutable resource state and track resource evolution across observability workflows.