Search all the documentation for "logs"
Sensitive Action Logging is an Enterprise feature that helps administrators detect suspicious user activity actions and investigate suspec
/monitor/sensitive-action-logging-enterprise-feature-293797915.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
- Enterprise Feature
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
account requires the following permissions: The account should have Log on as service rights. For information on how to assign these p
/monitor/permissions-required-for-the-redgate-monitor-service-accounts-239667406.html
environment. Configure extensions, logging, and other settings (steps 1-3) If you are unsure how to change the following configuration
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
instance so that the maximum number of user connections permitted is determined automatically by identifying the number of users currentl
on the target instance. Database instance error log entry Raised by: SQL Server, PostgreSQL, Oracle, MySQL, MongoDB. Ra
session, and will require up to 16MB of disk space for the session log files. Because only queries with a minimum duration of 5 seconds a
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
: 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
provider on Base Monitors running on Linux see Authenticating with OpenID Connect. By default, users log in to Redgate Monitor using the
/monitor/authenticating-with-active-directory-239667551.html
By default, users log in to Redgate Monitor using the passwords set by the administrator. Alternatively, administrators can set Redgate M
, /*RESTAPIResponse*/ response) { var event = request.body.data; gs.info("Redgate Monitor webhook log: " + JSON.stringify(event));
/monitor/integrating-with-servicenow-using-webhooks-239668090.html
space, potentially up to 450 MB a day. For a SQL Server Data Repository we recommend you set fixed autogrowth and transaction log size r
/monitor/redgate-monitor-database-requirements-239667402.html
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
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
(8 for Aurora) No CloudWatch Logs GetLogEvents https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogEven
/monitor/enabling-advanced-monitoring-for-rds-instances-239667800.html
Issues If you encounter an problems sending a test email, you can further identify issues in the Redgate Monitor logs. Authentication
/monitor/oauth-email-notifications-for-exchange-306941346.html
space for each of the components. We recommend having 1GB for each of the components to accommodate for the growth of application logs.
Redgate Monitor Website, logging in (RDP) to the machine that hosts it (localhost), Set the base monitor location as the new address of
/monitor/moving-the-base-monitor-to-a-different-machine-239668733.html
. These metrics represent key stages in the replication process. For more information about a particular metric, click the metric name.
-commit mode, the primary replica sends log records to the secondary replica, and then waits for the secondary to receive and harden these
