<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aura – </title>
    <link>/docs/aura-releases/metallica/changelog/</link>
    <description>Recent content on Aura</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
	  <atom:link href="/docs/aura-releases/metallica/changelog/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-system-components-version/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-system-components-version/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-system-components-versions&#34;&gt;Aura system components versions&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Updated versions of Aura system components for the current Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;components-versions&#34;&gt;Components versions&lt;/h2&gt;
&lt;p&gt;All components in the table below run over &lt;strong&gt;AKS cluster version 1.30&lt;/strong&gt;&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Name&lt;/th&gt;
&lt;th&gt;Namespace&lt;/th&gt;
&lt;th&gt;Image deployed&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;alertmanager&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/alertmanager:v0.26.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;elastic-operator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;docker.elastic.co/eck/eck-operator:2.7.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;elasticsearch-es-aura&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/elasticsearch:8.16.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;elasticsearch-exporter&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/elasticsearch_exporter:v1.5.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;fluent-bit-aggregator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/fluent-bit:3.2.2&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;grafana&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/grafana:10.3.3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;kibana-kb&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;docker.elastic.co/kibana/kibana:8.16.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;prometheus&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/prom/prometheus:v2.53.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;mongodb-atlas-operator&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/mongodb-atlas-kubernetes-operator:2.1.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;redis-exporter&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/redis-exporter:1.6.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;redis&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/redis:6.0.19&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;thanos-store-gateway&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/thanos:v0.32.5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;atlas-logger&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/atlas-logger:2.0.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;azure-logger&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/azure-logger:1.4.0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;pushgateway&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/pushgateway:v1.4.1&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;thanos-querier&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;aura-system&lt;/td&gt;
&lt;td&gt;devopstf.azurecr.io/tools/thanos:v0.32.5&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id=&#34;additional-information&#34;&gt;Additional information&lt;/h2&gt;
&lt;p&gt;Information regarding Aura system components end-of-life (EOL) and next updates is included in the document &lt;em&gt;&lt;strong&gt;Scheduled updates in Aura components&lt;/strong&gt;&lt;/em&gt;. Find it in the &lt;a href=&#34;../../../../docs/aura-releases/&#34;&gt;Aura releases&lt;/a&gt; section
of your corresponding release.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/atria-model-gateway/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/atria-model-gateway/</guid>
      <description>
        
        
        &lt;h1 id=&#34;atria-model-gateway-changelog&#34;&gt;Atria Model Gateway changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Atria Model Gateway for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-17---new-section-for-atria-technical-operation&#34;&gt;2025-02-17 - New section for ATRIA technical operation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new section has been added to Aura Technical Documentation website that includes &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; technical operational flows, designed as sequence diagrams to provide a clear, step-by-step representation of &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; capabilities and processes, interactions between components or systems, and the overall &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; workflow.&lt;/li&gt;
&lt;li&gt;The operational flowcharts for &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; Generative capability have been updated in this section.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-operation/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; technical operation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-14---apification-of-atria-model-gateway-configuration&#34;&gt;2025-02-14 - Apification of atria-model-gateway configuration&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The configuration of &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; components, including &lt;em&gt;&lt;strong&gt;atria-model-gateway&lt;/strong&gt;&lt;/em&gt;, has been redesigned through a new, more generalizable architecture. This approach simplifies and decentralizes chains management. Additionally, the architecture is prepared for upcoming &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; scenarios with more available LLM/RAG chains and different objectives.&lt;/li&gt;
&lt;li&gt;Consequently, two main tasks have been executed:
&lt;ul&gt;
&lt;li&gt;Refactor of configuration parameters, both for the server configuration and parameters related to use cases development&lt;/li&gt;
&lt;li&gt;Apification of configuration parameters for &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; use cases constructors, that can be easily modified through the swagger
&lt;br&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/atria-default-configuration/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; default configuration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/modify-atria-configuration/&#34;&gt;Modify &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration: Configure &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; presets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/import-documents/&#34;&gt;Import documents to &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-14---atria-presets-configuration-through-api&#34;&gt;2025-02-14 - ATRIA presets configuration through API&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Presets, that is, configurable entities to define the instructions to work with the AI model for the resolution of a use case, can be modified through the API swagger &lt;a href=&#34;../../../../docs/components/aura-configuration-api/api-definition/preset/&#34;&gt;Aura Configuration API Preset&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/modify-atria-configuration&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration: Configure &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; presets&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/atria-rag-server/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/atria-rag-server/</guid>
      <description>
        
        
        &lt;h1 id=&#34;atria-rag-server-changelog&#34;&gt;Atria RAG Server changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Atria RAG Server for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-17---new-section-for-atria-technical-operation&#34;&gt;2025-02-17 - New section for ATRIA technical operation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new section has been added to Aura Technical Documentation website that includes &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; technical operational flows, designed as sequence diagrams to provide a clear, step-by-step representation of &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; capabilities and processes, interactions between components or systems, and the overall &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; workflow.&lt;/li&gt;
