{"meta":{"title":"Providing data to GitHub Support","intro":"Since GitHub Support doesn't have access to your environment, we sometimes require some additional information from you.","product":"GitHub Support","breadcrumbs":[{"href":"/en/enterprise-server@3.19/support","title":"GitHub Support"},{"href":"/en/enterprise-server@3.19/support/contacting-github-support","title":"Contacting support"},{"href":"/en/enterprise-server@3.19/support/contacting-github-support/providing-data-to-github-support","title":"Providing data"}],"documentType":"article"},"body":"# Providing data to GitHub Support\n\nSince GitHub Support doesn't have access to your environment, we sometimes require some additional information from you.\n\n## About diagnostic files and support bundles\n\nTo help you troubleshoot issues with a GitHub Enterprise Server instance in your environment, GitHub Support may request one or more types of data.\n\n| Data | File format | Description |\n| :---------------------- | :---------- | :------------------------------------------------------------------------------------- |\n| Diagnostic file | Plaintext | Contains information about the instance's settings and environment. |\n| Support bundle | Archive | Contains a diagnostics file and sanitized log files from the past two days by default. |\n| Extended support bundle | Archive | Contains a diagnostics file and sanitized log files from the past eight days. |\n\n## About log file sanitization\n\nAuthentication tokens, keys, and secrets are removed from log files in the following log directories contained within a support bundle or diagnostics file:\n\n* `alambic-logs`\n* `babeld-logs`\n* `codeload-logs`\n* `enterprise-manage-logs`\n* `github-logs`\n* `hookshot-logs`\n* `lfs-server-logs`\n* `semiotic-logs`\n* `task-dispatcher-logs`\n* `pages-logs`\n* `registry-logs`\n* `render-logs`\n* `svn-bridge-logs`\n\n## Creating and sharing diagnostic files\n\nDiagnostic files are an overview of a GitHub Enterprise Server instance's settings and environment that contain:\n\n* Client license information, including company name, expiration date, and number of user licenses\n* Version numbers and SHAs\n* VM architecture\n* Host name, private mode, SSL settings\n* Load and process listings\n* Network settings\n* Authentication method and details\n* Number of repositories, users, and other installation data\n\nYou can download the diagnostics for your instance from the Management Console or by running the `ghe-diagnostics` command-line utility.\n\n### Creating a diagnostic file from the Management Console\n\nYou can create a diagnostic file from the Management Console if you don't currently have SSH access.\n\n1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .\n2. If you're not already on the \"Site admin\" page, in the upper-left corner, click **Site admin**.\n3. In the \" Site admin\" sidebar, click **Management Console**.\n4. If you have created multiple Management Console user accounts, select **Root site admin** or **Management Console user**. For more information about Management Console user accounts see, [Managing access to the Management Console](/en/enterprise-server@3.19/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console).\n5. Type your Management Console credentials. Then click **Continue**.\n6. In the top navigation bar, click **Support**.\n\n \n7. Click **Download diagnostics info**.\n\n### Creating a diagnostic file using SSH\n\nYou can use this method without signing into the Management Console.\n\nUse the [ghe-diagnostics](/en/enterprise-server@3.19/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance.\n\n```shell\nssh -p122 admin@HOSTNAME -- 'ghe-diagnostics' > diagnostics.txt\n```\n\n## Creating and sharing support bundles\n\nAfter you submit your support request, we may ask you to share a support bundle with our team. The support bundle is a gzip-compressed tar archive that includes diagnostics and important logs from your instance, such as:\n\n* Authentication-related logs that may be helpful when troubleshooting authentication errors, or configuring LDAP, CAS, or SAML\n\n* Management Console log\n\n* `github-logs/exceptions.log`: Information about 500 errors encountered on the site\n\n* `github-logs/audit.log`: GitHub Enterprise Server audit logs\n\n* `babeld-logs/babeld.log`: Git proxy logs\n\n* `system-logs/haproxy.log`: HAProxy logs\n\n* `elasticsearch-logs/github-enterprise.log`: Elasticsearch logs\n\n* `configuration-logs/`: GitHub Enterprise Server configuration logs\n\n* `collectd/logs/collectd.log`: Collectd logs\n\n* `mail-logs/mail.log`: SMTP email delivery logs\n\nFor more information, see [Audit log for an enterprise](/en/enterprise-server@3.19/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise).\n\nSupport bundles include logs from the past two days by default. You can specify an exact duration in days. To provide logs from the past eight days, you can download an extended support bundle. For more information, see [Creating and sharing extended support bundles](#creating-and-sharing-extended-support-bundles).\n\n> \\[!TIP]\n> When you contact GitHub Support, you'll be sent a confirmation email that will contain a ticket reference link. If GitHub Support asks you to upload a support bundle, you can use the ticket reference link to upload the support bundle.\n\n### Creating a support bundle from the Management Console\n\nYou can use these steps to create and share a support bundle if you can access the web-based Management Console and have outbound internet access.\n\n1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .\n2. If you're not already on the \"Site admin\" page, in the upper-left corner, click **Site admin**.\n3. In the \" Site admin\" sidebar, click **Management Console**.\n4. If you have created multiple Management Console user accounts, select **Root site admin** or **Management Console user**. For more information about Management Console user accounts see, [Managing access to the Management Console](/en/enterprise-server@3.19/admin/configuration/administering-your-instance-from-the-management-console/managing-access-to-the-management-console).\n5. Type your Management Console credentials. Then click **Continue**.\n6. In the top navigation bar, click **Support**.\n\n \n7. Click **Download support bundle**.\n8. If a support engineer has given you an upload link for your support bundle, use this link. Otherwise, visit and sign in (if prompted) to an enterprise account that is entitled to support.\n9. Visit and upload your support bundle.\n\n### Creating a support bundle using SSH\n\nYou can use these steps to create and share a support bundle if you have SSH access to your GitHub Enterprise Server instance and have outbound internet access.\n\n> \\[!NOTE]\n> If your GitHub Enterprise Server instance is in a geo-replication configuration, or if your instance is a cluster, you should use the `ghe-cluster-support-bundle` command to retrieve the support bundle. For more information, see [Command-line utilities](/en/enterprise-server@3.19/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-cluster-support-bundle).\n\n1. Download the support bundle via SSH:\n\n ```shell\n ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz\n ```\n\n For more information about the `ghe-support-bundle` command, see [Command-line utilities](/en/enterprise-server@3.19/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-support-bundle).\n2. If a support engineer has given you an upload link for your support bundle, use this link. Otherwise, visit and sign in (if prompted) to an enterprise account that is entitled to support.\n3. Visit and upload your support bundle.\n\n### Uploading a support bundle using your enterprise account\n\n1. Navigate to GitHub Enterprise Cloud.\n2. In the top-right corner of GitHub, click your profile picture.\n3. Depending on your environment, click **Enterprise**, or click **Enterprises** then click the enterprise you want to view.\n4. At the top of the page, click **Settings**.\n5. Under ** Settings**, click **License**.\n6. Under \"GitHub Enterprise Help\", click **Upload a support bundle**.\n\n \n7. Under \"Select an enterprise account\", use the drop-down menu to select the support bundle's associated account.\n8. Under \"Upload a support bundle for GitHub Enterprise Support\", to select your support bundle, click **Choose file**, or drag your support bundle file onto **Choose file**.\n9. Click **Upload**.\n\n### Uploading a support bundle directly using SSH\n\nYou can directly upload a support bundle to our server if:\n\n* You have SSH access to your GitHub Enterprise Server instance.\n* Outbound HTTPS connections over TCP port 443 are allowed from your GitHub Enterprise Server instance to *enterprise-bundles.github.com* and *esbtoolsproduction.blob.core.windows.net*.\n\n1. Upload the bundle to our support bundle server:\n\n ```shell\n ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u'\n ```\n\n## Creating and sharing extended support bundles\n\nSupport bundles include logs from the past two days by default, while *extended* support bundles include logs from the past eight days. If the events that GitHub Support is investigating occurred more than two days ago, we may ask you to share an extended support bundle. You will need SSH access to download an extended bundle - you cannot download an extended bundle from the Management Console.\n\nTo prevent bundles from becoming too large, bundles only contain logs that haven't been rotated and compressed. Log rotation on GitHub Enterprise Server happens at various frequencies (daily or weekly) for different log files, depending on how large we expect the logs to be.\n\n### Creating an extended support bundle using SSH\n\nYou can use these steps to create and share an extended support bundle if you have SSH access to your GitHub Enterprise Server instance and you have outbound internet access.\n\n1. Download the extended support bundle via SSH by adding the `-x` flag to the `ghe-support-bundle` command:\n\n ```shell\n ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o -x' > support-bundle.tgz\n ```\n\n2. If a support engineer has given you an upload link for your support bundle, use this link. Otherwise, visit and sign in (if prompted) to an enterprise account that is entitled to support.\n\n3. Visit and upload your support bundle.\n\n### Uploading an extended support bundle directly using SSH\n\nYou can directly upload a support bundle to our server if:\n\n* You have SSH access to your GitHub Enterprise Server instance.\n* Outbound HTTPS connections over TCP port 443 are allowed from your GitHub Enterprise Server instance to *enterprise-bundles.github.com* and *esbtoolsproduction.blob.core.windows.net*.\n\n1. Upload the bundle to our support bundle server:\n\n ```shell\n ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u -x'\n ```\n\n## Further reading\n\n* [About GitHub Support](/en/enterprise-server@3.19/support/learning-about-github-support/about-github-support)\n* [Generating a Health Check for your enterprise](/en/enterprise-server@3.20/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)"}