This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Metallica release

Metallica release

This section includes key information regarding new features included in Aura Platform for Metallica and main changes in comparison with previous releases

What’s new in Metallica (9.9.0)?

Discover here the new features and modifications at a glance. You can find the technical details in the release changelog and the Release Notes.

For environments that can be suspended and set up again, it is required to carry out a previous task: Workaround for Metallica release

Novelties Description
Aura multibrand ✔️ Both Aura Virtual Assistant and ATRIA are now designed as multibrand, capable of providing services to all the brands through which an OB commercializes its services. This feature is based on a multitenant architecture.
Refactor and apification of ATRIA configuration ✔️ The configuration of ATRIA components has been redesigned through a new, more generalizable architecture. Changes include the refactor of configuration parameters and the apification of the configuration parameters managed by ATRIA use cases constructors
Aura Analytics 2.0.0 is launched ✔️ New version of the monitoring tool designed and managed by Aura Global Team that allows active listening in Aura, with the ultimate goal of improving its quality
✔️ In this version, our tool has been refactored to enhance efficiency and support future extensions
WhatsApp experiences support channelData v3 ✔️ Aura Platform has been adapted for WhatsApp use cases to support the normalized request-response model channelData v3
Avoid call loops in WhatsApp ✔️ New mechanism to stop call loops in numbers with autoreply activated
New at Aura NLP ✔️ New stage Intent Entity Mapper stage can be used to replace a recognized intent and its entities with another ones defined in configuration
✔️ Complete removal of QNA and replacement by OpenAI Embeddings stage
✔️ A new version of Aura NLP Virtual Machine has been published, suitable for Metallica release onwards
Enhancements in Aura deployment & operation ✔️ Qdrant vector similarity search engine and vector database is upgraded to 1.12.6 version
✔️ Updated fluent-bit version to 3.2.2
✔️ Guidelines for the migration of aura-bot and aura-groot context database to Linkin Park
✔️ Added information to configure and deploy in Next environment
Modifications in aura-configuration-api derived from ATRIA config apification ✔️ New plugin and settings, so the entire ATRIA configuration can be managed using aura-configuration-api
Modifications in aura-gateway-api derived from ATRIA config apification ✔️ Make aura-gateway-api more flexible to allow sending any type of parameters to models
✔️ Plugin refactor
✔️ Published new version of aura-aiservices in Kernel
Updated ATRIA documentation ✔️ Reorganization of ATRIA configuration documents to adapt them to the new refactor and apification
✔️ Improved ATRIA documentation, with the introduction of newer operational flows for all the AI-driven capabilities
✔️ Added recommendations for including in the request to the Generative API the required output format for the model
Improved Aura documentation ✔️ Documents are continuously updated, reviewed and corrected in order to achieve, release after release, a better quality in Aura Platform documentation
Bugfixing Metallica 9.9.1: Maintain compatibility in requests to ATRIA ✔️ Allow send preset identifier or name in aura-gateway-api request

1 - Metallica release changelog

Metallica release changelog

Discover the record of all notable changes made in Aura Platform for this release, organized by component.

1.1 - Aura system components version

Aura system components versions

Updated versions of Aura system components for the current Aura Platform release

Components versions

All components in the table below run over AKS cluster version 1.30

Name Namespace Image deployed
alertmanager aura-system devopstf.azurecr.io/tools/alertmanager:v0.26.0
elastic-operator aura-system docker.elastic.co/eck/eck-operator:2.7.0
elasticsearch-es-aura aura-system devopstf.azurecr.io/tools/elasticsearch:8.16.1
elasticsearch-exporter aura-system devopstf.azurecr.io/tools/elasticsearch_exporter:v1.5.0
fluent-bit-aggregator aura-system devopstf.azurecr.io/tools/fluent-bit:3.2.2
grafana aura-system devopstf.azurecr.io/tools/grafana:10.3.3
kibana-kb aura-system docker.elastic.co/kibana/kibana:8.16.1
prometheus aura-system devopstf.azurecr.io/tools/prom/prometheus:v2.53.1
mongodb-atlas-operator aura-system devopstf.azurecr.io/tools/mongodb-atlas-kubernetes-operator:2.1.0
redis-exporter aura-system devopstf.azurecr.io/tools/redis-exporter:1.6.1
redis aura-system devopstf.azurecr.io/tools/redis:6.0.19
thanos-store-gateway aura-system devopstf.azurecr.io/tools/thanos:v0.32.5
atlas-logger aura-system devopstf.azurecr.io/tools/atlas-logger:2.0.0
azure-logger aura-system devopstf.azurecr.io/tools/azure-logger:1.4.0
pushgateway aura-system devopstf.azurecr.io/tools/pushgateway:v1.4.1
thanos-querier aura-system devopstf.azurecr.io/tools/thanos:v0.32.5