&lt;li&gt;The operational flowcharts for &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; RAG capability have been updated in this section.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-operation/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; technical operation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-17---added-aura-copilot-rag-operational-workflow&#34;&gt;2025-02-17 - Added Aura Copilot RAG operational workflow&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added the operational flow corresponding to the call that &lt;em&gt;&lt;strong&gt;aura-copilot&lt;/strong&gt;&lt;/em&gt; makes to the &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; RAG capability into a new section &amp;ldquo;Technical operation&amp;rdquo;&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-operation/copilot-operational-flow/&#34;&gt;Copilot RAG operational workflow&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-14---apification-of-atria-rag-server-configuration&#34;&gt;2025-02-14 - Apification of atria-rag-server configuration&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The configuration of &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; components, including &lt;em&gt;&lt;strong&gt;atria-rag-server&lt;/strong&gt;&lt;/em&gt;, has been redesigned through a new, more generalizable architecture. This approach simplifies and decentralizes chains management. Additionally, the architecture is prepared for upcoming &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; scenarios with more available LLM/RAG chains and different objectives.&lt;/li&gt;
&lt;li&gt;Consequently, two main tasks have been executed:
&lt;ul&gt;
&lt;li&gt;Refactor of configuration parameters, both for the server configuration and parameters related to use cases development&lt;/li&gt;
&lt;li&gt;Apification of configuration parameters for &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; use cases constructors, that can be easily modified through the swagger
&lt;br&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/atria-default-configuration/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; default configuration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/modify-atria-configuration/&#34;&gt;Modify &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration: Configure &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; presets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/import-documents/&#34;&gt;Import documents to &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-14---atria-presets-configuration-through-api&#34;&gt;2025-02-14 - ATRIA presets configuration through API&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Presets, that is, configurable entities to define the instructions to work with the AI model for the resolution of a use case, can be modified through the API swagger &lt;a href=&#34;../../../../docs/components/aura-configuration-api/api-definition/preset/&#34;&gt;Aura Configuration API Preset&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/modify-atria-configuration&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration: Configure &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; presets&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-analytics/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-analytics/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-analytics-200-changelog&#34;&gt;Aura Analytics 2.0.0 changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Analytics 2.0.0 for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-20---aura-analytics-200&#34;&gt;2025-02-20 - Aura Analytics 2.0.0&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Version 2.0.0. of &lt;strong&gt;Aura Analytics&lt;/strong&gt; is launched. In this version, this tool has undergone a refactor to improve its structure and make it easier to understand, maintain and extend in the future.&lt;/li&gt;
&lt;li&gt;This version also simplifies the deployment and execution process and allows managing both processed and to-process files centrally in one place (database).&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers-workspace/monitoring/active-listening/&#34;&gt;Aura Analytics 2.0.0&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers-workspace/monitoring/active-listening/architecture/&#34;&gt;Aura Analytics 2.0.0. architecture&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers-workspace/monitoring/active-listening/operation/&#34;&gt;Aura Analytics 2.0.0 operation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers-workspace/monitoring/active-listening/guidelines-obs/&#34;&gt;Guidelines for OBs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers-workspace/monitoring/active-listening/analytics-dashboard/&#34;&gt;Aura Analytics 2.0.0. dashboard&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/developers-workspace/monitoring/active-listening/annex-dataset-fields-detail/&#34;&gt;Annex: Dataset fields detail&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-authentication-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-authentication-api/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-authentication-api-changelog&#34;&gt;Aura authentication API changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura authentication API component for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-19---use-of-redis-cache&#34;&gt;2025-02-19 - Use of Redis cache&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Users collection data stored in MongoDB are also cached in Redis to increase request&amp;rsquo;s speed.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-authentication-api/#users-database-cache&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-authentication-api&lt;/strong&gt;&lt;/em&gt; users database cache&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-19---anonymous-users-management&#34;&gt;2025-02-19 - Anonymous users management&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;New feature to enable auto-generated anonymous users if needed for KPIs generation.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-authentication-api/#anonymous-users&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-authentication-api&lt;/strong&gt;&lt;/em&gt; anonymous users&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-bridge/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-bridge/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-bridge-changelog&#34;&gt;Aura bridge changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura bridge for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-01-08---aura-bridge-handles-channeldata-v3-in-whatsapp&#34;&gt;2025-01-08 - Aura bridge handles channelData v3 in WhatsApp&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; can now handle the communication with &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt; using channelData v3 for WhatsApp channels&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/aura-bridge-processes/bridge-channel-data-v3-configuration&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; channelData v3 configuration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/environment-variables/#whatsapp-service-plugin&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; environment variables&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/channels/current-channel-model/&#34;&gt;Channels configuration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-01-28---new-mechanism-for-avoiding-call-loops-in-whatsapp-communications&#34;&gt;2025-01-28 - New mechanism for avoiding call loops in WhatsApp communications&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; manages a mechanism to stop call loops in numbers with autoreply activated, as these numbers can be configured to be included in a blacklist.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/aura-bridge-processes/bridge-wa-blacklist-numbers&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; Whatsapp blacklist numbers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-bridge/environment-variables&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; environment variables&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-channels/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-channels/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-channels-changelog&#34;&gt;Aura Channels changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Channels component for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-01-20---whatsapp-experiences-support-channeldata-v3&#34;&gt;2025-01-20 - WhatsApp experiences support channelData v3&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Aura Platform has been adapted for WhatsApp use cases to support the normalized request-response model channelData v3.&lt;/li&gt;
&lt;li&gt;For this purpose, certain modifications have been executed in &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt;, the component that handles the communication with &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt; using channelData v3 for WhatsApp channels.&lt;/li&gt;
&lt;li&gt;Additionally, a new parameter (&lt;code&gt;defaultDirectlineVersion&lt;/code&gt;) has been added in Aura channel model to indicate if messages should be sent using the default Direct Line version for the communication between &lt;em&gt;&lt;strong&gt;aura-bridge&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/channels/current-channel-model/#responseoptionsversionparameters-model&#34;&gt;Aura channel model: ResponseOptionsVersionParameters model&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-configuration-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-configuration-api/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-configuration-api-changelog&#34;&gt;Aura Configuration API changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Configuration API component for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-05---added-preset-management-in-aura-configuration-api&#34;&gt;2025-02-05 - Added preset management in Aura Configuration API&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new set of endpoints has been added to manage the list of presets configured in each instance of Aura: &lt;code&gt;preset-api&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; documentation has been updated to include this new plugin and update the architecture diagrams.&lt;/li&gt;
&lt;li&gt;Implemented the /aura-services/v1/configuration/presets endpoints.&lt;/li&gt;
&lt;li&gt;Added tests to cover the new functionalities.&lt;/li&gt;
&lt;li&gt;Refactor of the server to allow plugins loading.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; client.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-configuration-api&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; server documentation&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-configuration-api/plugins/preset-plugin/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; preset plugin&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-configuration-api/api-definition/preset/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; preset swagger&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/components/aura-configuration-api/api-definition/aura-configuration-api-core/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-configuration-api&lt;/strong&gt;&lt;/em&gt; core swagger&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-deployment/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-deployment/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-deployment-changelog&#34;&gt;Aura deployment changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura deployment for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-06---multitenant-architecture-in-aura-installer&#34;&gt;2025-02-06 - Multitenant architecture in Aura installer&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Aura is now capable of providing services to multiple brands. This feature is based on a &lt;strong&gt;multitenant architecture&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Aurak8s installer has been modified to support the multitenant architecture, as a specific tenant for each brand must be deployed.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/deployment/installer/#multitenant-configuration&#34;&gt;Aura installer: Multitenant configuration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-14---migrate-aura-bot-and-groot-context-database-to-linkin-park&#34;&gt;2025-02-14 - Migrate Aura Bot and Groot context database to Linkin Park&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;New guidelines for the migration of &lt;em&gt;&lt;strong&gt;aura-bot&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;aura-groot&lt;/strong&gt;&lt;/em&gt; database context schemas from releases previous to Linkin Park to Linkin Park onwards. Additionally, the rollback procedure is included.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/deployment/troubleshooting/&#34;&gt;Deployment troubleshooting&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-14---added-information-to-configure-and-deploy-in-next-environment&#34;&gt;2025-02-14 - Added information to configure and deploy in Next environment&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Within aurak8s installer documentation, guidelines for working with Next environment are added: Next DNS endpoints and Next Azure Bot channel&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/deployment/installer/#nextenvironment&#34;&gt;Installer aurak8s: Next environment&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-gateway-api/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-gateway-api/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-gateway-api-changelog&#34;&gt;Aura Gateway API changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura Gateway API component for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-01---added-recommendations-for-using-response_format-in-requests-to-generative-api&#34;&gt;2025-02-01 - Added recommendations for using response_format in requests to Generative API&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Within the guidelines for making a request to &lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; Aura Generative API, recommendations for using &lt;code&gt;response_format&lt;/code&gt;, an object that specifies the format that the model must output, have been added.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/generative-api-request/#recommendations-for-using-response_format&#34;&gt;Guidelines for making a request to Aura Generative API: recommendations for using response_format&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-04---update-aura-gateway-api-swagger-to-allow-free-params&#34;&gt;2025-02-04 - Update Aura Gateway API swagger to allow free params&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Changed field &lt;code&gt;modelParams&lt;/code&gt; in &lt;code&gt;GenerativeApiMessage&lt;/code&gt; and &lt;code&gt;GenerativeApiResponse&lt;/code&gt; to allow any object.&lt;/li&gt;
&lt;li&gt;Deleted &lt;code&gt;ModelParams&lt;/code&gt; schema.&lt;/li&gt;
&lt;li&gt;Updated &lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; client.&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-components/aura-gateway-api/api-definition/aura-generative-api/&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; Generative API&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-04---plugin-refactor&#34;&gt;2025-02-04 - Plugin refactor&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added plugin for &lt;em&gt;&lt;strong&gt;aura-generative-process-service&lt;/strong&gt;&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Affected documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-components/aura-gateway-api/components&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt;: components&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-components/aura-gateway-api/components/plugins&#34;&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt;: plugins&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-04---publish-version-120-of-aura-aiservices&#34;&gt;2025-02-04 - Publish version 1.2.0 of aura-aiservices&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Publish in &lt;strong&gt;Kernel&lt;/strong&gt; these changes as version 1.2.0 of &lt;em&gt;&lt;strong&gt;aura-aiservices&lt;/strong&gt;&lt;/em&gt;, which is the publication of &lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; in &lt;strong&gt;Kernel&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;fixed&#34;&gt;Fixed&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-26---allowed-sending-preset-identifier-or-name-in-aura-gateway-api-request---metallica-991&#34;&gt;2025-02-26 - Allowed sending preset identifier or name in aura-gateway-api request - Metallica 9.9.1&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;aura-gateway-api&lt;/strong&gt;&lt;/em&gt; accepts receiving both preset id or preset name in the request in order not to break compatilibility in requests to &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt;: When the name of the preset is received in the request, the system obtains the preset configuration and validates that the identifier is among those associated with the application.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-nlp/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-nlp/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-nlp-changelog&#34;&gt;Aura NLP changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura NLP component for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;added&#34;&gt;Added&lt;/h2&gt;
&lt;h3 id=&#34;2025-01-09---new-nlp-stage-intent-entity-mapper-stage&#34;&gt;2025-01-09 - New NLP stage: Intent Entity Mapper stage&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new stage has been included in &lt;em&gt;&lt;strong&gt;Aura NLP&lt;/strong&gt;&lt;/em&gt;, the &lt;strong&gt;Intent Entity Mapper stage&lt;/strong&gt;, that allows replacing a recognized intent and its entities with another ones defined in the configuration.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/experiences-builder/development-use-cases/nlp-uc-development/nlp-pipeline-components-catalog/nlp-stages/nlp-adapters/#intent-entity-mapper&#34;&gt;Intent Entity Mapper stage&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-01---new-version-of-aura-nlp-virtual-machine&#34;&gt;2025-02-01 - New version of Aura NLP virtual Machine&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new version of &lt;em&gt;&lt;strong&gt;Aura NLP&lt;/strong&gt;&lt;/em&gt; Virtual Machine has been published, suitable for Metallica release onwards.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://telefonicacorp.sharepoint.com/:f:/r/sites/ColaboraTID/SourcingDeployment/AuraL-CDO/Shared%20Documents/Development%20Technical%20Resources/Aura%20NLP/Metallica%20release%20onwards?csf=1&amp;amp;web=1&amp;amp;e=gUwI2X&#34;&gt;&lt;em&gt;&lt;strong&gt;Aura NLP&lt;/strong&gt;&lt;/em&gt; Virtual Machine&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;deleted&#34;&gt;Deleted&lt;/h2&gt;
&lt;h3 id=&#34;2025-01-13---complete-removal-of-qna&#34;&gt;2025-01-13 - Complete removal of QNA&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Complete removal of QNA from &lt;em&gt;&lt;strong&gt;Aura NLP&lt;/strong&gt;&lt;/em&gt; repositories (configuration, environment variables, outdated code, related components, documentation, etc.) and replacement by the OpenAI Embeddings stage.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-operations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-operations/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-operations-changelog&#34;&gt;Aura operations changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura operations for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2025-01-09---updated-qdrant-version&#34;&gt;2025-01-09 - Updated Qdrant version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Qdrant, the vector similarity search engine and vector database, is upgraded to 1.12.6 version.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-releases/metallica/scheduled-updates/&#34;&gt;Scheduled updates in Aura components&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-09---updated-fluent-bit-version&#34;&gt;2025-02-09 - Updated fluent-bit version&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Updated the version of fluent-bit to 3.2.2&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-releases/metallica/scheduled-updates/&#34;&gt;Scheduled updates in Aura components&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-releases/metallica/changelog/aura-system-components-version/&#34;&gt;Aura system components versions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-platform/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-platform/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-platform-changelog&#34;&gt;Aura platform changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura platform for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-18---aura-multibrand-feature-and-multitenant-architecture&#34;&gt;2025-02-18 - Aura multibrand feature and multitenant architecture&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Both &lt;em&gt;&lt;strong&gt;Aura Virtual Assistant&lt;/strong&gt;&lt;/em&gt; and &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; are designed as &lt;strong&gt;multibrand&lt;/strong&gt; platforms, meaning that users can access them through the different Telefónica brands available in their country. This multibrand feature is based on a &lt;strong&gt;multitenant architecture&lt;/strong&gt;, with a &lt;strong&gt;tenant&lt;/strong&gt; defined as the deployment associated to a specific brand.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-assistant/functional-description/multibrand-overview/&#34;&gt;Introduction to multibrand feature&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Docs: </title>
      <link>/docs/aura-releases/metallica/changelog/aura-documentation/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/docs/aura-releases/metallica/changelog/aura-documentation/</guid>
      <description>
        
        
        &lt;h1 id=&#34;aura-documentation-changelog&#34;&gt;Aura documentation changelog&lt;/h1&gt;


