Azure Monitor for SAP Solutions (Preview)

Question

Hi Experts,

I tried myself deploying the monitor in a trial subscription using BW/4HANA
and I could get the Hana (2.0) part running without a problem.
I'm running on Hana 2.0 and SAP Netweaver 7.53

However, a problem occured in Netweaver provider: the default monitor workbook shows no data.

The Netweaver provider was successfully deployed:

• Write ProviderInstances succeeded
• Logs are comming into the log monitor:
  • SID_s A4H
    dispstatus_s SAPControl-GREEN
    features_s ABAP|GATEWAY|ICMAN|IGS
    hostname_s vhxxxx
    httpPort_d 50013
    httpsPort_d 50014
    instanceNr_d 0
    serverTimestamp_t [UTC] 2021-06-01T08:38:34.158Z
    startPriority_s 3
    timestamp_t [UTC] 2021-06-01T08:38:34.217Z
    Type SapNetweaver_GetSystemInstanceList_CL
• but the Performance workbook shows no data:

I removed the Webmethods from the Protected list in Netweaver instance via RZ10 so they can be accessed
by the Monitor and restarted the instance as stated in the docs:

service/protectedwebmethods = SDEFAULT -GetQueueStatistic –ABAPGetWPTable –EnqGetStatistic –GetProcessList  

I thought they should also appear in the logs during access, but they aren't.

Only the unprotected method GetSystemInstanceList seems to be running:

I checked the also the queue of the Netweaver provider and it seems the methods are executed but the data is not displayed in the workbook:

Do you have an idea whats going on?
It seems the protected webmethods GetQueueStatistic ,ABAPGetWPTable , EnqGetStatistic ,GetProcessList are accessed but somehow
the result data is NOT transferred to the default workbook of SAP Netweaver Monitor.

Would appreciate if you could help...
Thanks

Answer 1

Azure Technical Team connected offline with customer to walk him through proper configuration of hostname + subdomain, and then discovered customer had extra complication of having custom /etc/hosts file definitions to map virtual hostnames to specific VMs, and thus the collector VM was not able to resolve. After assisting with adhoc steps like propagating hosts file changes to collector VM and restarting container, customer was able to add net weaver provider successfully.