Search all the documentation for "logs"
instance so that the maximum number of user connections permitted is determined automatically by identifying the number of users currentl
: connection memory SQL Server: lock memory SQL Server: optimizer memory SQL Server: buffer cache memory SQL Server: granted workspace
/monitor/sql-server-on-linux-metrics-and-alerts-239667983.html
Log files collect information about Redgate Monitor while you are using it. These files are useful if you have a problem. To view the log
/monitor/viewing-component-information-and-log-files-239668682.html
connected to the server process Username Name of the user logged in to the backend by this server process Address, Port IP address or
/monitor/user-processes-error-log-and-databases-239668464.html
If Redgate Monitor is configured to authenticate users with Active Directory or OpenID Connect and you're unable to log in, check that:
/monitor/can-t-log-in-to-redgate-monitor-with-active-directory-or-openid-connect-239668901.html
. SQL Server: you're running a version of SQL Server 2008 susceptible to a bug that causes high CPU usage when reading error logs. Postg
SQL Server: optimizer memory SQL Server: buffer cache memory SQL Server: log pool memory SQL Server: maximum workspace memory SQL Se
/monitor/azure-sql-managed-instance-metrics-and-alerts-239667982.html
Data I/O percent Log I/O percent Memory used percent User connections SQL Server: total memory SQL Server: target memory SQL Serve
/monitor/azure-sql-database-metrics-and-alerts-239667989.html
this information on the Server Overview page. SQL Server Errors Redgate Monitor captures entries in the SQL Server error log and displa
/monitor/how-redgate-monitor-collects-metric-and-alert-data-239667910.html
memory SQL Server: buffer cache memory SQL Server: granted workspace memory SQL Server: log pool memory SQL Server: reserved server m
/monitor/sql-server-on-amazon-rds-metrics-and-alerts-239667978.html
specific choices which are suitable based on your own assessment of your particular environment's needs. Configure extensions, logging
/monitor/guidance-for-postgresql-configuration-choices-259621636.html
environment. Configure extensions, logging, and other settings (steps 1-3) If you are unsure how to change the following configuration
Database instance error log entry Instance unreachable Long-running query Host alerts Disk space Internal Redgate Monitor error
/monitor/oracle-on-amazon-rds-metrics-and-alerts-289047661.html
The following is a list of alerts available for Oracle on Linux: Oracle specific alerts Database instance error log entry Instanc
Edit credentials Remove servers Show logs Set maintenance windows Suspend monitoring Select servers Can't: Add servers to mo
instance error log entry Instance unreachable Long-running query Host alerts Disk space Internal Redgate Monitor error (host) M
/monitor/mysql-on-amazon-rds-metrics-and-alerts-289047657.html
By default, users log in to Redgate Monitor using the passwords set by the administrator. Alternatively, administrators can set Redgate M
/monitor/authenticating-with-active-directory-239667551.html
written / sec Alerts The following is a list of alerts available for MongoDB on Linux: MongoDB specific alerts Database in
By default, users log in to Redgate Monitor using the passwords set by the administrator. Alternatively, administrators can set Redgate M
is specified incorrectly, the Base Monitor service will fail to start. A full reason will be logged to the Red Gate section of t
/monitor/monitoring-servers-without-sysadmin-permissions-239667635.html
) Instance unreachable Low cache hit ratio Server log entry Replica role change Host machine alerts Disk average read time Disk a
/monitor/postgresql-on-amazon-rds-metrics-and-alerts-239667985.html
is a list of alerts available for MySQL on Linux: MySQL specific alerts Database instance error log entry Instance unreachable L
replicas and metrics such as log growth, the size for the send and redo queues, length of transaction delays and more. See: Availability
recommends only logging failed login attempts via the SQL Server Errorlog. This template assumes that logging successful attempts would c
/monitor/cis-microsoft-sql-server-2022-benchmark-266141714.html
. These metrics represent key stages in the replication process. For more information about a particular metric, click the metric name.
