solace-agent-mesh 0.0.1__py3-none-any.whl → 0.1.0__py3-none-any.whl

solace_agent_mesh/configs/agent_global.yaml

@@ -0,0 +1,74 @@
+# This is the configuration file for the global agent
+#
+# It fulfills a few functions:
+# 1. A flow to do periodic registration of this agent with the orchestrator
+# 2. A flow to process action requests and produce action responses
+#    This requires a custom component to process the action requests
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+# trace:
+#   trace_file: agent_global.trace
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+# Take from CUST_DOCS and publish to Solace
+flows:
+
+  # Flow to handle action requests
+  - name: global_agent_action_request_processor
+    components:
+      # Input from a Solace broker
+      - component_name: broker_input
+        component_module: broker_input
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}agent_global_action_request
+          broker_subscriptions:
+            # Subscribe to all global actions - note that if we
+            # wanted to handle some global actions elsewhere, we would
+            # need to be more specific here
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/actionRequest/*/*/global/>
+              qos: 1
+
+      # Custom component to process the action request
+      - component_name: action_request_processor
+        component_base_path: .
+        component_module: src.agents.global.global_agent_component
+        component_config:
+          max_allowed_file_retrieve_size: 300000 # Approx 60k tokens
+          llm_service_topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/llm-service/request/general-good/
+          embedding_service_topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/embedding-service/request/text/
+        broker_request_response:
+          enabled: true
+          broker_config: *broker_connection
+          request_expiry_ms: 120000
+          payload_encoding: utf-8
+          payload_format: json
+          response_topic_prefix: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1
+          response_queue_prefix: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1
+        component_input:
+          source_expression: input.payload
+
+      # Output to a Solace broker
+      - component_name: broker_output
+        component_module: broker_output
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          copy_user_properties: true

solace_agent_mesh/configs/agent_image_processing.yaml

@@ -0,0 +1,82 @@
+# This is the configuration file for the Image Processing agent
+#
+# It fulfills a few functions:
+# 1. A flow to do periodic registration of this agent with the orchestrator
+# 2. A flow to process action requests and produce action responses
+#    This requires a custom component to process the action requests
+# Requires the following environment variables:
+# - ${SOLACE_BROKER_URL}
+# - ${SOLACE_BROKER_USERNAME}
+# - ${SOLACE_BROKER_PASSWORD}
+# - ${SOLACE_BROKER_VPN}
+# - ${SOLACE_AGENT_MESH_NAMESPACE}
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+# trace:
+#   trace_file: agent_image_processing.trace
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+# Take from Slack and publish to Solace
+flows:
+  # Flow to handle action requests
+  - name: image_processing_agent_action_request_processor
+
+    components:
+      # Input from a Solace broker
+      - component_name: broker_input
+        component_module: broker_input
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}agent_image_processing_action_request
+          broker_subscriptions:
+            # Subscribe to all image_processing actions - note that if we
+            # wanted to handle some image_processing actions elsewhere, we would
+            # need to be more specific here
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/actionRequest/*/*/image_processing/>
+              qos: 1
+
+      # Custom component to process the action request
+      - component_name: action_request_processor
+        component_base_path: .
+        component_module: src.agents.image_processing.image_processing_agent_component
+        component_config:
+          image_gen_model: ${IMAGE_GEN_MODEL}
+          image_gen_endpoint: ${IMAGE_GEN_ENDPOINT}
+          image_gen_api_key: ${IMAGE_GEN_API_KEY}
+          image_gen_litellm_config: {}
+          llm_service_topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/llm-service/request/general-good/
+        broker_request_response:
+          enabled: true
+          broker_config: *broker_connection
+          request_expiry_ms: 120000
+          payload_encoding: utf-8
+          payload_format: json
+          response_topic_prefix: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1
+          response_queue_prefix: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1
+        component_input:
+          source_expression: input.payload
+
+      # Output to a Solace broker
+      - component_name: broker_output
+        component_module: broker_output
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          copy_user_properties: true

solace_agent_mesh/configs/agent_slack.yaml

@@ -0,0 +1,64 @@
+# This is the configuration file for the Slack agent
+#
+# It fulfills a few functions:
+# 1. A flow to do periodic registration of this agent with the orchestrator
+# 2. A flow to process action requests and produce action responses
+#    This requires a custom component to process the action requests
+# Requires the following environment variables:
+# - SOLACE_BROKER_URL
+# - SOLACE_BROKER_USERNAME
+# - SOLACE_BROKER_PASSWORD
+# - SOLACE_BROKER_VPN
+# - SOLACE_AGENT_MESH_NAMESPACE
+# - MONITOR_SLACK_BOT_TOKEN
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+flows:
+  # Flow to handle action requests
+  - name: action_request_processor
+    components:
+      # Input from a Solace broker
+      - component_name: broker_input
+        component_module: broker_input
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}agent_slack_action_request
+          broker_subscriptions:
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/actionRequest/*/*/slack/>
+              qos: 1
+
+      # Custom component to process the action request
+      - component_name: action_request_processor
+        component_base_path: .
+        component_module: src.agents.slack.slack_agent_component
+        component_config:
+          slack_bot_token: ${MONITOR_SLACK_BOT_TOKEN}
+          thread_cache_ttl: 600
+        component_input:
+          source_expression: input.payload
+
+      # Output to a Solace broker
+      - component_name: broker_output
+        component_module: broker_output
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          copy_user_properties: true

