Release Notes

Cisco Observability Platform 24.7.0

Collectors, Operators, Agents, and Add-ons 

UI Enhancements

Resolved Issues

Known Issues and Limitations

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Cisco Observability Platform 24.6.0

Collectors, Operators, Agents, and Add-ons

UI Enhancements

Resolved Issues

Known Issues and Limitations

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Cisco Observability Platform 24.5.0

Collectors, Operators, Agents, and Add-ons

There is no 24.5 release for any of the artifacts.

UI Enhancements 

Resolved Issues

Known Issues and Limitations

Plugin Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Cisco Observability Platform 24.4.0

Collectors, Operators, Agents, and Add-ons

UI Enhancements 

Category	Summary	Cisco Cloud Observability Version
Agent Management	In previous releases, every restart or upgrade of a collector created a new collector instance in the Agent Management console and Metric Explorer. Metric and data history was not retained across different collector instances. In >= 24.4.0, a collector is represented by a single collector instance that retains historical metrics and data even if the collector is restarted or upgraded. Breaking Change Collector instances and data generated in releases < 24.4.0 have been deleted. Each collector is now represented by one collector instance that retains historical metrics and data from >= 24.4.0.	1.0.53
App Root Cause Analysis using Anomaly Detection	Cisco Cloud Observability can now identify the underlying root causes of an anomaly by correlating infrastructure issues with application issues. For example, if a business transaction anomaly is detected and its root cause is a host or pod issue, Cisco Cloud Observability automatically pinpoint the suspected cause within the host or pod. See Determine the Root Cause of an Anomaly.
Alerting	In past versions, Cisco Cloud Observability had many predefined health rules configured with various MELT data types, conditions, and thresholds against the baseline. In this release, to reduce unnecessary alerts triggered by health rules, only the critical health rules and the health rules that are already modified or saved without any modification by users are enabled by default. Any redundant or duplicate predefined health rules are deprecated.
	You can now test an HTTP action to a configured endpoint and check if the action is working instead of waiting for an actual violation. After testing, you get a success or failure message along with the status code that helps you to debug any issue that might occur while testing the HTTP action. See Create HTTP Request Action.
	On the entity centric page, you can now view all the alerts corresponding to an entity by selecting a specific time range on the Entity Health Timeline graph. Click each alert to view its details and the stages of the alert such as violation started, violation upgraded, violation downgraded, violation continues, and so on. See Health Violation Timeline.
	In an HTTP action payload, you can now fetch the values of the attributes of an entity. To fetch the values in runtime, use ${entityAttrList[0].<attribute_name>} in the payload. See Predefined Variables.
	On the Observe page and the entity centric pages, the health icon NO ALERT RULES ENABLED is displayed for the entities that don’t have any health rules configured or when the corresponding health rules are deleted. See Health and Status Violations in the UI.
Cloud and Infrastructure Monitoring	This release supports a new AWS Events Ingestion feature. You can now send events from Amazon EventBridge to Cisco Cloud Observability and monitor AWS events using the Explore > Events page.
	Cisco Cloud Observability now supports monitoring Amazon DocumentDB.
	Cisco Cloud Observability now supports monitoring Azure Event Hubs.
	Cisco Cloud Observability now supports monitoring: GCP Cloud Tasks GCP Compute Engine Autoscaler GCP Identity and Access Management (IAM) GCP Memorystore for Memcached
Dashboards	Splunk AppDynamics now offers Azure and Service Performance Overview dashboards to detect problems before they happen while viewing multiple entity types and manipulating data to fit your needs.
Kubernetes and App Service Monitoring	This release includes support for more granular entity filters that enables you to apply filters for specific entity types and namespaces. For details, refer to the filters parameter in Cisco AppDynamics Collectors Settings.
	With this release, the following predefined health rules will be disabled by default: K8s Replication Controller Running vs Desired K8s Pod Resource Usage vs Limits K8s Deployment Running vs Desired K8s Statefulset Running vs Desired K8s Daemonset Running vs Desired  K8s Replicaset Running vs Desired K8s Node Resource Memory, PID, Disk Pressure For the complete list of predefined health rules, see Kubernetes Entities. However, if the predefined health rules are modified or saved without modification, the health rules will remain enabled by default.
