---

This documentation and the Cisco Observability Platform functionalities it describes are subject to change. Data saved on the platform may disappear and APIs may change without notice.

---

24.x Release Notes

May 7, 2024

Version ID: 24.5.3

Enhancements

• Codex:
  • Leverage the capabilities of zodiac:function in your Codex workflows. See Solution Services Integration.
• Knowledge Store:
  • A new concept of a fully qualified ID (FQID), which is a unique ID used to identify a knowledge object at a specific layer. The syntax for the FQID is <fqtn>/<objectId>;layerId=<layerId>;layerType=<layerType>. See Define a Knowledge Object.
  • A new functionality for using references in knowledge type definitions. References enable a property in one knowledge type to point to an object in the same knowledge type or another knowledge type. They can be used to prevent duplication of information. See Use References in Knowledge Types and Objects.
• Solutions:
  • Underscores (_) are now supported in solution names for solutions that do not contain solution services functions. See Solution Naming Conventions.
  • A new fsoc solution show command lists all files in a solution bundle.
• fsoc:
  • Fixed issues that occurred in the fsoc solution extend command when it was used to add objects that (a) had embedded references in them and (b) were generated in YAML format.
  • Fixed JSON encoding issues in the fsoc solution fork and fsoc solution bump commands.

Known Issues and Limitations

• The fsoc knowledge create, fsoc knowledge get, fsoc knowledge update, and fsoc knowledge delete commands do not yet support ACCOUNT or GLOBALUSER for the --layer-type parameter.
• Solution isolation is not currently supported.
• When you call a function that a solution declares, it can't access external services or identity context and propagate it to other services.
• Tenants' source environments cannot send non-OTLP or non-MELT data to the platform.
• If custom OpenTelemetry collectors send OTLP packets directly to the platform's Common Ingestion Service API endpoint, they must use HTTP1.1 or gRPC.
• Currently, the platform doesn't support defining a logging solution. Instead, you can configure the Log Collector that is bundled with the Cisco Cloud Observability solution.
• Adding explicit data binding and data transformation to a template's building block is not yet supported.

Restrictions

• Only select design partners can build on the platform. End-users can't build on the platform at this time.
• Design partners can only build modules, not solutions, at this time.

April 4, 2024

Version ID: 24.3.0

Enhancements

• Access Management:
  • In Make Calls to the Platform and Other Solutions, a new section for supported transport protocols was added and the example calls were corrected to use http instead of https. The supported transport protocols are http and gRPC.
• Actions:
  • Updated the API reference specification and sample codes to add metadata.applications in the filter expression.
• Data Ingestion:
  • The platform now handles inexact intervals between metrics. It aggregates metrics collected at sub-minute granularities into one-minute granularities by default.
• Data Queries:
  • Updated the API reference specification to add the schemas BatchedQueryRequestBody and QueryRequestQuery for requests containing multiple queries.
• Health Rules:
  • Updated the API reference specification to add the details of the ViolationStatus metadata and updated the sample codes to add metadata.applications in the filter expression.
• Solutions:
  • Support for solution manifest version 1.1.0, which includes a new solutionType attribute that can be used to classify a solution as a module or component. See Solution Manifest Attributes and Components.
  • Support for YAML files in solutions. The solution manifest file, knowledge object files, and knowledge type files can now be in YAML format. Solutions can also use a combination of JSON and YAML files. See Solutions Introduction.
  • The --yaml flag is now supported in the fsoc solution init and fsoc solution extend commands. See:
    • Create a Solution
    • Add a Knowledge Type to a Solution
    • Add a Knowledge Object to a Solution
  • A new fsoc solution fix command to:
    • Convert the manifest file format to JSON or YAML.
    • Update the manifest file version to the latest version and add the solutionType property.
  • A new fsoc solution delete and cURL command to delete solutions that do not have the stable tag. See Delete a Solution.
  • A new cURL command and an updated fsoc command to check the deletion status of a solution. See Check the Solution Deletion Status.

Known Issues and Limitations

• The fsoc knowledge create, fsoc knowledge get, fsoc knowledge update, and fsoc knowledge delete commands do not yet support ACCOUNT or GLOBALUSER for the --layer-type parameter.
• Solution isolation is not currently supported.
• When you call a function that a solution declares, it can't access external services or identity context and propagate it to other services.
• Tenants' source environments cannot send non-OTLP or non-MELT data to the platform.
• If custom OpenTelemetry collectors send OTLP packets directly to the platform's Common Ingestion Service API endpoint, they must use HTTP1.1 or gRPC.
• Currently, the platform doesn't support defining a logging solution. Instead, you can configure the Log Collector that is bundled with the Cisco Cloud Observability solution.
• Adding explicit data binding and data transformation to a template's building block is not yet supported.

