SAP NetWeaver
The SAP NetWeaver source collects metrics from an SAP NetWeaver instance by calling the SAPControl web service exposed by the SAP Start Service (sapstartsrv). Bindplane connects to the instance over HTTP or HTTPS using OS-user basic authentication and scrapes availability, work process, CPU, memory, session, request, queue, lock, connection, cache, and short-dump metrics on a fixed interval.
Supported Telemetry Types
Linux
✓
Prerequisites
Supports SAP NetWeaver 7.10 and later.
The collector must run on the SAP NetWeaver host. Some metrics (certificate validity, and the optional RFC and session-count metrics) require executing OS-level commands locally, so a remote collector cannot gather them.
Connecting requires a valid OS user and password. SAP NetWeaver authenticates the SAPControl web service with the host operating system user via HTTP basic auth, and the user needs read access to the SAP instance. For SAP NetWeaver 7.38 and later, collecting some metrics also requires execute or write permission for the sapstartsrv instance.
The SAP Start Service exposes SAPControl over HTTP port 50013 and HTTPS port 50014 for instance number 00. Adjust the port for your instance number. See the SAP Start Service documentation for details on the SAPControl interface and ports.
Configuration

Connection
Hostname
string
Yes
localhost
The hostname or IP address of the SAP NetWeaver system.
Port
int
No
50013
The TCP port of the SAP NetWeaver system. Use 50013 for HTTP and 50014 for HTTPS, adjusted for your instance number.
Username
string
Yes
(empty)
The username to use when connecting to SAP NetWeaver.
Password
string
Yes
(empty)
The password to use when connecting to SAP NetWeaver. Stored as a sensitive value.
Advanced
Collection Interval
int
No
60
How often (seconds) to scrape for metrics.
Profile
string
No
(empty)
The profile path in the form /sapmnt/SID/profile/SID_INSTANCE_HOSTNAME, used to collect the optional RFC and session-count metrics. See SAP profile documentation.
Metrics
metrics
No
(empty)
Toggle individual metrics on and off. By default all metrics are enabled; listing a metric here disables it.
TLS
Enable TLS
bool
No
false
Whether or not to use TLS. Enable when connecting over HTTPS (typically port 50014).
Skip TLS Certificate Verification
bool
No
false
Skip TLS certificate verification. Only relevant when Enable TLS is true.
TLS Certificate Authority File
string
No
(empty)
Certificate authority used to validate TLS certificates. Only relevant when Enable TLS is true.
TLS Client Certificate File
string
No
(empty)
A TLS certificate used for client authentication, if mutual TLS is enabled. Only relevant when Enable TLS is true.
TLS Client Private Key File
string
No
(empty)
A TLS private key used for client authentication, if mutual TLS is enabled. Only relevant when Enable TLS is true.
Examples
Collect metrics over HTTP from a local instance
This example scrapes the SAPControl web service on the default HTTP port of a local SAP NetWeaver instance every 60 seconds.
Collect metrics over HTTPS with the profile path
This example connects over HTTPS on port 50014 and sets the profile path so the optional RFC and session-count metrics are collected.
Configuration Tips
Match the port to the protocol: use
50013with TLS disabled for HTTP, and50014with TLS enabled for HTTPS, adjusting for your instance number.Certificate validity, RFC, and session-count metrics are only available when the collector runs on the SAP NetWeaver host. Set the Profile path to enable the RFC and session-count metrics.
Use the Metrics toggle to disable metrics you do not need rather than collecting the full default set.
Troubleshooting
Authentication failures
Symptoms: the source produces no metrics and the collector logs report authorization or 401 errors from the SAPControl endpoint.
Solutions:
Confirm the Username and Password belong to a valid OS user on the SAP NetWeaver host with read access to the instance.
For SAP NetWeaver 7.38 and later, confirm the user has execute or write permission for the
sapstartsrvinstance.
Connection refused or wrong port
Symptoms: the collector cannot reach the endpoint, or TLS handshake errors appear.
Solutions:
Verify the Port matches your instance number and protocol (
50013for HTTP,50014for HTTPS at instance 00).If connecting over HTTPS, set Enable TLS to
true. For self-signed certificates, supply the CA file or temporarily enable Skip TLS Certificate Verification.
Missing RFC, session-count, or certificate metrics
Symptoms: most metrics appear but the RFC, session-count, or certificate-validity metrics are absent.
Solutions:
Confirm the collector runs directly on the SAP NetWeaver host, since these metrics require local OS command execution.
Set the Profile path to the instance profile so the optional RFC and session-count metrics are collected.
Standalone Source
Related Resources
Last updated
Was this helpful?