Logs	For log ingestion from Amazon EC2 Application Logs, you can now specify the EC2 name in AGENT_PLATFORM_NAME.
	Cisco Cloud Observability can now ingest Amazon RDS service logs.
Network Monitoring	This release adds the following features for Network Monitoring: You can now monitor network connections on the list and detail view of the Namespaces entity-centric page. On the Clusters detail view, you can use the new Scope drop-down menu to switch the scope of network monitoring to namespace or workload. The flow map and connection list will be updated based on your selection.
Overview Page	The Overview page has a new Get Started panel that asks you questions to assist you better with onboarding Cisco Cloud Observability.  There is also a new Recently Visited that displays the previous 8 pages you visited and a Restore Page button to restore Overview to its default settings. See Overview.
Platform Monitoring	The Platform Monitoring dashboard now supports filtering your Tenant's telemetry so that you see only what applies to a specific solution or entity.
Schema Browser	You can now view the number of active instances of an entity. On the Explore area, click an entity to view the Number of instances. See Explore Schema.
Service-oriented Investigations	There is a new Visual filter where you can filter using quick filters. See Traces and Spans. Also, you can now customize the columns you want displayed on all APM pages.
	For JMX metrics, there is a new Garbage Collection (GC) column and new Time Spent in Garbage Collections, Garbage Collections, and Thread Count graphs available. See Service Instances Detail.
Traces	You can now configure backend trace sampling to reduce your storage costs. Configuration is available only through the Knowledge Store API.

Resolved Issues

Deprecation Notes

Known Issues and Limitations

Module Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Cisco Observability Platform 24.3.0

Collectors, Operators, Agents, and Add-ons 

Enhancements 

Category	Summary	Cisco Cloud Observability Version
Agent Management	In the 24.2.0 release, the Infrastructure Collector was displayed on the Agent Management console as two collectors: Server Collector and Container Collector. In this release, the Infrastructure Collector is now displayed as a single collector under the name Infra Collector. This is a breaking change. Action is required. In the Metric Explorer, historical health metrics for the Server and Container Collectors will no longer be accessible. To view the Infrastructure Collector in the Agent Management console and to view its metrics in the Metric Explorer, you must upgrade your operators and collectors to version >=24.3.0.	1.0.38
Alerting	For a data-unavailable scenario, you can now control the health rule evaluation to one of the following: Critical or Warning: The health rule considers this no data scenario as Critical or Warning condition and the health rule status is shown in red or yellow respectively. Unknown: The health rule considers the no data scenario as unknown and the health status is shown in gray. Healthy: The health rule considers the no data scenario as healthy and the heath rule status is shown in green.
	From the list view, you can now view the health violation information of the entities that are in critical, warning, or unknown state. Click the health icon to view the violating metrics and the conditions on the HEALTH AND ALERTING inspector panel. For example, if an entity is in a critical state, you can click the health icon to view violating health rules or anomaly detection. This information helps you quickly identify the entity's violations without navigating deeper into the entity page.
	When you link an action to a health rule of an entity, the action applies to only the leaf entity and not to the parent entities in an entity scope path. For example, when you create a health rule for an entity type k8s:pod and select Entity scope as k8s:pd->k8s:cronjob→k8s:namespace, the action that you select for this health rule applies to the leaf entity k8s:pod.
App Root Cause Analysis using Anomaly Detection	While configuring Anomaly Detection for an entity, you can now select the option to evaluate an entity's health for a no data scenario. Select the health evaluation as Unknown or Healthy when no metric data is available for evaluation.
Splunk AppDynamics Support for OpenTelemetry	This release adds the following new configurations for the Cisco AppDynamics Distribution of OpenTelemetry Collector: A new appdynamics-otel-collector.customService configuration to deploy an additional service with a configurable name and Kubernetes namespace. A new appdynamics-otel-collector.presets.selfTelemetry configuration to send the Cisco AppDynamics Distribution of OpenTelemetry Collector's self-telemetry data to different endpoints.
	In the configOverride configuration, the data type of retry_on_failure.max_elapsed_time was changed to time.Duration. If you manually configured retry_on_failure.max_elapsed_time as an integer, you must convert it to time.Duration. Example exporters: otlphttp: retry_on_failure: # max_elapsed_time: 180 should be changed to max_elapsed_time: 180s YML
	This release adds a new batchbybytesize processor. This processor breaks large OTLP data packets into smaller packets and prevents Cisco Cloud Observability from rejecting data packets due to size limitations. See Configure Max Export Byte Size.
