Guidewire Observability

---
name: guidewire-observability
description: |
  Implement comprehensive observability for Guidewire InsuranceSuite including logging,
  metrics, tracing, and alerting.
  Trigger with phrases like "guidewire monitoring", "logging guidewire",
  "metrics", "observability", "alerting", "dashboards guidewire". Use when working with guidewire observability.
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Guidewire Observability

## Overview
Implement comprehensive observability for Guidewire InsuranceSuite including structured logging, metrics collection, distributed tracing, and intelligent alerting.

## Prerequisites
- Access to Guidewire Cloud Console logs
- Monitoring platform (Datadog, Splunk, New Relic, or similar)
- Understanding of observability principles

## Instructions

### Step 1: Observability Stack
┌─────────────────────────────────────────────────────────────────────────────────┐
### Step 2: Instructions
// Structured logging implementation
### Step 3: Key Metrics to Monitor
Implement key metrics to monitor.

For detailed implementation code and configurations, load the reference guide:
`Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)`

## Output
- Observability Stack
- Instructions
- Key Metrics to Monitor

## Error Handling
| Issue | Solution |
|-------|----------|
| Configuration error | Check settings |

## Resources
- [Guidewire Cloud Console](https://gcc.guidewire.com/)
- [OpenTelemetry Documentation](https://opentelemetry.io/docs/)

## Next Steps
For incident response procedures, see `guidewire-incident-runbook`.

## Examples

**Basic usage**: Apply guidewire observability to a standard project setup with default configuration options.

**Advanced scenario**: Customize guidewire observability for production environments with multiple constraints and team-specific requirements.