NET (Agent, Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

problems monitoring app windows service and sql server db

Explorer

problems monitoring app windows service and sql server db

 

Hello,

 

I downloaded an AppDynamics trial version that includes

1.controller and events service,
2.net agents for application monitoring written in .net and installed as a windows service
3.agent for database server sql monitoring

 

 The problem we have is that the agents no longer collect data after about 5 minutes. If they restart the agents collect about 5 minutes and stop collecting .......

Is there any specific parameter that needs to be set somewhere to continue monitoring?

This is the config.xml part of the .net agent

"<app-agents>
  <Standalone-applications>
<standalone-application executable = "C: \ Program Files (x86) \ ... appserver.exe">
<tier name = "Windows Service" />
</ Standalone-application>
<standalone-application executable = "C: \ Program Files (x86) \... AppWinUI.exe">
<tier name = "Standalone Application" />
</ Standalone-application>
</ Standalone-applications>
</ App-agents> "

 

I mention that the application has a part as a Windows service and another that starts using AppWinUI.exe. So both are "exe" and are on the same virtual machine.
The database agent runs on the machine with SQLServer (2008). The user in the sql server base has all possible rights so no rights seems to be the db problem.

 

Thank You,

Sorin

 

 

P.S.This is the error appear in dbagent log file (agent.log)

 

Transient-Event-Scheduler-1] 22 Jun 2018 14:18:29,085 INFO SystemAgentTransientEventChannel - Successfully sent response to controller for [
-Transient-Event-Scheduler-1] 22 Jun 2018 14:18:29,087 INFO SystemAgentTransientEventChannel - TransientEventData{ operation [DBMON_GET_PROCESS_LIST], sessionId [830dd732-af96-4b84-be6b-a4f26aba72db], opId [b62f7d00-75d4-4565-b164-e104d44de804], nvp = [null]}
-Transient-Event-Scheduler-1] 22 Jun 2018 14:18:29,088 INFO SystemAgentTransientEventChannel - ]
-Transient-Event-Scheduler-1] 22 Jun 2018 14:18:29,089 INFO SystemAgentTransientEventChannel - Received operation TransientEventData{ operation [DBMON_GET_BLOCK_TREE], sessionId [830dd732-af96-4b84-be6b-a4f26aba72db], opId [00db7f37-7b51-42b9-9353-7df05b6d45cf], nvp = [null]}
-Transient-Event-Scheduler-1] 22 Jun 2018 14:18:29,133 ERROR DBTransientOperationHandler - Error evaluating operation:TransientEventData{sessionId='830dd732-af96-4b84-be6b-a4f26aba72db', sessionType='DBMON', exceptionMessage='null', data=null, status='', operation='DBMON_GET_BLOCK_TREE', nvp=null, nodeId=23, opId='00db7f37-7b51-42b9-9353-7df05b6d45cf', transientBTSessionId='null', transientBTSessionOperationId='null'} Agent Event Type[null]
Occurred at Time[0]
Summary[null]
Severity[null]
Event Details[{}]
Error IDs[[]]
Correlation Map[{}]
EventProperties[null]

java.lang.NullPointerException
at com.singularity.ee.controller.api.dto.dbmon.DBMonitorConfig.toShortString(DBMonitorConfig.java:575)
at com.singularity.ee.agent.dbagent.config.ResolvedDBMonConfig.toShortString(ResolvedDBMonConfig.java:265)
at com.singularity.ee.agent.dbagent.handler.executor.relational.ARelationalDBTransientOpExecutor.execute(ARelationalDBTransientOpExecutor.java:169)
at com.singularity.ee.agent.dbagent.handler.DBTransientOperationHandler.executeOperationSynchronously(DBTransientOperationHandler.java:65)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel.executeOperationInternal(ATransientEventChannel.java:312)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel.executeOperations(ATransientEventChannel.java:261)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel.access$000(ATransientEventChannel.java:43)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel$EventChannelPollingTask.handleOperations(ATransientEventChannel.java:378)
at com.singularity.ee.agent.commonservices.transientoperations.ATransientEventChannel$EventChannelPollingTask.run(ATransientEventChannel.java:343)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:122)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)

problems monitoring app windows service and sql server db
5 REPLIES 5
Moderator

Re: problems monitoring app windows service and sql server db

Hi ,

For DB Agent could you start a new thread at https://community.appdynamics.com/t5/Infrastructure-Server-Network/bd-p/Infrastructure

For .Net Agent do you see tier named "Windows Service" and "Standalone Application" at the Controller UI ?

Thanks,
Raunak


Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Explorer

Re: problems monitoring app windows service and sql server db

Hello,

 

 

For .Net Agent YES i see tier named "Windows Service" and "Standalone Application" at the Controller UI.

 

Thank You,

S

Moderator

Re: problems monitoring app windows service and sql server db

Great. Now to get BTs identified you will need to create POCO rules in case of Standalone applications.
Please look at
https://docs.appdynamics.com/display/PRO44/POCO+Entry+Points

Thanks,
Raunak


Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Explorer

Re: problems monitoring app windows service and sql server db

Hello,

 

Okay, i will take a  look at POCO.... but why do not I still give data from  my database and applications? And why does he stop collecting data after 5 minutes? Is there a parameter or is it because it's a demo version?

 

 

Thanks,

S

Re: problems monitoring app windows service and sql server db

I think it's a bug in the latest DB collector with MSSQL. Try version dbagent-4.4.1.229 and see if that fixes it.