23.x Release Notes

December 14, 2023

Version ID: 23.12.14

Name Changes

Cisco Full-Stack Observability (FSO) Platform is now the Cisco Observability Platform, and Cloud Native Application Observability is now Cisco Cloud Observability, powered by the Cisco Observability Platform. These name changes better align our products with the Cisco portfolio and with our business strategy.

Enhancements

• DashUI updates:
  • This release includes the scopeGroupBy building block and the currency and wizard elements for Forms.
• Data Ingestion updates:
  • We've updated how we handle time aggregations of monotonically increasing metrics.
• Knowledge Store updates:
  • Support for tagging knowledge objects. Tags can be used to categorize, retrieve, and filter knowledge objects. See Tag a Knowledge Object.
• Solution Services updates:
  • We've implemented security measures for zodiac:functions to access platform services. All solutions and their functions must have the right permissions to access platform services. In addition, all functions must change the URLs they use to access services to the format http://${APPD_INTERNAL_EGRESS_HOST}/{route-to-the-api}, where APPD_INTERNAL_EGRESS_HOST is an environment variable that the platform provides to all functions at runtime.
• Health Rules updates:
  • Support for alerting on log events.
• Data Queries updates:
  • Support for the OPTION clause for UQL query processing.
  • Support for array attributes and tags in the Event() function.
  • Support for the operators (>, >=, <, <=) for filtering numerical event attributes.
  • Support for the wildcards in the IN operator.
• Access Management updates:
  • Solutions will need to declare permissions to access resources from the platform or other solutions. While the platform currently won't enforce this requirement, it's advisable for future compliance. These resources can either be objects or URIs.
  • Developers can configure permissions for requests to platform or other solution resources to run in the background or require user consent with the property can_access_in_background.
  • The platform substitutes the domain in the request URI with the environment variable APPD_INTERNAL_EGRESS_HOST. For example, the request URI to call the Health Rules API would be http://${APPD_INTERNAL_EGRESS_HOST}/alerting/v1beta/healthRules.
  • Solutions must adhere to the following requirements to make calls to the Cisco Observability Platform or other solutions:
    • Solutions must specify the host making calls to the Cisco Observability Platform.
    • If a user action creates an incoming request to the solution, the solution must copy the request's Authorization header to the call to the platform or other solutions.
• Security update: All system components, and all communication into, out of, and within the platform, now use TLS protocol version 1.3 by default.

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.

October 27, 2023

Version ID: 23.10.27

Enhancements

• DashUI updates:
  • A new DashUI type dashui:entityPagePropSet.
  • A new Form element named form.ContainerCard.
  • Validation can now be triggered by the Group and Repeater elements.
  • Support for macros on Entity Centric Pages.
  • Support for the Configurable Filter.
  • A new JSONata functionality named $format.
  • The @fetch action now has Knowledge Store functionality.
  • The ability to use Themes and Tokens for Templates.
• Data Ingestion updates:
  • There's an updated configuration for masking sensitive data in log messages, logs:dataMaskingRuleV1. The platform still supports older configurations based on logs:dataMaskingRule, but we strongly suggest you migrate them.
  • You can now create server-side parsing rules that apply to all matching log messages.
• Solution Services updates:
  • Solutions can introduce randomness into the cron job schedule by using the randomizeMinute function in their zodiac:subscriptionCronConfig definitions.
• A new system solution, solutionsecret, allows you to encrypt secrets and pass the encrypted values to your zodiac:functions.
• Health Rules updates:
  • Support for the health rule granularity and delay configuration by using the healthrule:healthRuleScopeOverrides schema.
  • Support for percentile function for metric values.
  • Support for events in a health rule condition.
• Data Queries updates:
  • Support for the not like (!~) operator in the topology filter.
  • Support for Span links in the spans() function.

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.

September 27, 2023

Version ID: 23.9.27

Enhancements

• DashUI updates:
  • Support for Custom Slots for Entity Centric Pages.
  • A new element, form.Template, for Forms.
  • Forms allow navigation to another Form page or v1plus page.
• The Knowledge Store has a new ID generation mechanism for knowledge types. The idGeneration property has been deprecated for all new knowledge types. All existing knowledge types must be updated to replace idGeneration with the new identifyingProperties property as soon as possible. For more information on identifyingProperties, see Define a Knowledge Type.
• Solution Services updates:
  • Solution Services supports function-to-function calls.
  • zodiac:function calls now return Content-Security-Policy HTTP response headers. You can customize the Content-Security-Policy headers returned by your functions by setting the cspHeader attribute in your zodiac:function definitions.
• UQL Queries support the coalesceAttributes() function in the FETCH block.

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.

August 25, 2023

Version ID: 23.8.25

Name Changes

AppDynamics Cloud is now Cloud Native Application Observability.

Enhancements

