AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    To monitor Sybase with Database Visibility, you must be running version 15 or newer. 

    Connection Details

    SectionFieldDescription
    Create New CollectorDatabase TypeThe database type that you want to monitor.
    AgentThe Database Agent that manages the collector.
    Collector NameThe name you want to identify the collector by.
    Connection DetailsHostname or IP AddressThe hostname or IP address of the machine that your database is running on.
    Listener PortThe TCP/IP address of the port on which your database communicates with the Database Agent.
    Custom JDBC Connection StringThe JDBC connection string generated by the database agent, for example, jdbc:db2://. You can also specify a custom connection string, which is useful for setting custom authentication options.
    Username and PasswordUsernameThe name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for IBM DB2 LUW.
    PasswordThe password of the user who is connecting to and monitoring the database through the Database Agent.
    CyberArkClick to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file. 
    Advanced OptionsSub-Collectors

    Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type.

    Note

    • All connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector. If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API.

    • You cannot convert a custom cluster collector to a standalone collector. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector. However, note that deleting the custom cluster collector will delete all its historical data.
    Connection PropertiesClick to add a new JDBC connection property or edit an existing property for relational databases.
    Exclude DatabasesThe databases that you want to exclude, separated by commas. 
    Monitor Operating SystemSee this page for more details, Configure the Database Agent to Monitor Server Hardware.

    User Permissions for Sybase

    For complete AppDynamics Database Visibility functionality, the monitoring user requires the permissions listed in the table below.

    Permission typePermission
    Role permission
    • sa_role
    • mon_role
    Select permission
    • master.dbo.monWaitEventInfo
    • master.dbo.sysconfigures
    • master.dbo.sysmonitors
    • master.dbo.monProcess
    • master.dbo.monProcessLookup
    • master.dbo.monProcessSQLText
    • master.dbo.monProcessProcedures
    Execute permission
    • sp_sysmon


    To create a new dedicated user for AppDynamics Database Visibility, you can use following sample user creation script. Before running the script, change "password" to a more secure value.

    exec  sp_addlogin  'DBMon_Agent_User', 'password', @defdb='master', @deflanguage='us_english', @fullname='DBMon_Agent_User monitoring account', @auth_mech = 'ANY'
    go
    exec  sp_locklogin  'DBMon_Agent_User', 'unlock'
    go
    exec  sp_role 'grant', 'mon_role', 'DBMon_Agent_User'
    go
    

    where DBMon_Agent_User is the user name under which you run the Database Visibility Agent.


    Also, the following configuration parameters must be set to 1 (true) in order to monitor the Sybase ASE database with AppDynamics Database Visibility: "enable monitoring", "wait event timing", "SQL batch capture", and "object lockwait timing". You should also set "max SQL text monitored" to at least 8192 (8kB).

    Here is an example of the commands required to configure these settings:

    sp_configure "enable monitoring", 1
    go
    sp_configure "wait event timing", 1
    go
    sp_configure "SQL batch capture", 1
    go
    sp_configure "object lockwait timing", 1
    go
    sp_configure "max SQL text monitored", 8192
    go
    

    If the value for "max SQL text monitored" was previously less than 4096, then increasing this setting will require that you restart the Sybase ASE instance.

    To monitor Sybase version 15.7 and later without the sa_role permission, run the following commands:

    use sybsystemprocs
    grant execute on sp_sysmon to mon_role

    If you choose to monitor Sybase using sp_sysmon, you may encounter the following errors:

    • Thread utilization is incorrectly reported. View the official report here.
    • Timeslice error in mmap64 or mda_flush_iostats. View the official report here.
    • No labels