Does the agent need inbound network access to my SAP hosts?

No. The agent is outbound-only. It polls Farrenio over HTTPS for its config and pushes metrics the same way. No new firewall rules, no exposed ports on your SAP boxes.

Can my service desk see alerts without touching production?

Yes. The service_desk role is read-only on alerts and incidents, with no SAP transaction access, no config changes and no token reveal. Granular per-action RBAC means you can carve out exactly what each team sees.

How long does a proof of concept take?

A 30-minute call to scope. We typically have one production SID streaming live metrics within an hour of agent install, and the rest of the landscape follows as fast as you can roll out the package.

SAP-level monitoring · 02

Green dashboards, frozen SAP: what infrastructure monitoring cannot see

Your infrastructure monitoring can be perfectly green while your SAP system is effectively down. CPU at 40 percent, memory fine, disk fine, and every dialog work process stuck in PRIV mode.

Request a demo All insights

The host is healthy. The system is not.

Infrastructure tools measure the host, and they measure it well. What they do not see is what happens inside the SAP kernel. A system can exhaust its dialog work processes, pile up enqueue locks or fail update requests while every operating-system metric stays comfortably inside its threshold.

That gap is where many SAP incidents actually start. The first alert is a phone call from a user at the hourglass, and the investigation begins with someone logging on to find out which system, which process and which user.

The answer is not a second infrastructure monitor. It is an SAP-aware layer on top of the one you already have: one that reads the system the way a Basis engineer reads it.

SAP signals worth watching continuously

Work process states (SM50, SM66)
Dialog processes in PRIV mode or all busy, long-running processes and their programs.
Lock entries (SM12)
Old or rapidly growing enqueue entries that block business users.
Update requests (SM13)
Failed or stuck updates, which can mean data that users believe was saved was not.
Short dumps (ST22)
A dump that repeats every few minutes is a defect in progress, not background noise.
Buffers and response times (ST02, ST03)
Buffer swaps and drifting dialog response time, before users notice.

How FCC covers it

Collected from every system

Work processes, locks, updates, dumps, buffers and response times read continuously by the collector on each host.

One landscape view

The same signal across every SID, so the drifting system stands out.

Thresholds per system

Alerting that matches how each system really behaves, not one global default.

Beside your existing tools

FCC adds the SAP layer. Your infrastructure monitoring keeps doing its job.

Infrastructure monitoring stays. FCC complements it with the layer it was never designed to see.

Go deeper

Topic

SAP Basis monitoring

The transactions FCC reads and how they appear across systems.

Blog

SM50 in the browser

Work process monitoring across the landscape.

Common questions

Do I need to change my infrastructure monitoring?

No. FCC adds SAP-level visibility on top. Hosts, networks and storage stay with the tools you already use.

How is the data collected?

A collector agent on each SAP host reads the system and sends the results out over HTTPS. No inbound connection is opened.

Find out what your dashboards are not telling you.

Connect one system and compare what FCC sees with what your current monitoring shows. FCC is in Beta.

Request a demo See pricing

"SAP" and SAP product names are used descriptively. Farrenio Cloud Control is a Farrenio product and implies no partnership with or endorsement by SAP.