redfish eventservice

Redfish EventService Resource

Table of Contents

• Overview
  • References
• Implementation Guidelines
• URIs - Supported
  • Status Indicators
• URIs - Not Supported
• URIs - To be Analysed
  • GET /redfish/v1/EventService - Event Service Endpoint
  • GET /redfish/v1/EventService/Subscriptions - Event Subscriptions Collection
  • POST /redfish/v1/EventService/Subscriptions - Create Event Subscription
  • GET /redfish/v1/EventService/Subscriptions/{SubscriptionId} - Individual Subscription
  • PATCH /redfish/v1/EventService/Subscriptions/{SubscriptionId} - Update Subscription
  • DELETE /redfish/v1/EventService/Subscriptions/{SubscriptionId} - Delete Subscription
  • POST /redfish/v1/EventService/Actions/EventService.SubmitTestEvent - Submit Test Event
  • GET /redfish/v1/EventService/EventDestinations - Event Destinations Collection
  • POST /redfish/v1/EventService/EventDestinations - Create Event Destination
  • GET /redfish/v1/EventService/EventDestinations/{EventDestinationId} - Individual Event Destination
• Property Support Summary
  • Properties with DMT Limitations
  • Properties Not Applicable for DMT

Overview

The EventService resource provides comprehensive event handling capabilities for the DMT Console's Redfish implementation. This service-level resource manages event subscriptions, notifications, and event processing while integrating with the existing DMT event infrastructure and AMT device event systems.

📋 PLANNING STATUS: This document represents future planning for EventService implementation in DMT Console. All endpoints and features described are currently in the analysis and design phase and are planned for future development.

Endpoint Overview:

• EventService - Provides centralized event management and subscription services
• Event Subscription Management - Handles client subscription creation, configuration, and lifecycle
• Event Filtering and Routing - Implements event type filtering and conditional routing
• Push Notification Mechanisms - Delivers real-time events via webhooks and callbacks
• AMT Integration - Translates AMT device events to Redfish format

References

• DMTF Redfish Specification: EventService Schema
• DMTF Event Schema: Event Schema
• AMT Event System: Intel AMT device event infrastructure
• DMT Event Infrastructure: Existing DMT event handling system

Implementation Guidelines

The EventService implementation must:

1. AMT Integration: Seamlessly integrate with Intel AMT device event systems
2. Standards Compliance: Maintain full compatibility with DMTF Redfish EventService standards
3. Real-time Processing: Provide low-latency event processing and delivery
4. Scalability: Support high-volume event processing for large device deployments
5. Security: Implement secure event transmission and subscriber authentication
6. Reliability: Ensure reliable event delivery with appropriate retry mechanisms

URIs - Supported

Status Indicators

• ✅ Supported - Fully implemented and tested
• 🚧 In Progress - Currently under development
• 📋 Planned - Scheduled for future implementation

Note: All endpoints are currently in planning phase and will be implemented as part of the Redfish service expansion.

URIs - Not Supported

This section will be populated with endpoints that are not supported in the current implementation.

URIs - To be Analysed

The following EventService endpoints require analysis for DMT Console integration, based on DMTF Redfish Publications OpenAPI specification:

GET /redfish/v1/EventService - Event Service Endpoint

Status: 📋 Planned

Purpose: Retrieve event service configuration and capabilities

DMT Integration: Integrate with existing DMT event infrastructure

GET /redfish/v1/EventService/Subscriptions - Event Subscriptions Collection

Status: 📋 Planned

Purpose: Retrieve collection of event subscriptions

DMT Integration: Map to DMT subscription management

POST /redfish/v1/EventService/Subscriptions - Create Event Subscription

Status: 📋 Planned

Purpose: Create new event subscription

DMT Integration: Use DMT subscription workflow

GET /redfish/v1/EventService/Subscriptions/{SubscriptionId} - Individual Subscription

Status: 📋 Planned

Purpose: Retrieve individual subscription details

DMT Integration: Map to DMT subscription data

PATCH /redfish/v1/EventService/Subscriptions/{SubscriptionId} - Update Subscription

Status: 📋 Planned

Purpose: Update subscription properties

DMT Integration: Use DMT subscription modification

DELETE /redfish/v1/EventService/Subscriptions/{SubscriptionId} - Delete Subscription

Status: 📋 Planned

Purpose: Delete event subscription

DMT Integration: Use DMT subscription cleanup

POST /redfish/v1/EventService/Actions/EventService.SubmitTestEvent - Submit Test Event

Status: 📋 Planned

Purpose: Submit test event for validation

DMT Integration: Test event delivery mechanisms

GET /redfish/v1/EventService/EventDestinations - Event Destinations Collection

Status: 📋 Planned

Purpose: Retrieve collection of event destinations

DMT Integration: Map to DMT event destination management

POST /redfish/v1/EventService/EventDestinations - Create Event Destination

Status: 📋 Planned

Purpose: Create new event destination

DMT Integration: Use DMT destination creation workflow

GET /redfish/v1/EventService/EventDestinations/{EventDestinationId} - Individual Event Destination

Status: 📋 Planned

Purpose: Retrieve individual event destination details

DMT Integration: Map to specific destination configuration

Property Support Summary

Properties with DMT Limitations

This section will be populated with properties that have limitations in the DMT Console context.

Properties Not Applicable for DMT

This section will be populated with properties that are not applicable in the DMT Console environment.