solace_agent_mesh/configs/agent_web_request.yaml

@@ -0,0 +1,75 @@
+# This is the configuration file for the Web Request agent
+#
+# It fulfills a few functions:
+# 1. A flow to do periodic registration of this agent with the orchestrator
+# 2. A flow to process action requests and produce action responses
+#    This requires a custom component to process the action requests
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+# trace:
+#   trace_file: agent_web_request.trace
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+# Take from Slack and publish to Solace
+flows:
+
+  # Flow to handle action requests
+  - name: action_request_processor
+
+    components:
+
+      # Input from a Solace broker
+      - component_name: broker_input
+        component_module: broker_input
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}agent_web_request_action_request
+          broker_subscriptions:
+            # Subscribe to all web_request actions - note that if we
+            # wanted to handle some web_request actions elsewhere, we would
+            # need to be more specific here
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/actionRequest/*/*/web_request/>
+              qos: 1
+
+      # Custom component to process the action request
+      - component_name: action_request_processor
+        num_instances: 10
+        component_base_path: .
+        component_module: src.agents.web_request.web_request_agent_component
+        broker_request_response:
+          enabled: true
+          broker_config: *broker_connection
+          request_expiry_ms: 120000
+          payload_encoding: utf-8
+          payload_format: json
+          response_topic_prefix: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1
+          response_queue_prefix: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1
+        component_config:
+          llm_service_topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/llm-service/request/general-good/
+        component_input:
+          source_expression: input.payload
+
+      # Output to a Solace broker
+      - component_name: broker_output
+        component_module: broker_output
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          copy_user_properties: true

solace_agent_mesh/configs/conversation_to_file.yaml

