The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
| Applicable Product(s) or Functional Area | PCF |
| Applicable Platform(s) | SMI |
| Feature Default Setting | Enabled – Always-on |
| Related Documentation | Not Applicable |
| Revision Details | Release |
|---|---|
| First introduced. |
2020.02.0 |
PCF provides a centralized view of the application logs that are consolidated from different containers. The unified view improves the efficiency as you can determine the issue faster instead of accessing the individual containers to view the logs. Collection of logs from the containers is enabled by default.
You can view the logs in the real time and offline mode. The real-time mode captures the current event activity that is performed on the container. In the offline mode, you have the flexibility to access the logs from a remote machine.
Logs are listed based on the timestamp at which they are generated.
This section describes how this feature works.
The OAM node hosts the logs which different application containers generate. These containers include the pcf (engine), pcf-rest-ep, policy-builder, diameter-ep, ldap-ep, crd, and unifiedapi.
This section describes how to view the consolidated application logs.
To view the consolidated logs, use the following command:
kubectl logs -n namespace consolidated-logging-0 NOTES:
namespace – Specifies the namespace under which PCF is deployed.
This section provides information for troubleshooting any issues that may arise during the feature operation.
If the logs are not generated in the consolidated-logging-0 pod, then one of the following conditions may be causing the failure. To resolve the issue, make sure that you do the following:
Verify the status of <namespace>-pcf-oam-app helm deployment. To view the configured helm charts and their status, use the following command:
helm list Ensure that the gRPC stream appender is enabled by verifying the contents of cps-logback configMap. To verify the contents, use the following command:
kubectl describe configmap -n namespace cps-logback Ensure that the consolidated-logging-0 pod is up and running. To check the pod status, use the following command:
kubectl describe pod consolidated-logging-0 -n namespace Verify that the consolidated-logging-0 pod is accessible through the consolidated-logging service. To verify the connection,
use the nc command.
Feedback