CCMSPING not collecting "Dialog Response Time"

In Solution Manager 4.0, we have configured the CCMSPING agent to monitor a number of systems. For only two of those systems, CCMSPING is not collecting "Dialog Response Time" (Availability_DiaRespTime) and "Standardized Response Time" (Availability_StdRespTime) data. All other MTE's for those two servers are being successfully collected. Looking at CPH, for at least one of those systems, the data was collected for a couple of weeks and then stopped. For the other system, that data has never been collected. The two systems with problems are the only two ECC 6.0 systems in the landscape. In the RZ20 monitor, all that it says is that the "Value is obsolete". I have deactivated and reactivate CCMSPING one of the systems without any change.
Has anyone seen anything like this? Is there any way that I can find out what errors are occurring?

I have already a ccmsping agent registered on my central system but it seams to be not correctly registered.
I registered correctly the agent with the '-push' option and it seams to work properly now.
Thanks for your response
Regards,
Emmanuel Coindre.
[www.emmanuelcoindre.fr|http://www.emmanuelcoindre.fr]

Similar Messages

Dialog Response Time is Missing in ST03N

Hi,
In one ofour SAP system the dialog response time data is missing in ST03 however other Task type such as RFC,SPOOL,AUTOABAP,AUTOCCMS,BACKGROUND etc are visible.
OS COllector job is running fine and collecting all data except DIALOG
Step for issue reproduction :
ST03n > Expert Mode > instance > under workload overview > Task Typne Name ( Here it should show the data/response time for Background,spool,update etc).
Kindly help me to know why it is missing. Screenshot for the same is attached here.
Regards,
SURYA.

Hello Surya
here screenshots from my test:
ST03 for my instance before I have executed something on it, no dialog task type:
here I have connected to the instance through SM51, still no dialog task type:
and here I have connected directly through SAP Logon to this instance, now my actions on the instance are displayed as dialog task type:
If your users connect through RFC to the instance, then all their actions are RFC task type actions. As soon as a user logons directly to the instance, dialog task type will appear in ST03.
regards,
Alwina

Dialog response time exceeds threshold (SOLMAN Alert)

Dear All,
I found an alert in Solution Manager,
2.023 msec > 2.000 msec Dialog response time exceeds threshold (56 dialog steps)
What does this alert means?
Are SAP system still in a good performance?
And what kind of action i have to do to clear this alert..?
thanks and regards
Rio(nubie)

Hi
What does this alert means?
see answer Mapp Tyrone above
Are SAP system still in a good performance?
SAP performance is not determined only by response time. you have to look globally: your free memory, your ABAP dumps, your swap, your database statistics etc.
And what kind of action i have to do to clear this alert..?
No need to clear it. All you have to do is tune your SAP system to increase your current performance, and one indicator of that is the better response time.
hope it help you.
rgds,
Alfonsus Guritno.

High Dialog response time

Hi,
We have a solman 4.0 system. The average dialog response time of the system is very high. What can be done to bring down this response time??
Thanks in Advance
Amit.

Hi Amit,
Please check out the breakdown of dialog response time in Workload Monitor. Also, use the Time Profile to check if this high response time is at specific timings.
regards, Shantanu

Dialog response time comaprison between cities

Is there any way where we can compare dialog response time in different cities for the same transaction?
As we are facing issues with response time in 2 different cities and response time in 1 city is lesser comared to other city while fetching the same data.
System is an ABAP ECC 6.0 R/3 system.
We checked that GUI time is also different in both cities.

Hi,
Check the network times from each city with the SAP utility niping.
Check also if people from the different cities are connected to the same application servers.
Regards,
Olivier

Average Dialog Response Time.

Hello friends.........
What is the table or function module that stores the data of Average Dialog Response Time (transaction ST03)? After executing ST03, when a particular date is selected, i need the table or function module that stores the value corresponding to Dialog and Time.
Thanks & Regards,
Ajay.

check ST05? i dont have idea on St03.
or STAT .
Regards
Prabhu

Table name for dialog response time without GUI in ST03?

In SWNC_COLLECTOR_GET_AGGREGATES, cnt00x (x =1,2,3... 9) gives me the proportion of transaction steps with a response time between 0s and the upper limit of the individual response time categories (includes GUI time), broken down by task type. But where is the data without GUI time store? any ideas?

Hello Surya
here screenshots from my test:
ST03 for my instance before I have executed something on it, no dialog task type:
here I have connected to the instance through SM51, still no dialog task type:
and here I have connected directly through SAP Logon to this instance, now my actions on the instance are displayed as dialog task type:
If your users connect through RFC to the instance, then all their actions are RFC task type actions. As soon as a user logons directly to the instance, dialog task type will appear in ST03.
regards,
Alwina

Response times -- Dialog Steps Week / Weekend: How to compare it?

Hello,
We have SAP ECC 6.0 running on a HP-UX Cluster. Our service is a 7x7 24x24.
Like most of companies system activity is lower in the weekend, for example:
From Monday to Friday an average of 2.500.000 DIALOG Steps with a response time of 900 ms.
On Saturday we have an average of: 650.000 DIALOGS Steps with a response time of 650 ms.
On Sunday we have an average of: 250.000 DIALOG Steps with a response time of 450 ms.
So the question is: It have sense that with 10% of user activity on sunday response time is near to 50% (comparing 450ms on sunday with 900 ms in the week) why the response time on sunday is not 10% of response time in the week, something like 90 ms?
What is the correct way to analyze this numbers? Probably you never will have a linear function to represent this situation (in fact this is a Exponential function). SAP always have this behavior?
sap_responseTime(t) = exp(t) Where t is the time in ms.
F(450) = 250.000
F(650) = 650.000
F(900) = 2.500.000
Please some tips about this topic.
Best Regards,
Erick Ilarraza

Hi Erick
Response times entirely depend on the overall system hardware, usage and user activities over the system. In your case, during weekends , a lower number of dialog steps suggest fewer dialog logons in comparison to the weekdays.
In contrast, the response time ( 50%) in comparison to weekdays suggest that the users are executing some heavy transactions that show increased overall response time. These may be transactions that run reports with expensive SQL statements or fetch huge volumes of data from your database ( in comparison to the weekdays).
There cannot be a linearity maintained between the dialog steps and response times when users log in and work randomly in a system
I hope this helps
Regards
Chen

Slow response time for "Print Settings" dialog in CS6

steps performed to resolve - with no success:
disabled NET DRIVER HPZ12
updated CS6 with latest fixes
printer driver is up to date
usb driver up to date
swapped USB ports across three ports
ran font test with no errors
changed default Win 7 printer to Adobe PDF.
Windows 7 has latest fixes.
Configuration is:
     Win 7 Home 64 bit
     8 core AMD
     16 GB memory
     Photoshop CS6 64 bit
     HP c410a printer - USB connected
32 bit Photoshop CS4 on the same platform does not have the response time issue.

From Adobe Support: 17 secs response time is a normal time interval for the "Print Settings" dialogue.

Average Response Time Different in SLR/EWA (in solman) and ST03 (in satelli

Hi All,
We find that the average dialog response time shown in SLR and EWA reports of Solman is much lower (250 ms) whereas the dialog response time shown in ST03 transaction of the system (XI instance) is high 2000 ms.
Which one is correct and how can I correlate these two values if both are right in their own way.
regards

Hello,
The data source is ST03, therefore unless there is an issue with the collectors, you should assume the ST03 data is correct.
Pleae run RTCCTOOL on the managed system and ensure ST-PI and ST-A/PI are current.. Also make sure your SAPOSCOL is current.
There is a possibility that there was an error during preparing the transport to send the data back to Solution Manager, so scan the SDCCN task logs for any errors/warnings on the managed system. You can also check the transport to see what vaues are being returned to Solman's service session. If the have the same value as ST03 at this point, then there is an issue witht eh EWA/SLR provcessing. If the data is not the same here as ST03 then there was an issue with the SDCCN tasks.
If the data collection is not at issue and the transfering of that data to Solution Manager service session had no errors, then Please follow Jared's recommendation, as this would then be an issue processing the service sessions, and this could be due to outstanding Service Content updates. This can be checked with transaction code AGS_UPDATE.
Regards,
Paul

Avg iview response time

At Workload Analysis (Sol man Diagnostics) why I have u201CAvg servlet/webdynpro response timeu201D and u201CAvg iview response timeu201D?
I mean, the request time of the iview is calculated separated from the request time of the servlet (In case I have an iview with a servlet inside), if so I have to sum both to have the complete time request? Or the KPI u201Cavg iviewu201D is for the iviews that does not have a servlets or a webdynpros inside?
I am a little confused with these concepts, someone can explain to me or show me some document that explains this?
Thanks in advance
Regards,
Walde Requena

I don't understand the question.
Do you want to know how to display dialog response time in ST03? If so, your instructions tell how to bring up that screen. It will show Dialog response time providing there have been Dialog steps executed.
Or do you want to know which function module you call to get dialog response time data? Use SAPWL_WORKLOAD_GET_STATISTIC to get hourly, daily, etc. data (for a given day and instance) for each task type.
Tim

Ranking response times for Fire Department

Hello,
I'm in the middle of powerpivot pro's online course, but I'm looking for a little feedback to see if I'm on the right track with a project. I work for a fire department and we collect the response times of our units. As you can guess, we have goals we measure
against and I'm hoping powerpivot will be a good choice to work with. Simply put, for each incident (fire, medical) I create a response time using a calculated column in powerpivot window subtracting the arrival time from the dispatch time (format HH:MM:SS).
I am populating the workbook with a database connection to our SQL database. I group the incidents using the unique incident number in a pivot table, so it list every unit that was on the run. My idea would be to create a measure listing each unit's response
time, looking for the minimum time and compare the minimum against our goal. The result returns either true or false.
I"m working on the solution, but I'm just wondering if my idea sound plausible using powerpivot?
I'm not looking for anyone to do my work, but looking for any suggestions to push me in the right direction.
Thank you for looking , Brent

Hello Paul,
The calendar table was something I just put in because of a lesson I had with Rob's course, so I was in the processing of adding it to the project as a means of reinforcing the lesson. I will take another look at our SQL database, but
in the database, the incident and apparatus tables are primarily linked by the incident key. I will double check to see if the apparatuses in the table have another relationship with a look up table and I can change the data model. Initially, I was looking
for the simplest model to start with and then build from there.
As far as the error, the min function is working correctly to find the minimum time of the incident, but I think my confusion comes with the grouping of the rows. As you can probably tell, there is one incident key for each fire call
and many apparatus are assigned to the call with the incident key as the primary relationship. If I add all the incidents to the pivot table, it correctly identifies each incident as being met or not met. But, if I remove the incident keys from the pivot and
just keep the months, the pivot table correctly filters down to the month and find the minimum of the entire month and I loose the details of each incident's value of met or not met. Thank to Rob, I understand what is happening, but not how to fix it (I'm
finishing up the calendar table now and the X factors are next, which will probably help me with this issue).
The reporting for now, is pretty simplistic. It is being able to identify each incident, if it met the goal and then able to report out of the incidents how many we made and how many we missed. If we had 1,000 calls and we made 500 of them, we would be at
50%. The goal is a simple true or false based on the minimum time of the first arriving unit ( I used 200 seconds for this project).
I do have Excel 2013, so I can open the file. I created the original at home with 2010.
I hope that make sense. Thank you for the help. I have the day off and I'm working through Rob's video course most of the day today. Thanks, Brent

Response times, interpretation times and round trips time

Hi
Can some body explain me what these terms means exactly ? What is their significance ? Appreciate answers without help links.
thanks
kumar

Hai,
Interpretation times: This is the duration from the time that user input actions are validated in the SAP GUI client and the moment the request is actually sent to the SAP application server. This measures the health of the SAP GUI client used for the test rather than the performance of the SAP R/3 server.
Check SAP Note: 364625.
Response Time: The response time of a transaction step is the difference in time between the point when the request arrives in the R/3 System and the point when the R/3 System completes the processing.
Check SAP Note: 8963 and 851012.
Round trip times: Is almost same as the response time. Time from client - LAN - Server and back to the client is known as Round trip time.
Regards,
Yoganand.V

ACE 4710: Find out the response time of a real server

Hi to everyone,
I have a couple of ACE 4710 and I need to find out what is the response time of a real server.
Is there a way for this?
Thank you for any answer!
giorgio romano

Hi,
Kindly add the following line in your serverfarm configuration:
predictor response syn-to-synack
Suppose your serverfarm looks like this:
serverfarm host AAA_FARM
predictor response syn-to-synack
probe HTTP_PROBE
probe TCP9001_PROBE
rserver SC106
inservice
rserver SC107
inservice
rserver SC108
inservice
rserver SC109
inservice
rserver SC110
inservice
rserver SC111
inservice
rserver SC112
inservice
rserver SC113
inservice
rserver SC114
inservice
rserver SC120
inservice
rserver SC131
inservice
And then use the following command to see the average response time from your rserver as follows:
ACE1/prod# show serverfarm AAA_FARM detail
serverfarm     : AAA_FARM, type: HOST
total rservers : 11
active rservers: 11
description    : ServerFarm AAA
state          : ACTIVE
predictor      : RESPONSE
method            : syn-to-synack
samples           : 8
failaction     : -
back-inservice    : 0
partial-threshold : 0
num times failover       : 0
num times back inservice : 0
total conn-dropcount : 0
Probe(s) :
HTTP_PROBE, type = HTTP
TCP9001_PROBE, type = TCP
----------connections-----------
real                  weight state        current    total      failures
---+---------------------+------+------------+----------+----------+---------
rserver: SC106
x.x.x.x.:0        8      OPERATIONAL 2          1125       0
max-conns            : 4000000   , out-of-rotation count : 0
min-conns            : 4000000
conn-rate-limit      : -         , out-of-rotation count : -
bandwidth-rate-limit : -         , out-of-rotation count : -
retcode out-of-rotation count : -
load value           : 0
average response time (usecs) : 81   ----> thats what you might be looking for
From other day :
rserver: SC114
x.x.x.x:0        8      OPERATIONAL 70         10903      2
max-conns            : 4000000   , out-of-rotation count : 0
min-conns            : 4000000
conn-rate-limit      : -         , out-of-rotation count : -
bandwidth-rate-limit : -         , out-of-rotation count : -
retcode out-of-rotation count : -
load value           : 0
         average response time (usecs) : 1334                       ----> thats what you might be looking for
For Serverfarm BBB_FARM
serverfarm     : BBB_FARM, type: HOST
total rservers : 1
active rservers: 1
description    : ServerFarm BBB
state          : ACTIVE
predictor      : RESPONSE
method            : syn-to-synack
samples           : 8
failaction     : -
back-inservice    : 0
partial-threshold : 0
num times failover       : 1
num times back inservice : 1
total conn-dropcount : 0
Probe(s) :
----------connections-----------
real                  weight state        current    total      failures
---+---------------------+------+------------+----------+----------+---------
rserver: SC208
x.x.x.x:0        8      OPERATIONAL 0          0          0
max-conns            : 4000000   , out-of-rotation count : 0
min-conns            : 4000000
conn-rate-limit      : -         , out-of-rotation count : -
bandwidth-rate-limit : -         , out-of-rotation count : -
retcode out-of-rotation count : -
load value           : 0
         average response time (usecs) : 0   ----> thats what you might be looking for
Use more detials for response predictor:
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/rsfarms.html#wp1068831
Configuring the Application Response Predictor
To instruct the ACE to select the server with the lowest average response time for the specified response-time measurement based on the current connection count and server weight (if configured), use the predictor response command in server farm host or redirect configuration mode. This predictor is considered adaptive because the ACE continuously provides feedback to the load-balancing algorithm based on the behavior of the real server.
To select the appropriate server, the ACE measures the absolute response time for each server in the server farm and averages the result over a specified number of samples (if configured). With the default weight connection option configured, the ACE also takes into account the server's average response time and current connection count. This calculation results in a connection distribution that is proportional to the average response time of the server.
The syntax of this command is as follows:
predictor response {app-req-to-resp | syn-to-close | syn-to-synack}[samples number]
The keywords and arguments are as follows:
•app-request-to-resp—Measures the response time from when the ACE sends an HTTP request to a server to the time that the ACE receives a response from the server for that request.
•syn-to-close—Measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives a CLOSE from the server.
•syn-to-synack—Measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives the SYN-ACK from the server.
•samples number—(Optional) Specifies the number of samples over which you want to average the results of the response time measurement. Enter an integer from 1 to 16 in powers of 2. Valid values are 1, 2, 4, 8, and 16. The default is 8.
For example, to configure the response predictor to load balance a request based on the response time from when the ACE sends an HTTP request to a server to when the ACE receives a response back from the server and average the results over four samples, enter:
host1/Admin(config)# serverfarm SFARM1
host1/Admin(config-sfarm-host)# predictor response app-req-to-resp
samples 4
To reset the predictor method to the default of round-robin, enter:
host1/Admin(config-sfarm-host)# no predictor
To configure an additional parameter to take into account the current connection count of the servers in a server farm, use the weight connection command in server farm host predictor configuration mode. By default, this command is enabled. The syntax of this command is as follows:
weight connection
For example, enter:
host1/Admin(config)# serverfarm SF1
host1/Admin(config-sfarm-host)# predictor response app-request-to-resp
samples 4
host1/Admin(config-sfarm-host-predictor)# weight connection
To remove the current connection count from the calculation of the average server response time, enter:
host1/Admin(config-sfarm-host-predictor)# no weight connection
You can use threshold milliseconds parameter which is optional Specifies the required minimum average response time for a server. If the server response time is greater than the specified threshold value, the ACE removes the server from the load-balancing decision process (takes the server out of service).
Enter an integer from 1 to 300000 milliseconds (5 minutes). The default is no threshold (servers are not taken out of service).
In case if you have measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives a CLOSE from the server use syn-to-close      (already discussed previously)
If you have to measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives the SYN-ACK from the server use syn-to-synack   (already discussed previously)
SAMPLES parameter is optional and specifies the number of samples that you want to average from the results of the response time measurement and response time is used to select the server with the lowest response time for the requested response-time measurement. If you do not specify a response-time measurement method, the ACE uses the HTTP app-req-to-response method.
Whenever a server's load reaches zero, by default, the ACE uses the autoadjust feature to assign a maximum load value of 16000 to that server to prevent it from being flooded with new incoming connections. The ACE periodically adjusts this load value based on feedback from the server's SNMP probe and other configured options.
Using the least-loaded predictor with the configured server weight and the current connection count option enabled, the ACE calculates the final load of a real server as follows:
final load = weighted load Ã— static weight Ã— current connection count
where:
â€¢weighted load is the load reported by the SNMP probe
â€¢static weight is the configured weight of the real server
â€¢current connection count is the total number of active connections to the real server
The ACE recalculates the final load whenever the connection count changes, provided that the (config-sfarm-host-predictor) weight connection command is configured. If the (config-sfarm-host-predictor) weight connection command is not configured, the ACE updates the final load when the next load update arrives from the SNMP probe.
If two servers have the same lowest load (either zero or nonzero), the ACE load balances the connections between the two servers in a round-robin manner.
HTH
Plz rate if u find it useful.
Sachin

Management Services Response Time; per Role or per Deployment? Broken?

Management Services, Alert on Response Time, appears to be incorrect.
Can you help me understand why the Response Time charts for each Role in a deployment are identical? is this a bug?
My Testing
I have 3 Roles in my Cloud Service Deployment. A Web Role, a worker Role, and an extra Worker Role for this test.
Web Role: Light load 0 to 10 requests per hour.
Worker Role: Generates massive net work traffic. Constantly making web service calls to 3rd party data services & running a Distributed Azure Data Cache.
Extra Worker Role: No load. I added it to test this problem. It does nothing other than respond to Management Services Alert pings.
I created 3 Alerts to Track response time. One to each of the 3 roles, testing from within the same data center; San Jose to San Jose. Then added 3 more to test from Singapore to San Jose.
The Result (over several Months)
A. The San Jose charts are identical for each role.
B. The Singapore charts are identical for each role.
C. The set of Singapore charts are very similar to the San Jose set of charts. With slight variations likely due to internet latency & extra load at Singapore.
D. (most Important). The latency is directly correlated to the network load created by the Worker Role. When I turn it off or throttle it, Response Time on all boxes drops. When working at "full speed" network response time rises
to 10 - 30 secs. (very bad)
Conclusion
The Network Monitoring Response Time Alert is not working as designed. It does not show the Response Time for that Role. But seems to be displaying the Response Time for the whole deployment.
My Request
Can you assist me to understand if this is "By Design". If my testing is flawed? or what is going on.
My Goal
Alert the Azure dev team to this so that maybe they can fix it to function as I expected it to. (or for them to explain why my expectations are unreasonable.)
Why is this important?
Poor Network Perf is a showstopper bug that is preventing us from moving into production. I may be able to solve this with multiple instances. But as I lack the granularity to track even at the Role level. I'm stuck.

Thank you for your reply.
I forgot to update this with the answer.
It turned out that Azure Portal's Create Alert/monitoring UI has a bug.
The monitoring service is only capable of pining your public endpoints. ie: your Web Roles. Yet it lets you think you can create an Alert to monitor any of the roles within your solution. To make things worse, it shows a chart that suggests it actually is
pinging your worker roles, when it is actually only pinging the public Web Role.
That is why all the Roles in your solution display identical metrics regardless of their load. Even stopping your worker roles will not affect their ping response times.
If your worker role fails, Azure Alerts don't tell you about it.
NB: Using Application Insights to create alerting does not have this issue. But only because it doesn't attempt to monitor your web roles, not because it can alert you to any issues.

CCMSPING not collecting "Dialog Response Time"

Similar Messages

Maybe you are looking for