Evento Framework
  • Introduction
  • Architecture Overview
    • Distributed Systems & Microservices
    • Recative Manifesto & Reactive Principles
    • State-of-the-art Patterns
      • DDD (Domain Driven Design)
      • CQRS (Command Query Responsability Separation)
      • Event Sourcing
      • Messaging
      • Saga
  • GETTING STARTED
    • Quick Start
    • TodoList - RECQ Tutorial
      • Problem Description and Requirement Gathering
      • RECQ Payload Design
      • RECQ Components Design
      • Set up your Development Environment
      • RECQ Payload Evento Implementation
        • Domain Commands
        • Domain Events
        • Views
        • Queries
      • RECQ Components Evento Implementation with Spring Data
        • TodoListAggregate
        • TodoList Model with Spring Data
        • TodoListProjector
        • TodoListProjection
        • TodoList Invoker
      • Expose the RECQ architecture with Spring Web
      • Test Your App
    • Extend TodoList - Handle Complexity Tutorial
      • Unique identifier generation
      • Extends behaviors with Observer and Services
      • Cross Domain Consistency with Sagas
      • Handle Real time data updates with MQTT and Save-Notify Pattern
  • RECQ Patterns
    • RECQ Patterns
    • RECQ System Pattern
      • Component
      • Message Gateway
      • System State Store
    • RECQ Communication Pattern
      • Component to Component
      • Component to System State Store
      • System State Store to Component
    • RECQ Component Pattern
      • Aggregate
      • Projector
      • Projection
      • Service
      • Invoker
      • Saga
      • Observer
  • Evento Framework
    • Evento Framework Introcution
    • Payload and Messages
      • Command
        • Domain Command
        • Service Command
      • Event
        • Domain and Service Event
      • Query and View
    • @Component
      • @Aggregate
        • Aggregate State
        • @AggregateCommandHandler
        • @EventSourcingHandler
      • @Projector
        • Projector @EventHandler
      • @Projection
        • @QueryHandler
      • @Service
        • @CommandHandler
      • @Invoker
      • @Saga
        • SagaState
        • @SagaEventHandler
      • @Observer
    • Dead Event Queues
    • EventoBundle
      • EventoServerMessageBusConfiguration
      • ConsumerStateStore
        • InMemoryConsumerStateStore
        • PostgresConsumerStateStore
        • MysqlConsumerStateStore
      • Context
      • TracingAgend and @Track
        • SentryTracingAgent
      • Autoscaling Protocol
        • ThreadCountAutoscalingProtocol
      • Injector and @Component
  • Evento Server
    • Evento Server Introduction
    • SetUp Evento Server
      • Advanced Options
      • Evento Event Store Modes: APES and CPES
    • Evento Server Cluster
    • Bundle Deploy Script
  • EVENTO GUI
    • Explore RECQ Systems Visually
    • GUI Auth
    • Payload Catalog
    • Component Catalog
    • Bundle Catalog
    • Cluster Status (Experimental)
    • Flows
      • Performance Evaluation
    • Application Graph
    • System State Store
  • Evento CLI
    • Evento CLI Introduction
    • Update Version
    • Publish
Powered by GitBook
On this page
  1. EVENTO GUI

Cluster Status (Experimental)

The Cluster Status page provides a comprehensive overview of the health and status of your Evento cluster. It consists of two primary sections: Bundle Instances and Consumers.

PreviousBundle CatalogNextFlows

Last updated 9 months ago

Bundle Instances

The Bundle Instances section displays all connected bundles within your cluster. Each bundle is represented by a card containing essential information:

  • Bundle Name: The unique identifier of the bundle.

  • Status: The current status of the bundle (e.g., Available, Unavailable).

  • Replica Count: The number of instances running for the bundle.

  • Instance IDs: A list of the unique identifiers for each bundle instance.

Actions:

You can perform the following actions on bundle instances:

  • Spawn Instance: Create a new instance of the bundle to increase its capacity or redundancy.

  • Kill Instance: Terminate an existing instance of the bundle.

By monitoring the Bundle Instances section, you can ensure that your cluster has the necessary resources to handle the workload and maintain optimal performance.

Consumers

The Consumers section provides a list of all active consumers within your cluster. For each consumer, the following information is displayed:

  • Consumer Name (Identifier): The Consumer Identifier composed by the {{Component Name}} - {{Component Version}} ({{Context}})

  • Bundle

  • Shared Instances: A list of bundle instances with which the consumer is shared.

By clicking on a specific consumer, you can access additional details, such as:

  • Last Consumed Event Identifier: The identifier of the last event processed by the consumer.

  • Dead Event Queue: A list of events that failed to be processed, allowing for manual reprocessing.

The Cluster Status page, with its Bundle Instances and Consumers sections, offers a valuable tool for managing and monitoring your Evento cluster. By effectively utilizing this information, you can optimize performance, troubleshoot issues, and ensure the overall health of your system.

Note: Based on the provided information, the Consumers section appears to be under development, and the full functionality may not be available in the current version of the interface.

Bundle Instances
COnsumer Detailed Status