Skip to main content

​
What are Integration Resources?

Integration resources are structured metadata that describe how your organization uses tools and systems such as Datadog, New Relic, Buildkite, GitHub, and others. They help TierZero understand:
  • What tags and attributes are used across your logs, metrics, events, and spans
  • What repositories exist and where relevant code is located
  • Which dashboards, notebooks, and documents contain important operational insights
  • Which CI/CD pipelines exist and what they do

​
Why Integration Resources?

Your integrations provide raw data (logs, metrics, traces, commits), but TierZero needs context to interpret that data meaningfully. By cataloging these integration resources, you give TierZero the domain knowledge needed to investigate issues effectively and provide accurate recommendations.

​
Supported Resources

Some integration resources are automatically imported and remain read-only such as dashboards and repositories and others are auto-populated with defaults that you can customize such as logs and spans configurations.

​
Buildkite

  • pipelines.json - List of Buildkite pipelines including relevant annotations and artifacts
  • test_suites.json - List of Buildkite test suites

​
CloudWatch

  • log_groups.json - List of CloudWatch log groups and its fields
  • metrics.json - List of CloudWatch metrics

​
Datadog

  • ci_events_tags.json - Tags and attributes of CI pipeline events
  • dashboards.json - List of dashboards that have been ingested
  • events_tags.json - Tags and attributes of events
  • logs_tags.json - Tags and attributes of logs
  • metrics.json - List of Datadog metrics
  • notebooks.json - List of notebooks that have been ingested
  • rum_tags.json - Tags and attributes of RUM events
  • spans_tags.json - Tags and attributes of spans

​
GitHub

  • repositories.json - List of GitHub repositories

​
New Relic

  • applications.json - List of New Relic applications
  • dashboards.json - List of dashboards that have been ingested
  • logs_attrs.json - Attributes of logs
  • metrics.json - List of New Relic metrics
  • spans_attrs.json - Attributes of spans
  • transactions_attrs.json - Attributes of transactions

​
Notion

  • pages.json - List of Notion pages that have been ingested

​
Sentry

  • issues_tags.json - Tags of issues
  • projects.json - List of Sentry projects

​
Temporal

  • namespaces.json - List of Temporal namespaces

​
Using Integration Resources

​
Accessing Integration Resources

  1. Navigate to Knowledge → Integration Resources in your TierZero app
  2. Browse resources by integration type (Datadog, Buildkite, GitHub, etc.)
  3. Select a resource type to view or edit its configuration

​
Ingesting Resources

Depending on the resource type, you may import or ingest a resource by URL or ID, or configure via JSON: Importing by URL or ID (Dashboards, Notebooks, Notion Pages):
  1. Navigate to the resource type (e.g., Datadog → Dashboards).
  2. Click the Ingest button.
  3. Paste the URL or ID of the resource you want to import.
  4. TierZero will fetch and index the content.
Configuring via JSON (Logs, Spans, Pipelines):
  1. Navigate to the resource type (e.g., Buildkite → Pipelines or Datadog → Logs).
  2. View existing configuration or click Copy Template for a starter structure.
  3. Edit the JSON with your specific metadata.
  4. Click Save to apply your changes.

​
Configuration Examples

Example - Importing a Datadog Dashboard: 
ID: abc-123-xyz
TierZero will extract the dashboard’s metrics, queries, and visualizations to understand what’s important in your observability setup. Example - Configuring a Buildkite Pipeline: 
[
  {
    "name": "Production Deploy",
    "slug": "production-deploy",
    "description": "Main deployment pipeline for production environment. Runs on every merge to main branch.",
    "url": "https://buildkite.com/acme/production-deploy",
    "annotations": [
      {
        "name": "Deploy Summary",
        "context": "deploy-summary",
        "description": "Summary of deployment steps and affected services"
      }
    ],
    "artifacts": [
      {
        "name": "Deploy Logs",
        "job_name": "Deploy Logs",
        "artifact_path": "logs/deploy.log",
        "description": "Detailed deployment logs including kubectl output"
      }
    ]
  }
]
Example - Configuring Datadog Logs: 
{
  "tags": [
    {
      "name": "service",
      "description": "The microservice that emitted the log"
    },
    {
      "name": "env",
      "description": "Environment: production, staging, or development"
    },
    {
      "name": "user_tier",
      "description": "Customer tier: free, pro, or enterprise. Used for prioritizing issues."
    }
  ],
  "attributes": [
    {
      "name": "@user_id",
      "description": "Unique identifier for the user experiencing the issue"
    },
    {
      "name": "@request_id",
      "description": "Trace ID for correlating logs with distributed traces"
    }
  ]
}

​
Best Practices

1. Start with Critical Systems Focus first on your most important services, pipelines, and data sources. You don’t need to catalog everything - prioritize what matters most for incident response. 2. Document Important Tags and Attributes Highlight the tags and attributes that are essential for troubleshooting. 3. Add Concrete Descriptions Use concrete descriptions to describe the semantics of each resource:
  • ✅ “The trace ID for correlating logs with distributed traces”
  • ❌ “The trace ID”