cancel
Showing results for 
Search instead for 
Did you mean: 

Cloud Logging endpoints cannot be read

moeka_matsumura
Discoverer
0 Kudos

Hello,
I am attempting to use opentelemetry to get metrics and pass data to Cloud Logging.
I am adding the following to pom.xml under the srv folder of the project.

		<dependency>
			<groupId>com.sap.hcp.cf.logging</groupId>
			<artifactId>cf-java-logging-support-opentelemetry-agent-extension</artifactId>
			<version>3.8.3</version>
		</dependency>

The following image was set up in mta.yaml.

mta2.png

mta1.png

And in the service keys of the cls-test instance, there are endpoints and other authentication information you want to use.

BTP.png

When I deploy and check the log, it outputs that Credential is not found.

2024-05-01T08:20:29.691+0000 [APP/PROC/WEB/0] STDERR [otel.javaagent 2024-05-01 08:20:29:691 +0000] [main] INFO com.sap.hcf.cf.logging.opentelemetry.agent.ext.CloudLoggingConfigurationCustomizerProvider - Initializing SAP BTP Observability extension 3.8.3
2024-05-01T08:20:29.704+0000 [APP/PROC/WEB/0] STDERR [otel.javaagent 2024-05-01 08:20:29:703 +0000] [main] INFO com.sap.hcf.cf.logging.opentelemetry.agent.ext.binding.CloudLoggingBindingPropertiesSupplier - Using service cls-test (cloud-logging)
2024-05-01T08:20:29.704+0000 [APP/PROC/WEB/0] STDERR [otel.javaagent 2024-05-01 08:20:29:704 +0000] [main] WARN com.sap.hcf.cf.logging.opentelemetry.agent.ext.binding.CloudLoggingBindingPropertiesSupplier - Credential "ingest-otlp-endpoint" not found. Skipping OTLP exporter configuration

I am thinking that the Credential is not found because it is not on the cls-test instance, but in the service keys of the cls-test instance.
Could someone please tell me how to reference Credential in Service Keys?

Kind regards,
Moeka.

Accepted Solutions (1)

Accepted Solutions (1)

moeka_matsumura
Discoverer
0 Kudos

After deleting the Cloud Logging instance and recreating it again, the otlp endpoint and certificate information now appears in the credential of the instance.
Cloud Logging is working correctly now!

Answers (0)