@@ -0,0 +1,56 @@
+---
+log:
+  stdout_log_level: ERROR
+
+# trace:
+#   trace_file: conversation_to_file.trace
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+# Take from Slack and publish to Solace
+flows:
+  - name: write_to_file
+    components:
+      - component_name: broker_input
+        component_module: broker_input
+        component_config: 
+          <<: *broker_connection
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}conversation_to_file
+          broker_subscriptions:
+            - topic: "!${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/register/>"
+              qos: 1
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/>
+              qos: 1
+          payload_encoding: utf-8
+          payload_format: json
+
+      - component_name: conversation_formatter
+        component_base_path: .
+        component_module: src.tools.components.conversation_formatter
+        component_config:
+        component_input:
+          source_expression: input
+
+      - component_name: file_output
+        component_module: file_output
+        component_config:
+        input_transforms:
+          - type: copy
+            source_expression: template:trace_{{text://input.user_properties:channel}}_{{text://input.user_properties:identity}}.txt
+            dest_expression: user_data.component_input:file_path
+          - type: copy
+            source_expression: previous:message
+            dest_expression: user_data.component_input:content
+          - type: copy
+            source_value: a
+            dest_expression: user_data.component_input:mode
+        component_input:
+          source_expression: user_data.component_input

solace_agent_mesh/configs/error_catcher.yaml

@@ -0,0 +1,56 @@
+# This is the configuration file for the error catcher flow
+#
+# This config file must be included with every running instance within the Solace Agent Mesh
+#
+# 1. It uses the error_input component to receive messages from the error queue
+# 2. Sends the error message to the broker
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+# trace:
+#   trace_file: orchestrator.trace
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+flows:
+
+  # Error flow - if an error happens the message will be sent to this flow
+  - name: error-catcher-flow
+    # Disable the error queue to avoid infinite loops
+    put_errors_in_error_queue: false
+    components:
+
+      # Input from the Error Queue
+      - component_name: error_input
+        component_module: error_input
+
+      # If it wasn't filtered, it means that there was a channel in the user_properties
+      # This means that we can send the error message to the channel
+      - component_name: broker_output_error_message
+        component_module: broker_output
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          copy_user_properties: true
+        input_transforms:
+          - type: copy
+            source_expression: input.payload
+            dest_expression: user_data.output:payload
+          - type: copy
+            source_expression: template:${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/stimulus/error/error-flow
+            dest_expression: user_data.output:topic
+        component_input:
+          source_expression: user_data.output

solace_agent_mesh/configs/monitor_stim_and_errors_to_slack.yaml

@@ -0,0 +1,106 @@
+# Configuration for the Slack Monitor Agent
+#
+# This sets up:
+# 1. Agent registration flow
+# 2. Action request processing flow
+# 3. Event monitoring flow for tracking all solace agent mesh events
+#
+# Required environment variables:
+# - SOLACE_BROKER_URL
+# - SOLACE_BROKER_USERNAME
+# - SOLACE_BROKER_PASSWORD
+# - SOLACE_BROKER_VPN
+# - SOLACE_AGENT_MESH_NAMESPACE
+# - MONITOR_SLACK_STATUS_CHANNEL
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+flows:
+
+  # Event monitoring flow
+  - name: event_monitor
+    put_errors_in_error_queue: false
+    components:
+      # Input from broker - subscribe to all solace agent mesh events
+      - component_name: broker_input
+        component_module: broker_input
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}agent_slack_monitor_events
+          broker_subscriptions:
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/>
+              qos: 1
+            - topic: "!${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/register/>"
+              qos: 1
+
+      # Process events
+      - component_name: event_processor
+        component_base_path: .
+        component_module: src.monitors.stim_and_errors.stim_and_error_monitor
+        component_config:
+          notification_flow_name: slack_notification
+          stimulus_ttl: 300
+          error_format: slack
+
+  # Send notifications - this is called directly by the monitor
+  - name: slack_notification
+    put_errors_in_error_queue: false
+    components:
+
+      # Output to the broker to call the appropriate agent's action
+      - component_name: broker_output
+        component_module: broker_output
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          copy_user_properties: true
+        input_transforms:
+          - type: copy
+            source_expression: input.payload:is_last
+            dest_expression: user_data.output:payload.action_params.last_post_to_thread
+          - type: copy
+            source_expression: input.payload:correlation_id
+            dest_expression: user_data.output:payload.action_params.thread_correlation_id
+          - type: copy
+            source_expression: input.payload:text
+            dest_expression: user_data.output:payload.action_params.text
+          - type: copy
+            source_expression: input.payload:blocks
+            dest_expression: user_data.output:payload.action_params.blocks
+          - type: copy
+            source_expression: input.payload:files
+            dest_expression: user_data.output:payload.action_params.files
+          - type: copy
+            source_value: ${MONITOR_SLACK_STATUS_CHANNEL}
+            dest_expression: user_data.output:payload.action_params.channel
+          - type: copy
+            source_value: slack
+            dest_expression: user_data.output:payload.agent_name
+          - type: copy
+            source_value: post_message
+            dest_expression: user_data.output:payload.action_name
+          - type: copy
+            source_value: '0'
+            dest_expression: user_data.output:payload.action_idx
+          - type: copy
+            source_expression: template:${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/actionRequest/monitor/x/slack/post_message/{{text://input.payload:correlation_id}}
+            dest_expression: user_data.output:topic
+        input_selection:
+          source_expression: user_data.output

solace_agent_mesh/configs/monitor_user_feedback.yaml

@@ -0,0 +1,58 @@
+# Configuration for the Slack Monitor Agent
+#
+# This sets up:
+# 1. Agent registration flow
+# 2. Action request processing flow
+# 3. Event monitoring flow for tracking all solace agent mesh events
+#
+# Required environment variables:
+# - SOLACE_BROKER_URL
+# - SOLACE_BROKER_USERNAME
+# - SOLACE_BROKER_PASSWORD
+# - SOLACE_BROKER_VPN
+# - SOLACE_AGENT_MESH_NAMESPACE
+# - MONITOR_SLACK_STATUS_CHANNEL
+
+---
+log:
+  stdout_log_level: INFO
+  log_file_level: INFO
+  log_file: solace_ai_connector.log
+
+shared_config:
+  - broker_config: &broker_connection
+      broker_connection_share: ${SOLACE_BROKER_URL}
+      dev_mode: ${SOLACE_DEV_MODE, false}
+      broker_url: ${SOLACE_BROKER_URL}
+      broker_username: ${SOLACE_BROKER_USERNAME}
+      broker_password: ${SOLACE_BROKER_PASSWORD}
+      broker_vpn: ${SOLACE_BROKER_VPN}
+      temporary_queue: ${USE_TEMPORARY_QUEUES, false}
+
+flows:
+
+  # Feedback monitoring flow
+  - name: feedback_monitor
+    put_errors_in_error_queue: false
+    components:
+      # Input from broker - subscribe to all solace agent mesh events
+      - component_name: broker_input
+        component_module: broker_input
+        component_config:
+          <<: *broker_connection
+          payload_encoding: utf-8
+          payload_format: json
+          broker_queue_name: ${SOLACE_AGENT_MESH_NAMESPACE}user_feedback_monitor
+          broker_subscriptions:
+            - topic: ${SOLACE_AGENT_MESH_NAMESPACE}solace-agent-mesh/v1/feedback
+              qos: 1
+
+      # Process events
+      - component_name: user_feedback_processor
+        component_base_path: .
+        component_module: src.monitors.feedback.user_feedback_monitor
+        component_config: {}
+        component_input:
+          source_expression: input.payload
+
+