Additional information

Information regarding Aura system components end-of-life (EOL) and next updates is included in the document Scheduled updates in Aura components. Find it in the Aura releases section of your corresponding release.

1.2 - Atria Model Gateway changelog

Atria Model Gateway changelog

Changelog of Atria Model Gateway for Metallica Aura Platform release

Added

2025-02-17 - New section for ATRIA technical operation

  • A new section has been added to Aura Technical Documentation website that includes ATRIA technical operational flows, designed as sequence diagrams to provide a clear, step-by-step representation of ATRIA capabilities and processes, interactions between components or systems, and the overall ATRIA workflow.
  • The operational flowcharts for ATRIA Generative capability have been updated in this section.
  • Related documents:

Changed

2025-02-14 - Apification of atria-model-gateway configuration

  • The configuration of ATRIA components, including atria-model-gateway, has been redesigned through a new, more generalizable architecture. This approach simplifies and decentralizes chains management. Additionally, the architecture is prepared for upcoming ATRIA scenarios with more available LLM/RAG chains and different objectives.
  • Consequently, two main tasks have been executed:
    • Refactor of configuration parameters, both for the server configuration and parameters related to use cases development
    • Apification of configuration parameters for ATRIA use cases constructors, that can be easily modified through the swagger
  • Related documents:

2025-02-14 - ATRIA presets configuration through API

1.3 - Atria RAG Server changelog

Atria RAG Server changelog

Changelog of Atria RAG Server for Metallica Aura Platform release

Added

2025-02-17 - New section for ATRIA technical operation

  • A new section has been added to Aura Technical Documentation website that includes ATRIA technical operational flows, designed as sequence diagrams to provide a clear, step-by-step representation of ATRIA capabilities and processes, interactions between components or systems, and the overall ATRIA workflow.
  • The operational flowcharts for ATRIA RAG capability have been updated in this section.
  • Related documents:

2025-02-17 - Added Aura Copilot RAG operational workflow

  • Added the operational flow corresponding to the call that aura-copilot makes to the ATRIA RAG capability into a new section “Technical operation”
  • Related documents:

Changed

2025-02-14 - Apification of atria-rag-server configuration

  • The configuration of ATRIA components, including atria-rag-server, has been redesigned through a new, more generalizable architecture. This approach simplifies and decentralizes chains management. Additionally, the architecture is prepared for upcoming ATRIA scenarios with more available LLM/RAG chains and different objectives.
  • Consequently, two main tasks have been executed:
    • Refactor of configuration parameters, both for the server configuration and parameters related to use cases development
    • Apification of configuration parameters for ATRIA use cases constructors, that can be easily modified through the swagger
  • Related documents:

2025-02-14 - ATRIA presets configuration through API

1.4 - Aura Analytics 2.0.0

Aura Analytics 2.0.0 changelog

Changelog of Aura Analytics 2.0.0 for Metallica Aura Platform release

Added

2025-02-20 - Aura Analytics 2.0.0

1.5 - Aura authentication API changelog

Aura authentication API changelog

Changelog of Aura authentication API component for Metallica Aura Platform release

Added

2025-02-19 - Use of Redis cache

2025-02-19 - Anonymous users management

1.6 - Aura bridge changelog

Aura bridge changelog

Changelog of Aura bridge for Metallica Aura Platform release

Added

2025-01-08 - Aura bridge handles channelData v3 in WhatsApp

2025-01-28 - New mechanism for avoiding call loops in WhatsApp communications

aura-bridge manages a mechanism to stop call loops in numbers with autoreply activated, as these numbers can be configured to be included in a blacklist.

1.7 - Aura Channels changelog

Aura Channels changelog

Changelog of Aura Channels component for Metallica Aura Platform release

Added

2025-01-20 - WhatsApp experiences support channelData v3

  • Aura Platform has been adapted for WhatsApp use cases to support the normalized request-response model channelData v3.
  • For this purpose, certain modifications have been executed in aura-bridge, the component that handles the communication with aura-bot using channelData v3 for WhatsApp channels.
  • Additionally, a new parameter (defaultDirectlineVersion) has been added in Aura channel model to indicate if messages should be sent using the default Direct Line version for the communication between aura-bridge and aura-bot.
  • Related documents:

