@gopalanand - Is it mandatory to use SAP Cloud logging service with standard plan, Can't it work with Dev plan or application logging plan ?
Please take note of the following information:
The Development Plan is intended for evaluation purposes only and should not be used in production scenarios because it lacks essential cloud features such as auto-scaling and data replication.
Additionally, it has limited ingestion throughput and is not suitable for testing workloads that exceed its 7.5 GB storage capacity.
We currently utilize this plan in our development environment.
If available in your subscription plan (CPEA), you can still use the "SAP Application Logging Service."
Consider migrating to "SAP Cloud Logging," the successor to the SAP Application Logging Service, for access to additional features.
We are uncertain about the retirement timeline for "SAP Cloud Logging." Perhaps @gopalanand can provide further information on this matter.
SAP Cloud Logging is the successor of SAP Application Logging service for SAP BTP. The deprecation of SAP Application Logging service is in preparation and will be announced soon. The detailed timelines for that step will be made available with the upcoming announcement. SAP Cloud Logging can be used as a drop-in replacement.
@Bibhu @gopalanand - We have SAP Application Logging Service and We also tried with SAP Cloud Logging Development Plan but its not sending real time monitoring data to CALM on both node.js and JAVA stack.
So I am looking forward for understand more about if plugins for CALM works with Application logging or cloud logging service Dev plan.
HI Mantrisagar, just to clarify the apps need to be instrumented to send out data to two targets: Logging stack and CALM backend. CLS/ALS are not sending data to CALM, the application should send data to CALM. The procedure to setup your application for both CLS/CALM is explained here: https://github.com/SAP-samples/btp-developer-guide-cap/tree/main/documentation/observability