Cloud and Infrastructure Monitoring	Cisco Cloud Observability now supports monitoring Azure Container Apps.
	Cisco Cloud Observability now supports monitoring: GCP Memorystore for Redis Cluster GCP Memorystore for Redis Standalone Google Cloud DNS
Documentation	This release includes a new quick start guide for Kubernetes and App Service Monitoring. This installation flow is supported for Amazon Elastic Kubernetes Service, Azure Kubernetes Service, Google Kubernetes Engine, and Red Hat OpenShift.
Logs	Documentation updates: A relocated and reorganized Log Management section helps you to find the instructions you need more easily. Amazon S3 Access Logs explains how to enable Amazon S3 access logs. Configure the Filelog Receiver provides an example of how to configure the Filelog Receiver for multiple log sources with different service names but the same namespace name. Create a CloudFormation Stack includes authentication and service endpoint details.
Metrics	The Cisco Observability Platform now handles inexact intervals between metrics. It aggregates metrics collected at sub-minute granularities into one-minute granularities by default.
Platform Monitoring	In 24.1, Splunk AppDynamics subscribed all Tenants to the Platform Monitoring dashboard. This dashboard provides visibility into the runtime status of the Cisco Observability Platform. In doing so, it consumes your metric tokens to collect telemetry related to your Tenant's runtime environment. Therefore, Splunk AppDynamics has now unsubscribed all Tenants from this dashboard and made it an opt-in choice instead. To opt in, ask Customer Support to resubscribe your Tenant. Resubscribing to this dashboard will again incur the usage of your metric tokens.
Service-oriented Investigations	Splunk AppDynamics now supports .NET for for the downstream Lambda entry span. See  Monitor AWS Lambda Using OpenTelemetry Instrumentation.
	The performance of tail sampling collector metrics has been updated. See OpenTelemetry Trace Sampling.
	The system CPU utilization for Java Agent 2.0 users has been updated. See Service Instances Detail.
	You can now see Span and Traces list and detail view in the BRUM application, as well as in the Cisco Observability Platform application. See Traces View Details.
	For the spans and traces pages, there were many bug fixes including updated Duration numbers, time range enhancements, and recent filters fixes. There is also a new “Examples for Filter” tip that is directly on the UI next to the Spans or Traces name at the top of the Spans or Traces page.
	You can now easily sort metrics on all APM pages.
	There is now a new Service Endpoints list and detail page where you can view greater details on the Service Endpoints. See Services Detail.
	You can now see end-to-end Errors/min for the entire Business Transaction, from the root span to all of its children, which displays a more holistic metric.
	The Observe page has been updated with a new design. See Observe UI Overview.

Resolved Issues

Known Issues and Limitations

Module Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Cisco Observability Platform 24.2.29

Collectors, Operators, Agents, and Add-ons

he Cisco Cloud Observability Helm charts are tested as compatible with Helm v3.13.x. 

Enhancements

Category	Summary	Cisco Cloud Observability Version
Cloud and Infrastructure Monitoring	Cisco Cloud Observability now supports monitoring Amazon SageMaker.	1.0.34
	Cisco Cloud Observability now supports monitoring: Google Cloud APIs GCP Workflows
Collectors and Operators	This release supports Kubernetes nodes running on ARM64 architecture for these components: Cisco AppDynamics Smart Agent Cisco AppDynamics Operator Cluster Collector Infrastructure Collector Cisco AppDynamics Distribution of OpenTelemetry Collector Log Collector The OpenTelemetry Operator for Kubernetes supports ARM64.
Database Monitoring	This release adds: Support for PostgreSQL and Aurora PostgreSQL. See Supported Databases. New Predefined Health Rules for Database Monitoring.
Extend Cisco Cloud Observability Modules	You can now integrate Splunk Enterprise with Cisco AIOps. This integration brings the Splunk alerts into Cisco AIOps to correlate it with data from other monitoring tools. See Splunk Integration.
Log Monitoring	You can now forward your Amazon S3 access logs to Cisco Cloud Observability. See Amazon S3 Access Logs.
	The Log Collector has renamed one of the Kubernetes®  properties which it automatically extracts based on the value of the clusterName parameter in collectors-values.yaml: k8s.container.name is now container.name. This change doesn't affect your collectors-values.yaml.
	New Support for Non-Kubernetes Log Collector Observability: You can now send  metrics from the Log Collector service running on an Amazon EC2 instance to Cisco Cloud Observability. This Log Collector service is not visible on the Agent Management console because this console currently only displays Kubernetes-based collectors, but you can find the metrics associated with this Log Collector service using UQL queries. See Amazon EC2 Application Logs.
	All queries to the backend log store now fetch a maximum of 1000 most-recent fields per index to prevent giant queries from slowing down the UI. See Explore Logs.
	Documentation updates: Ingest Logs Using OpenTelemetry covers more use cases.  Amazon EC2 Application Logs has updated instructions for disabling the default or custom configuration for log collection, and for enabling log collector metrics. Install Kubernetes and App Service Monitoring has updated hardware requirements and supported platforms.