Restrictions

• Only select design partners can build on the platform. End-users can't build on the platform at this time.
• Design partners can only build modules, not solutions, at this time.

February 29, 2024

Version ID: 24.2.29

Enhancements

• Codex:
  • Added the Codex workflow schema
  • Added supported CloudEvents
  • Added input data structure
  • Added Platform Functions
• Data Queries
  • Added the sum(attributes(<attribute_name>))  function to add the values of the specified attributes of an event.
  • Added the count observation to sort the entities.
• Solutions:
  • A new fsoc solution zap command for deleting all of the knowledge types and objects of a solution. See Delete the Knowledge Types and Objects of a Solution.
• Solution Services:
  • zodiac:egressHosts supports a wildcard character in the left-most position of dnsName.

Known Issues and Limitations

• The fsoc knowledge create, fsoc knowledge get, fsoc knowledge update, and fsoc knowledge delete commands do not yet support ACCOUNT or GLOBALUSER for the --layer-type parameter.
• Solution isolation is not currently supported.
• When you call a function that a solution declares, it can't access external services or identity context and propagate it to other services.
• Tenants' source environments cannot send non-OTLP or non-MELT data to the platform.
• If custom OpenTelemetry collectors send OTLP packets directly to the platform's Common Ingestion Service API endpoint, they must use HTTP1.1 or gRPC.
• Currently, the platform doesn't support defining a logging solution. Instead, you can configure the Log Collector that is bundled with the Cisco Cloud Observability solution.
• Adding explicit data binding and data transformation to a template's building block is not yet supported.

Restrictions

• Only select design partners can build on the platform. End-users can't build on the platform at this time.
• Design partners can only build modules, not solutions, at this time.

January 31, 2024

Version ID: 24.1.31

New Location of Documentation

This documentation is now located at https://developer.cisco.com/docs/cisco-observability-platform/. The old URL, https://developer.cisco.com/docs/fso/, redirects to the new URL.

Enhancements

• DashUI updates:
  • Support configuration for the delete operation.
  • New parameters for columns: cell, storageAdapter, permissions.
  • A new withMetadata parameter used for lists. See dashui:settingsConfig.
• Data Ingestion updates:
  • The platform now supports dynamic metrics -- metrics that a tenant receives that aren't predefined by fmm:metric configurations in any solution that the tenant is subscribed to -- and maps each dynamic metric to an existing entity, if the metric's attributes match an entity's attributes. This feature is beneficial because solutions don't need to predefine all metrics that they might want to associate with their data model.
  • logs:logParsingRule now provides predefined GROK parsing patterns for Apache, Amazon ALB, Amazon ELB, AWS S3 Access, HA Proxy, Kafka, MySQL, NGINX, PostresSql, Redis, SQL Server, and Zookeeper. Predefined patterns reduce complexity with extracting the fields you need from your log messages and speed up troubleshooting.
  • Platform Home > Tools > Platform Monitoring is a dashboard that provides visibility into the runtime status of the platform. Tenants can use this dashboard to drill down into the platform's telemetry related to the three segments of MELT data pipeline:
    • Data ingestion
    • Data mapping and processing
    • Data storage Previously, when tenants sent data to the CIS endpoint they wouldn't know what happened to their data after it reached the CIS endpoint. With this dashboard, tenants have insight into any errors that happen beyond the CIS endpoint.
• Knowledge Store updates:
  • A new functionality for storing the property values of a knowledge object in blob storage. See Knowledge Object File with Blob Properties.
• fsoc updates:
  • fsoc melt push is now an alias for fsoc melt send.

Known Issues and Limitations

• The fsoc knowledge create, fsoc knowledge get, fsoc knowledge update, and fsoc knowledge delete commands do not yet support ACCOUNT or GLOBALUSER for the --layer-type parameter.
• Solution isolation is not currently supported.
• When you call a function that a solution declares, it can't access external services or identity context and propagate it to other services.
• Tenants' source environments cannot send non-OTLP or non-MELT data to the platform.
• If custom OpenTelemetry collectors send OTLP packets directly to the platform's Common Ingestion Service API endpoint, they must use HTTP1.1 or gRPC.
• Currently, the platform doesn't support defining a logging solution. Instead, you can configure the Log Collector that is bundled with the Cloud Native Application Observability solution.
• Adding explicit data binding and data transformation to a template's building block is not yet supported.

Restrictions

• Only select design partners can build on the platform. End-users can't build on the platform at this time.
• Design partners can only build modules, not solutions, at this time.