Hack week 2025: remove unneeded FBV instances (21) (#54014)
This commit is contained in:
@@ -52,8 +52,6 @@ settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-all
|
||||
1. When the test email succeeds, under the "Settings" sidebar, click **Save settings**.
|
||||
{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
|
||||
|
||||
{% ifversion require-tls-for-smtp %}
|
||||
|
||||
## Enforcing TLS for SMTP connections
|
||||
|
||||
You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
|
||||
@@ -63,7 +61,6 @@ You can enforce TLS encryption for all incoming SMTP connections, which can help
|
||||
|
||||

|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
{% endif %}
|
||||
|
||||
## Configuring DNS and firewall settings to allow incoming emails
|
||||
|
||||
|
||||
@@ -30,7 +30,7 @@ For more information about the specific events that you can access via the audit
|
||||
|
||||
Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](https://en.wikipedia.org/wiki/Unix_time).
|
||||
|
||||
{% ifversion read-audit-scope %}You can use the `read:audit_log` scope to access the audit log via the API.{% endif %}
|
||||
You can use the `read:audit_log` scope to access the audit log via the API.
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ redirect_from:
|
||||
|
||||
{% data reusables.enterprise.about-ha %} For more information, see [AUTOTITLE](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration).
|
||||
|
||||
After you configure high availability, you can proactively ensure redundancy by monitoring the overall health of replication and the status of each of your instance's replica nodes. You can use command-line utilities on the instance, an overview dashboard, {% ifversion replication-management-api %}the instance's REST API, {% endif %}or a remote monitoring system such as Nagios.
|
||||
After you configure high availability, you can proactively ensure redundancy by monitoring the overall health of replication and the status of each of your instance's replica nodes. You can use command-line utilities on the instance, an overview dashboard, the instance's REST API, or a remote monitoring system such as Nagios.
|
||||
|
||||
With high availability, your instance uses several approaches to replicate data between primary and replica nodes. Database services that support a native replication mechanism, such as MySQL, replicate using the service's native mechanism. Other services, such as Git repositories, replicate using a custom mechanism developed for {% data variables.product.product_name %}, or using platform tools like rsync.
|
||||
|
||||
@@ -40,14 +40,10 @@ You can monitor replication status on your instance using the `gh es` extension
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion replication-management-api %}
|
||||
|
||||
## Monitoring replication using the REST API
|
||||
|
||||
You can monitor replication status on your instance using the REST API. For more information, see [Manage {% data variables.product.product_name %}](/rest/enterprise-admin/manage-ghes#list-the-status-of-services-running-on-all-replica-nodes) in the REST API documentation.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Monitoring replication from a remote system
|
||||
|
||||
Output from the `ghe-repl-status` command-line utility conforms to the expectations of Nagios' check_by_ssh plugin. For more information, see [AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repl-status).
|
||||
|
||||
Reference in New Issue
Block a user