Metrics	The new Explore > Metric Explorer page provides a comprehensive tool for exploring metrics from any domain or entity. Previously, you could only view a limited subset of the metrics that were associated with an entity on its detail view; this view didn't display dynamic metrics, metrics that are associated with other entities, or even all of the metrics that are associated with that entity. Now, you can use the Metric Explorer to see the bigger picture of your environment. See Explore Metrics.
Network Monitoring	This release supports a new Network Monitoring feature for Kubernetes clusters and workloads. This feature uses eBPF to: Visualize and monitor the incoming and outgoing TCP/UDP network connections in your environment. Display the metrics and key performance indicators, properties, and health status of each network connection. Enable you to identify performance bottlenecks and their impact on the performance of your applications.
Service-oriented Investigations	For services, there are now new metric cards that are sorted by Average Response Time (ART), Calls Per Minute (CPM), and Errors Per Minute (EPM). See Services. There are also new flow map enhancements including a new feature where particles flow through neighboring nodes and now when you apply a filter, the flow map now zooms in on the filtered nodes. See Services Detail.

Resolved Issues

Known Issues and Limitations

global:
  clusterName: <cluster-name>
  oauth:
    clientId: <client-ID>
    clientSecret: <client-secret>
    endpoint: <endpoint-URL>
    tokenUrl: <token-URL>

Module Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

Cisco Observability Platform 24.1.31

Collectors, Operators, Agents, and Add-ons

Enhancements

oauth:
   clientId:
   clientSecret:
   endpoint: https://<your-tenant-url>/data
   tokenUrl: https://<your-tenant-url>/auth/<tenant-id>/default/oauth2/token  

Resolved Issues

Known Issues and Limitations

Module Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

December Release - 23.12.x 

Enhancements

processors:
  attributes:
    actions:
      - key: cloud.account.id
        value: "XXXXXXXXX"
        action: upsert 

Known Issues and Limitations

Resolved Issues

Module Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

October Release - 23.10.x 

Enhancements

Deprecation Notice

The Cluster Collectors <23.10 are deprecated. Therefore, ensure to upgrade the collector to version >=23.10. The support to collectors <23.10 will end on January 30, 2024. 

Impact: After January 30, 2024, you will not be able to monitor the associated Kubernetes entities using the relationship pane unless you have upgraded the Cluster Collector to version >=23.10.

Resolved Issues

Known Issues and Limitations

Module Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

September Release - 23.9.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Modules 

Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

August Release - 23.8.x 

Enhancements

Resolved Issues

None.

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

• For the HostProcess containers, the Splunk AppDynamics Collectors do not collect metrics from Windows Exporter. This happens because Windows HostProcess container monitoring is not supported. 

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has Splunk AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your Splunk AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas Splunk AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• Log details are not displayed when you navigate to Observe > Kubernetes > Hosts > <Host Name> > View All Logs. This issue occurs when Log Collector is deployed on Google Kubernetes Engine.
  Workaround: To view the logs for a host on a Google Cloud Platform, you require to navigate to Explore > Logs > Add Filter, and then add filters for attributes(host.id) or attributes(host.name).

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 
• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 
• The filter bar misinterprets the word Severity because it's a reserved word. Avoid this word in full-text searches.

Users may see the 'No Data' message due to query timeout when navigating from the Business Transaction Security tile of the Inspector panel to see log entries with critical sensitive data, especially when the time range selected is 1 Week or more. Workaround: Select a shorter custom time range on the Business Transaction page and try again.

Modules 

Enhancements

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

July Release - 23.7.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