1.8 - Aura Configuration API changelog

Aura Configuration API changelog

Changelog of Aura Configuration API component for Metallica Aura Platform release

Added

2025-02-05 - Added preset management in Aura Configuration API

1.9 - Aura deployment changelog

Aura deployment changelog

Changelog of Aura deployment for Metallica Aura Platform release

Added

2025-02-06 - Multitenant architecture in Aura installer

  • Aura is now capable of providing services to multiple brands. This feature is based on a multitenant architecture.
  • Aurak8s installer has been modified to support the multitenant architecture, as a specific tenant for each brand must be deployed.
  • Affected documents:

2025-02-14 - Migrate Aura Bot and Groot context database to Linkin Park

  • New guidelines for the migration of aura-bot and aura-groot database context schemas from releases previous to Linkin Park to Linkin Park onwards. Additionally, the rollback procedure is included.
  • Related documents:

2025-02-14 - Added information to configure and deploy in Next environment

  • Within aurak8s installer documentation, guidelines for working with Next environment are added: Next DNS endpoints and Next Azure Bot channel
  • Related documents:

1.10 - Aura Gateway API changelog

Aura Gateway API changelog

Changelog of Aura Gateway API component for Metallica Aura Platform release

Added

2025-02-01 - Added recommendations for using response_format in requests to Generative API

Changed

2025-02-04 - Update Aura Gateway API swagger to allow free params

  • Changed field modelParams in GenerativeApiMessage and GenerativeApiResponse to allow any object.
  • Deleted ModelParams schema.
  • Updated aura-gateway-api client.
  • Affected documents:

2025-02-04 - Plugin refactor

2025-02-04 - Publish version 1.2.0 of aura-aiservices

  • Publish in Kernel these changes as version 1.2.0 of aura-aiservices, which is the publication of aura-gateway-api in Kernel

Fixed

2025-02-26 - Allowed sending preset identifier or name in aura-gateway-api request - Metallica 9.9.1

  • aura-gateway-api accepts receiving both preset id or preset name in the request in order not to break compatilibility in requests to ATRIA: 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.

1.11 - Aura NLP changelog

Aura NLP changelog

Changelog of Aura NLP component for Metallica Aura Platform release

Added

2025-01-09 - New NLP stage: Intent Entity Mapper stage

  • A new stage has been included in Aura NLP, the Intent Entity Mapper stage, that allows replacing a recognized intent and its entities with another ones defined in the configuration.
  • Related documents:

2025-02-01 - New version of Aura NLP virtual Machine

  • A new version of Aura NLP Virtual Machine has been published, suitable for Metallica release onwards.
  • Related documents:

Deleted

2025-01-13 - Complete removal of QNA

  • Complete removal of QNA from Aura NLP repositories (configuration, environment variables, outdated code, related components, documentation, etc.) and replacement by the OpenAI Embeddings stage.

1.12 - Aura operations changelog

Aura operations changelog

Changelog of Aura operations for Metallica Aura Platform release

Changed

2025-01-09 - Updated Qdrant version

2025-02-09 - Updated fluent-bit version

1.13 - Aura platform changelog

Aura platform changelog

Changelog of Aura platform for Metallica Aura Platform release

Changed

2025-02-18 - Aura multibrand feature and multitenant architecture

  • Both Aura Virtual Assistant and ATRIA are designed as multibrand platforms, meaning that users can access them through the different Telefónica brands available in their country. This multibrand feature is based on a multitenant architecture, with a tenant defined as the deployment associated to a specific brand.
  • Related documents:

1.14 - Aura Documentation changelog

Aura documentation changelog

Changelog of Aura documentation for Metallica Aura Platform release

Changed

2025-02-21 New structure of ATRIA configuration documents

  • Due to the refactor and apification of ATRIA configuration, the documents have been updated and restructured:
  • In each document, parameters are organized:
      1. By configuration type:
      • Server configuration: internal configuration for ATRIA, managed by development or installation teams
      • Use cases configuration: parameter “preset”, related to the development of experiences in ATRIA, managed by use cases constructors
      1. By component:
      • atria-model-gateway
      • atria-rag-server

2025-02-21 - Remove deprecated releases