• Access Management functionality is now available.
• The health rule template has a new field, expressionVersion. This field indicates the version of the health rule expression language. The current version of expression language is v2. See Health Rules Schema.
• Health rule expression language v1 is deprecated.
• The Query Service API is updated to version 1.3.0. The following field properties were added:
  • resultType
  • functionType
  • orderable
  • fieldCoordinates
  • querySnippet
  • ordering
• fsoc updates:
  • fsoc switched to golang 1.20, so if you're building it locally, you must upgrade.
  • fsoc config set validates fields and clears dependent fields (unless you include the --patch flag).
  • A new command, fsoc config delete, deletes a context from the fsoc configuration file.
  • A new command, fsoc optimize servo-logs, retrieves the logs of the Servo agent currently running for the given optimization.
  • fsoc version recognizes locally built versions.
  • fsoc knowledge get supports paginated results.
  • fsoc solution status provides faster, parallel retrieval of status.
  • The fsoc melt commands support typed attributes.
  • The fsoc optimize commands support events and recommendations, and solution isolation (in fsoc optimize status only).
  • A new command, fsoc optimize delete, offboards the given optimizer from optimizing its target workload, removes the configuration, and frees up resources.
  • There is improved support for solution isolation through the envtype parameter on some fsoc solution 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 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.

Documentation Updates

• The following changes were made on Solutions:
  • The fsoc commands and example requests/responses were updated.
  • Additional details on solution tagging and deployment were added.
  • New instructions on how to check the upload and installation status of a specific solution version were added.
  • Two new pages were added: Deploy a Solution to the FSO Platform Exchange and Troubleshoot Solutions.
• The Knowledge Store API documentation has a new Errors and Troubleshooting page.
• The following diagrams in the overview documentation were updated to reflect the latest changes:
  • The ecosystem diagram on Solutions was updated with the name change from AppDynamics Cloud to Cloud Native Application Observability.
  • The platform architecture graphic on Platform Architecture was updated to reflect the name change of AppDynamics Cloud to Cloud Native Application Observability and the new UI layer name FSO Microsites and Dashboards.
• A walkthrough of the Space Fleet example solution explains each step of how the solution was created.

August 8, 2023

Version ID: 23.8.08 Hotfix

Enhancements

• Actions contains information about the HTTP action type definition and action templates for OpsGenie, PagerDuty, ServiceNow, Slack, and Webex.

July 26, 2023

Version ID: 23.7.0-268

Enhancements

• The syntax of the fsoc config set command has changed:

  • The flag --auth has been deprecated. Please use non-flag argument in the form "auth=<AUTH>".
  • The flag --url has been deprecated. Please use non-flag argument in the form "url=<URL>".

• Solution Services now allows you to configure ports and protocols for your egress hosts: see the portNumber and portProtocol attributes in zodiac:egressHosts.

Known Issues

Known issues and limitations are noted within context in applicable topics.

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 at this time. The functionality to build solutions is not yet generally available.

June 28, 2023

Version ID: 23.6.28

Introducing the Cisco Full-Stack Observability (FSO) Platform

This is the initial release of the FSO Platform, an extensible platform offering a collection of services that allow developers to build modules that provide observability into various domains, and customers to subscribe to modules that extend the existing solution powered by the FSO Platform, Cisco Cloud Observability.

• The authoring tool allows developers to browse, duplicate, create, or update UI templates. This tool offers two ways to edit UI templates: with an organized outline tool to insert elements from the building block library or with a raw code editor to directly edit the JSON code, with a preview function to visualize the changes. Basic contextual help, such as entity information, readme files, and documentation, are also available within the tool.
• The Knowledge Store API supports solution and Tenant-wide changes to knowledge objects, patching of knowledge objects to support mutable defaults with user-owned content, and building automation to manage the lifecycle of knowledge objects.
• The FSO Platform command line interface provides solution lifecycle support and an interface to the unified query engine.

Known Issues

Known issues and limitations are noted within context in applicable topics.

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 at this time. The functionality to build solutions is not yet generally available.

Documentation Updates

• Access Management includes a getting started section, RBAC modeling, and roles. This guide is still in preview, however, you can learn more about how to use it and the roles that can be configured.
• Knowledge Store has updated API paths and naming conventions for knowledge types.
• Solutions has updated commands, command output, and API paths; naming conventions for solutions; and a new page, Bump the Solution Version.
• Solution Services has information on how to pull images from a private Docker registry.
• Data Ingestion has information on how to mask sensitive data.
• Data Modeling includes reference content on metrics and more FMM configurations (also called MELT workflows).
• Data Queries links to the UQL User Guide and has updated information on the Alias parameter in FETCH and ORDER clauses and new information on parameterized queries.
• UI Enhancements has updated template types.
• FSO Platform CLI has instructions for authenticating with an agent principal.
• There is a link to the new Knowledge Store API documentation.
• Health Rules contains new information about the health rule expression language.

May 2023

This release is only for the Design Partner Program and does not include release notes.