• For the HostProcess containers, the Splunk AppDynamics Collectors do not collect metrics from Windows Exporter. This happens because Windows HostProcess container monitoring is not supported. 

   

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for Splunk AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has Splunk AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your Splunk AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas Splunk AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

  
  

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 
• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 
• The filter bar misinterprets the word Severity because it's a reserved word. Avoid this word in full-text searches.

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

June Release - 23.6.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

• For the HostProcess containers, the AppDynamics Collectors do not collect metrics from Windows Exporter. This happens because Windows HostProcess container monitoring is not supported. 

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

May Release - 23.5.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

• For the HostProcess containers, the AppDynamics Collectors do not collect metrics from Windows Exporter. This happens because Windows HostProcess container monitoring is not supported. 

   

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 
• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 

• When you navigate directly to the Logs page from Explore > Logs, some fields or attributes in the Properties panel are not hyperlinked back to their associated entities. Workaround: Navigate to the Logs page from the entity's detail view ("entity centric page").

• The filter bar misinterprets the word Severity because it's a reserved word. Avoid this word in full-text searches. Also, when you select a recent filter, the Severity menu quick filter doesn't reset to the value you used in that recent filter. 

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

April Release - 23.4.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• We are making constant updates to the site in order to make the user experience better, so the Observe page may not show the most up to date version. If this happens, we recommend clearing your browser's cache by holding down the Shift key and clicking the browser's reload button (or pressing Ctrl+F5 on a Windows computer or Cmd+Shift+R on a Mac computer). The browser will refresh and load the most recent version of the page.
• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

• For the HostProcess containers, the AppDynamics Collectors do not collect metrics from Windows Exporter. This happens because Windows HostProcess container monitoring is not supported.  

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 
• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

March Release - 23.3.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

• For the HostProcess containers, the AppDynamics Collectors do not collect metrics from Windows Exporter. This happens because Windows HostProcess container monitoring is not supported. 

   

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

  
  

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 
• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

February Release - 23.2.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 
• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

January Release - 23.1.x

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

Kubernetes Infrastructure and Troubleshooting

• On Clusters and Namespaces pages, the Persistent Volume Claim (PVC) events are not displayed in Kubernetes Events > View Event Summary. However, these events are listed in the Events detail view.
  To view the PVC events, click Kubernetes Events > Show All Events.
• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

  
  

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings. 

• Logs from cronjobs and jobs, which are part of a workload, are not visible on the workload's entity centric page. 

• On the Logs page, the Log Patterns tab does not appear when you use regular browser mode. Workaround: Use a browser in incognito mode. 

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

December Release - 22.12.x 

Enhancements

Resolved Issues

Known Issues and Limitations

Customer Onboarding and Startup

• Every user has the ability to configure and view all data. This release does not support more granular access control.

• Service-provider initiated SSO is not working (does not redirect to your identity provider), so you can't auto-federate users into your account. Workaround: On the Account Management Portal, assign your identity provider to each user through User Management > View User > Authenticated By > My IdP. 

• Cisco Cloud Observability is available in AWS US West, AWS Sydney and AWS Frankfurt regions only. See About Cisco Cloud Observability and SaaS Domains and IP Ranges. 

Kubernetes Infrastructure and Troubleshooting

• Cisco Cloud Observability may contain links to documentation for AppDynamics APM, which is a completely different product. Workaround: Use only the documentation on https://docs.appdynamics.com/appd-cloud. 
• The list view displays a maximum of 1000 entities of one type.
• The Properties panel shows limited metadata.

• If the cluster you connect to Cisco Cloud Observability already has AppDynamics APM agents running on it, the metrics you see on the Observe page may be different from the metrics you see on your AppDynamics APM Controller. Comparing metrics on the two platforms may yield inconclusive results. There are multiple reasons for this. Cisco Cloud Observability only ingests metrics from AWS CloudWatch, Azure Monitor, and OpenTelemetry™-compatible collectors, whereas AppDynamics App Server agents, such as Machine Agent, send metrics in a proprietary, non-OpenTelemetry format. In addition, those agents are connected to your Controller UI, not to Cisco Cloud Observability. 

  
  

