BlogBlogA post on somebody's own site or a community platform. Nobody edits it after publication, so it dates from the day it was written.See every one →SAP Community
Zero-Code Tracing in SAP CAP Java with the OpenTelemetry Java Agent
Walks through attaching the OpenTelemetry Java Agent to an unmodified SAP CAP Java bookshop service at startup, with no dependency or code change, and shows the resulting trace for a POST to the Books entity: one Trace ID correlating spans across the HTTP layer, a CAP-level CQN INSERT span, and the underlying JDBC INSERT, each with its Span ID and captured attributes. The agent is configured to export only traces (metrics and logs disabled) via JVM arguments, demonstrating that distributed tracing can be added to a CAP Java application purely through runtime instrumentation.
Where it sits
Explains
TelemetryTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.
Who is behind it
Anjali_Pathakauthor
Properties
About this work
Published
Published on
In topics
Building onedevatlasTopic, edition 1
Building onedevatlas: the idea, the back-and-forth with AI, the wrong turns, and an orb who lost his permanent spot in the atlas.
Group by13 of 13 pieces
Piece, what it offersStill applies
CAP in the age of AI #5 - agents wrap-upCAP in the age of AI #5 - agents wrap-upThe agents topic closed out on what sits around the agent rather than inside it, now that the documentation has moved into capire. The chat preview's session is persisted in the database rather than kept in memory, traces go out through @cap-js/telemetry to a self-hosted MLflow under the OpenTelemetry conventions for generative AI, and the panel is explicit that @agent reuses the MCP adapter's code programmatically without serving an MCP endpoint. It ends in the xtravels sample, where a travel agent delegates to a hotel-service sub-agent and reaches a separately started flight service over MCP through the service binding CAP resolves anyway. Earlier in the hour the same agent answers from a model running on the presenter's laptop, reached as an OpenAI-compatible endpoint.published 2026-10-02
S/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex AIS/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex AIWalks through pulling SAP Cloud ALM's Outbound Logs, Metrics and Traces APIs — OAuth 2.0 client-credentials auth, protobuf-encoded OTLP payloads, and the guardrails needed against its rate limits and 24 GB/30-day retention baseline — plus SAP LogServ's infrastructure logs, into Google BigQuery for multi-year, cross-domain storage. A time-window SQL join then correlates ABAP exceptions, health metrics, infrastructure events and ITSM tickets, with the joined record passed to Vertex AI (Gemini) to draft a structured incident dossier.Rudrapuneet, published 2026-07-22
Autonomous Diagnostics on Kyma Unplugged: Goose + LiteLLM + KRO + SAP AI Core in ProductionAutonomous Diagnostics on Kyma Unplugged: Goose + LiteLLM + KRO + SAP AI Core in ProductionAn in-cluster autonomous diagnostic pipeline on Kyma Unplugged (open-source Kyma, noted to also run on SAP BTP, Kyma runtime): a Goose agent with kubectl access calls SAP AI Core through a LiteLLM proxy, and most of the post is about the quirks of that route — drop_params silently swallowing unrecognised parameters and beta headers, streaming that has to be off when tools are attached, and prompt caching that sits on the Orchestration V2 API rather than the foundation-model path the LiteLLM provider hits. A second Node.js proxy reaches that API, and the author reports caching unconfirmed at production scale, which leaves the roughly $0.004 per static run a target rather than a measured figure. Spend metrics reach SAP Cloud Logging over OTLP through Kyma's Telemetry MetricPipeline while the health analysis itself lands in Kubernetes custom resources read in Busola, and the stack is declared as KRO Resource Group Definitions applied with one Terraform command.quovadis, published 2026-07-09
SAP Integration Suite - External logging to Datadog Using OpenTelemetrySAP Integration Suite - External logging to Datadog Using OpenTelemetrySoftware version update 8.42 of SAP Cloud Integration added OpenTelemetry as an external logging destination for Message Processing Logs, so a tenant can stream them straight to an OTLP-compatible platform such as Datadog. The post walks the full path on Cloud Integration: a BTP HTTP destination carrying the Datadog API key as a header property, a Process Integration Runtime service instance holding the ExternalLoggingActivate role, and the activateExternalLogging API call that turns the stream on, down to parsing the resulting log bodies in Datadog's pipelines. It also records a known limitation: custom-header timestamps arrive at Datadog unset, so only Run Events carry a usable time.Santhosh_Vellingiri, published 2026-05-18
A2A Agents on SAP BTP: Wiring the Agent-to-Agent Protocol into CAPA2A Agents on SAP BTP: Wiring the Agent-to-Agent Protocol into CAPShows how to mount Google's Agent-to-Agent protocol straight into a CAP application's own Express bootstrap hook, so the agent runs inside the same deployment, HANA binding and XSUAA instance as the rest of the service instead of as a separate sidecar. A custom HanaTaskStore and base executor class persist A2A task state and telemetry through ordinary CDS queries and expose it as a read-only service, while the agent resolves its SAP AI Core model and any MCP tool's credentials at call time through the SAP Destination service, forwarding the caller's own JWT for principal propagation.rpagni, published 2026-04-20
Implementation of Observability using OpenTelemetry in SAP BTPImplementation of Observability using OpenTelemetry in SAP BTPTracing across a landscape rather than inside one service — BTP applications, integrations, workflows and automations that also call non-SAP microservices the customer runs. That span is where correlation stops being a nice-to-have, and it is the half @cap-js/telemetry's automatic instrumentation does not reach on its own.Deepankar, published 2025-02-05
Performance Trace Node.js App on BTP with DynatracePerformance Trace Node.js App on BTP with DynatraceWalks through wiring Dynatrace as a third-party APM for a Node.js app on SAP BTP, as an alternative to the platform's own internal monitoring: creating an access token and a user-provided service instance, binding it in manifest.yaml, and adding the @dynatrace/oneagent-sdk package for distributed tracing across app router, IDP and connectivity-proxy hops. An appendix covers turning on @sap/approuter's debug-level log output through the XS_APP_LOG_LEVEL environment variable.jeremy_ma_usa, published 2024-09-04
Evaluate SAP Integration Suite, Advanced Event Mesh Datadog Distributed TracingEvaluate SAP Integration Suite, Advanced Event Mesh Datadog Distributed TracingWalks through testing Advanced Event Mesh's Distributed Tracing feature once it is configured: the event broker emits a Send or Receive span for each publish, acknowledgment, enqueue and receive, and an OpenTelemetry receiver reads these off a queue for Datadog. A two-region Try Me scenario, publishing with persistent delivery mode and consuming on a bound queue, produces a traceable exchange between the brokers, then the Datadog APM Trace Explorer is navigated to find it and filter by status, error detail and publisher or subscriber span kind.FlorianOkos, published 2024-07-31
Configure SAP Integration Suite, Advanced Event Mesh Distributed TracingConfigure SAP Integration Suite, Advanced Event Mesh Distributed TracingA configuration walkthrough for Distributed Tracing within SAP Integration Suite, advanced event mesh's telemetry: creating a Tracing Destination, enabling Trace and Receiver on a message broker, defining Trace Filters with their topic subscriptions, then enabling and deploying tracing on the broker itself. The default destination is AEM Insights, with OpenTelemetry or Datadog named as alternative targets, and a companion post on configuring Datadog is promised separately.FlorianOkos, published 2024-07-10
Adding Custom Metrics to a CAP application using cap-js/telementry plugin and SAP Cloud LoggingAdding Custom Metrics to a CAP application using cap-js/telementry plugin and SAP Cloud LoggingWalks through adding a custom OpenTelemetry counter metric to a CAP application on top of @cap-js/telemetry's built-in database-pool metrics, incrementing and decrementing it from a service handler on CREATE and UPDATE of high-urgency incidents. Shows the resulting metric in SAP Cloud Logging's Discover and Visualize screens, building a custom visualisation from the exported metrics data.gopalanand, published 2024-06-27
Kyma Integration with SAP Cloud Logging. Part 2: Let's ship some tracesKyma Integration with SAP Cloud Logging. Part 2: Let's ship some tracesWalks through shipping traces from SAP BTP, Kyma runtime to SAP Cloud Logging: a Kyma TracePipeline resource pointed at the service binding's OTLP endpoint, an Istio Telemetry resource that sets the mesh-wide sampling percentage, and Cloud Logging's Trace Analytics view to filter the resulting spans by service name or request ID. For a multitenant JavaScript CAP application it instruments with @cap-js/telemetry, naming the npm packages to add, and covers Cloud Native Buildpacks and manual Istio header propagation for services outside CAP.gabbi, published 2024-04-19
SAP Cloud Logging Serviceでコンテナメトリクスを監視するSAP Cloud Logging Serviceでコンテナメトリクスを監視するIn Japanese. Container metrics for a CAP Node.js application into SAP Cloud Logging Service, and the reason it exists is that the obvious route does not apply: Spring Boot Actuator covers the Java side, and Node has no equivalent, so the author reaches for Telegraf instead. The procedure is deliberately independent of application logic — bind the instance, add a startup script and a config file — so it works against an application you already have.kyoneo, published 2024-03-26
Monitor your AI agents with the SAP Cloud ALM solutionMonitor your AI agents with the SAP Cloud ALM solutionObserving AI agents with SAP Cloud ALM, which SAP's abstract says is now part of the SAP AI Agent Hub: agent telemetry integrated with application data into one view across agents and the systems they run beside, the telemetry concern read from the operations side. Neither SAP Cloud ALM nor the AI Agent Hub is an atlas entry, and the abstract states the integration as a promise and names no signal or tool. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Carsten Heinz, Frank Wenzke and Stefan Lahr, written here from SAP's abstract; the recording is not yet published.
Details
Graph
Source
Type
blog
Published on
Host
community.sap.com
Discovered via
First seen
History
- Entered the atlasDiscovered via SAP Community · cap-tag.
For your agent
- Ref
content:zero-code-tracing-in-sap-cap-java-with-the-opentelemetry-java-agent- JSON
- /content/zero-code-tracing-in-sap-cap-java-with-the-opentelemetry-java-agent.json
- MCP
- Connecting an agent