2025-02-21 - Aura multibrand and multitenant documentation

2025-02-21 - New section for ATRIA operational flows

  • A new section has been added to Aura Technical Documentation website that includes ATRIA technical operational flows, designed as sequence diagrams to provide a clear, step-by-step representation of ATRIA capabilities and processes, interactions between components or systems, and the overall ATRIA workflow.
  • Related documents:

2025-02-21 - Documents fixes and corrections

  • Throughout the website, different links, styles, weights and typos have been modified and/or corrected, for a continuous improvement of Aura Platform documentation.
  • Tags and categories are reviewed in every release in order to maintain the adequate taxonomy for the classification of documents.

2 - Metallica Release Notes

Metallica Release Notes

Access the document Aura Platform Release: Metallica 9.9.0- Release Notes

Access the document Aura Platform Release: Metallica 9.9.1 - Release Notes

3 - Scheduled updates in Aura components

Scheduled updates in Aura components

List of basic dependencies used by Aura components with their EOL information and the maximum frequency of update proposed by Aura Global team to avoid security issues. It also contains the next scheduled update, if it is already known.

Future updates

Aura Component Dependency Current Version EOL Max frequency Next update EOL Info
Aura System aks/kubernetes 1.30.5 07/25 Twice a year 2025Q3 https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions?tabs=azure-cli#kubernetes-versions
Aura System elasticsearch 8.16.1 05/27 Once a year 2025Q4 https://www.elastic.co/es/support/eol
Aura System grafana 10.3.3 N/A Once a year 2025Q2 https://community.grafana.com/t/support-policy-for-previous-releases/53350
Aura System kibana 8.16.1 05/27 Once a year 2025Q4 https://www.elastic.co/es/support/eol
Aura System prometheus 2.53.1 End of Support: 07/25 Once a year 2025Q4 https://prometheus.io/docs/introduction/release-cycle/
Aura System fluent-bit 3.2.2 3 months after version 3.3 is released Once a year 2026Q1 https://endoflife.date/fluent-bit/
Aura Bot mongodb 7.0 08/26 Once a year 2025Q4 https://www.mongodb.com/support-policy/lifecycles
Aura System, Aura Bot 1 node docker image node:20.17.0-alpine3.20 04/26 Once a year 2025Q2 https://endoflife.date/alpine
Aura System, Aura Context redis 6.X (azure) 08/24 Once a year 2025Q2 https://endoflife.date/redis
Aura Bot nodejs 20.17.0 04/26 Once a year1 2025Q2 https://endoflife.date/nodejs
Aura Bot typescript 5.0.0 N/A Once a year 2025Q4
Aura Bot botbuilder 4.22.1 N/A Once a year 2025Q2
Aura Bot joi 17.6.0 N/A Once a year 2025Q2
Aura Bot superagent 9.0.2 N/A Once a year 2025Q2
Databricks Jobs (uploading) python 3.9 31/10/25 Once a year 2025Q3 https://endoflife.date/python
Databricks Jobs (uploading) databricks 12.2 LTS spark: 3.3.2 01/03/26 Once a year 2025Q3
QA Tool python 3.9 / 3.10 31/10/25 (3.9)
31/10/26 (3.10)		 Once a year 2025Q3 https://endoflife.date/python
Aura Cognitive python 3.9 / 3.11 05/10/25 (3.9)
24/10/27 (3.11)		 Every 2 years 2025Q2 https://endoflife.date/python
Aura Cognitive python packages dependencies N/A N/A Every 2 years 2025Q2 (python - 1 year)
Aura Cognitive ubuntu 22.04 LTS 01/04/27 Every 5 years 2026Q4 https://ubuntu.com/about/release-cycle
Aura Cognitive local tool containers N/A N/A Every 2 years 2025Q2
Aura Cognitive Abacus react 17.0.2 🔴 29/03/22 Every 3 years 2025Q2 https://endoflife.date/react
Aura Cognitive Abacus typescript 4.1 N/A Every 3 years 2025Q2
Aura Cognitive Qdrant 1.12.6 N/A 2 Once a year 2025Q4 https://github.com/qdrant/qdrant/blob/master/docs/roadmap/README.md

  1. Nodejs will be updated to a major version on a yearly basis, but within the same major version, it will be updated every time a security update is released. ↩︎ ↩︎

  2. Qdrant will keep backward compatibility for, at least, one minor version back. ↩︎