• Some metrics are not displayed for ingress and service entities. Cisco Cloud Observability only displays metrics if your ingress controller is the Kubernetes NGINX controller. There is no support for displaying metrics from other ingress controllers at this time. In addition, if your ingress controller is configured with wildcard domains, there are no metrics for that ingress. To get metrics in this case you need to configure the ingress controller with --metrics-per-host=false (you will lose labeling by hostname, but still have labeling by ingress). 

  
  

Service-oriented Investigations

No known issues.

App Root Cause Analysis using Anomaly Detection

No known issues.

Application Troubleshooting with Logs

• The Log Collector does not filter or scrub out any sensitive data present in log messages. However, you can configure it to drop (omit) fields you specify. See Log Collector Settings.

• Logs from k8s jobs, which are part of a workload, are not visible on the workload's entity-centric page.

  
  

OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.

November Release - 22.11.x 

Enhancements

Category	Summary	Version
Cloud Infrastructure and Troubleshooting	Schema Change On November 17, 2022, we pushed a schema change that affects the Amazon RDS monitoring experience. As a result, Amazon RDS data from before the change is now inaccessible, and existing Amazon RDS health rules no longer work.  Required Actions Recreate your Amazon RDS health rules. See Create Health Rules to Monitor Entities or Group of Entities.	22.11.17
Cloud Infrastructure and Troubleshooting	Updates to the the list/detail views of entities include: Azure databases are now visible. You can now collect and correlate metrics from Azure SQL and PostgreSQL. Amazon RDS observability includes redesigned modeling of Aurora clusters and instances.	22.11.17
Kubernetes Infrastructure and Troubleshooting	Service entities now include a logs histogram.	22.11.17
Kubernetes Infrastructure and Troubleshooting	You can now monitor your Redis and Kafka entities via Prometheus-based exporters to Cisco Cloud Observability.	22.11.17
Kubernetes Infrastructure and Troubleshooting	You can now monitor Red Hat® OpenShift® clusters running on AWS or Azure infrastructure and managed offerings such as Red Hat OpenShift Service on AWS (ROSA) and Azure managed OpenShift. For the list of supported versions, see Software Requirements in Install Kubernetes and App Service Monitoring.	22.11.17
Kubernetes Infrastructure and Troubleshooting	We've updated the AppDynamics Operator and Cluster Collector: They are now based on Golang version 1.19.2. This is an important security update. We've moved their Helm charts to Artifactory cloud at https://appdynamics.jfrog.io/ui/repos/tree/General/appdynamics-cloud-helmcharts/appdynamics-collectors and https://appdynamics.jfrog.io/ui/repos/tree/General/appdynamics-cloud-helmcharts/appdynamics-operators. New artifacts have the following version IDs: appdynamics-cloud-operator: Docker image 22.11.0-763 appdynamics-collectors: Helm chart 1.5.244 appdynamics-operator: Helm chart 1.5.75 Required Actions To get these updates, upgrade the AppDynamics components on your clusters. See Upgrade or Uninstall Kubernetes and App Service Monitoring.	22.11.17
Application Troubleshooting with Logs	Use the Log Parsing Validator to test parsing patterns for your log messages. This tool displays the fields it extracts from a single-line log message, parser type, and pattern you provide. When you're happy with the parsing, you can copy the successful pattern into your Log Collector configuration. This leads to faster onboarding of logs. See Log Parsing Validator.	22.11.17
Application Troubleshooting with Logs	We've updated the Logs page: Breadcrumbs make it easier for you to navigate back to the entity you came from. Group logs by property/metric/tag. View log messages associated with an event when the event ID is included in the log messages. Searching by keyword has a new syntax:  raw = '<keyword>'. Always use single quotes. If you use double quotes or no quotes, auto-complete is unavailable.  The "load" progress of search results now has a visual element: On the histogram, a progress bar moves from right (newest timestamp) to left (oldest timestamp) as the page loads the search results. A new button, Explore All Logs, removes the entity filter so that you see an all logs in the time range you've selected. You can also navigate to this unfiltered view from Explore > Logs. Sort log messages by oldest-first or newest-first. See Explore Logs.	22.11.17
Application Troubleshooting with Logs	You can now configure the Log Collector with subparsers for Grok log messages in the new (June 2022) format of collector-values.yaml. When you specify a subparser, you can extract more fields from different parts of the log message. See Log Collector Settings.	22.11.17
Application Troubleshooting with Logs	Outliers are temporarily disabled on the log histogram of entity detail pages.	22.11.17