APMIA SQL monitor with dynamic port
search cancel

APMIA SQL monitor with dynamic port

book

Article ID: 229116

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Trying to configure the infrastructure agent, using the sql bundle. In this environment, SQL database uses dynamic port. In the port configuration, introscope.agent.dbmonitor.sqlserver.profiles.db1.port=, asks me to put in a static port. Can we use a dynamic port instead?

Environment

Release : 20.2

Component : Introscope

Resolution

Yes, you can workaround it by doing:

1. Open schema.json file in apmia\extensions\mssql-dd040621x1607-21.6.0.33\config\schema.json and edit the jdbc url attribute format as below:

BEFORE
"jdbcUrl":"jdbc:sqlserver://{hostName}\\{instanceName}:{port}"

NEW
"jdbcUrl":"jdbc:sqlserver://{hostName}\\{instanceName}"

2. Update the same in schemaExt.json as well.

3. Now make sure SQL Browser service is running on server to resolve instance name to port

4. Restart APMIA agent and check the logs for any errors.

5. Make sure that port property is not commented out, we are checking for not null for this in code. just provide some dummy port value:

introscope.agent.dbmonitor.sqlserver.profiles.db1.port=0

6. SQL browser service should be running on SQL server instance.