&lt;div class=&#34;pageinfo pageinfo-primary&#34;&gt;
&lt;p&gt;Changelog of Aura documentation for Metallica Aura Platform release&lt;/p&gt;

&lt;/div&gt;

&lt;h2 id=&#34;changed&#34;&gt;Changed&lt;/h2&gt;
&lt;h3 id=&#34;2025-02-21-new-structure-of-atria-configuration-documents&#34;&gt;2025-02-21 New structure of ATRIA configuration documents&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Due to the refactor and apification of &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration, the documents have been updated and restructured:
&lt;ul&gt;
&lt;li&gt;Firstly, contents have been split into separate documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/atria-default-configuration/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; default configuration&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/modify-atria-configuration/&#34;&gt;Modify &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; configuration: Configure &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; presets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-guidelines/configuration/import-documents/&#34;&gt;Import documents to &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;
&lt;br&gt;&lt;br&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;In each document, parameters are organized:
&lt;ul&gt;
&lt;li&gt;
&lt;ol&gt;
&lt;li&gt;By configuration type:&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;Server configuration: internal configuration for &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt;, managed by development or installation teams&lt;/li&gt;
&lt;li&gt;Use cases configuration: parameter &amp;ldquo;preset&amp;rdquo;, related to the development of experiences in &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt;, managed by use cases constructors&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;ol start=&#34;2&#34;&gt;
&lt;li&gt;By component:&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;atria-model-gateway&lt;/strong&gt;&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;&lt;strong&gt;atria-rag-server&lt;/strong&gt;&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-21---remove-deprecated-releases&#34;&gt;2025-02-21 - Remove deprecated releases&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Aura Platform outdated releases have been removed from Aura Technical Documentation website, both from the &lt;em&gt;aura-releases/&lt;/em&gt; section and from the landing page.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://technicaldocs.auracognitive.com/&#34;&gt;Aura Technical Documentation website landing page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-releases/&#34;&gt;Aura Virtual Assistant &amp;amp; ATRIA releases&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-21---aura-multibrand-and-multitenant-documentation&#34;&gt;2025-02-21 - Aura multibrand and multitenant documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Documentation related to the new &lt;strong&gt;multibrand&lt;/strong&gt; feature and &lt;strong&gt;multitenant architecture&lt;/strong&gt; has been published, including:
&lt;ul&gt;
&lt;li&gt;Functionality overview:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-assistant/functional-description/multibrand-overview/&#34;&gt;Introduction to multibrand feature&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/aura-assistant/functional-description/multibrand-overview/#overview-of-the-multitenant-architecture&#34;&gt;Overview of the multitenant architecture&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/atria-functional-description/multibrand-overview/&#34;&gt;Introduction to &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; multibrand feature&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Deployment guidelines:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/deployment/installer/#multitenant-configuration&#34;&gt;Aura installer: Multitenant configuration&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-21---new-section-for-atria-operational-flows&#34;&gt;2025-02-21 - New section for ATRIA operational flows&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;A new section has been added to Aura Technical Documentation website that includes &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; technical operational flows, designed as sequence diagrams to provide a clear, step-by-step representation of &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; capabilities and processes, interactions between components or systems, and the overall &lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; workflow.&lt;/li&gt;
&lt;li&gt;Related documents:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;../../../../docs/atria/technical-operation/&#34;&gt;&lt;em&gt;&lt;strong&gt;ATRIA&lt;/strong&gt;&lt;/em&gt; technical operation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;2025-02-21---documents-fixes-and-corrections&#34;&gt;2025-02-21 - Documents fixes and corrections&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Throughout the website, different links, styles, weights and typos have been modified and/or corrected, for a continuous improvement of Aura Platform documentation.&lt;/li&gt;
&lt;li&gt;Tags and categories are reviewed in every release in order to maintain the adequate taxonomy for the classification of documents.&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
  </channel>
</rss>
