Merge branch 'main' into otel-usecase

Author: jpipkin1

.clabot

@@ -143,7 +143,18 @@
     "aneeshep",
     "dmolenda-sumo",
     "Gourav2906",
-    "parth-sumo"
+    "parth-sumo",
+    "rishav-sumo-dev",
+    "cameroneckles",
+    "akhil-sumologic",
+    "paultobiasumo",
+    "atishya-22",
+    "kaliserichmond",
+    "ccressent",
+    "draval-sumo",
+    "jbaldo",
+    "prateek-sumologic",
+    "mafsumo"
   ],
   "message": "Thank you for your contribution! As this is an open source project, we require contributors to sign our Contributor License Agreement and do not have yours on file. To proceed with your PR, please [sign your name here](https://forms.gle/YgLddrckeJaCdZYA6) and we'll add you to our approved list of contributors.",
   "label": "cla-signed",

.github/CODEOWNERS

@@ -1,11 +1,14 @@
 # Default owners for everything in the repo.
-* @stacykor @kimsauce @jpipkin1 @JV0812
+* @kimsauce @jpipkin1 @JV0812 @mafsumo
 
 # Owners of all files in the `/docs` directory and its subdirectories.
-/docs/   @kimsauce @stacykor @jpipkin1 @JV0812
+/docs/   @kimsauce @jpipkin1 @JV0812 @mafsumo
+
+# Owners of all files in the `/docs/send-data/kubernetes` directory.
+/docs/send-data/kubernetes/  @SumoLogic/open-source-collection-team @kimsauce @jpipkin1 @JV0812 @mafsumo
 
 # Owners of all files in the `/docs/send-data/opentelemetry-collector` directory and its subdirectories.
-/docs/send-data/opentelemetry-collector/  @SumoLogic/open-source-collection-team @kimsauce @stacykor @jpipkin1 @JV0812
+/docs/send-data/opentelemetry-collector/  @SumoLogic/open-source-collection-team @kimsauce @mafsumo @JV0812
 
 # GitHub workflow owners
 /.github/workflows/ @SumoLogic/open-source-collection-team @kimsauce

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,20 +1,16 @@
-## PLEASE READ
-
-Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run `yarn install`. This does not apply to [direct page edits](https://help.sumologic.com/docs/contributing/edit-doc/#minor-edits).
-
-- [ ] Yes, I've run `yarn install`
-- [ ] No, does not apply to me
-
 ## Purpose of this pull request
 
-This pull request...
+This pull request... <!-- brief description here -->
 
-<!-- Enter the GitHub Issue number or the Jira project and number (e.g., SUMO-12345) -->
 
-## Select the type of change:
-<!-- What types of changes does your code introduce? Select the checkbox after creating the PR. -->
+## Select the type of change
+<!-- What types of changes does your code introduce? Select the checkbox after clicking "Create pull request" button. -->
 
-- [ ] Minor Changes - Typos, formatting, slight revisions, .clabot
+- [ ] Minor Changes - Typos, formatting, slight revisions
 - [ ] Update Content - Revisions, updating sections
 - [ ] New Content - New features, sections, pages, tutorials
-- [ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)
+- [ ] Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)
+
+## Ticket (if applicable)
+
+<!-- enter your Jira, Asana, or GitHub ticket number -->

.github/workflows/pr.yml

@@ -5,6 +5,8 @@ on:
       branches:
         - main
     merge_group:
+      types:
+        - checks_requested
 
 jobs:
     build-and-deploy:
@@ -38,5 +40,5 @@ jobs:
         name: Check spelling
         with:
           skip: "*.svg,*.js,*.map,*.css,*.scss"
-          ignore_words_list: "aks,atleast,cros,ddress,fiel,ist,nd,ot,pullrequest,ser,shttp,wast,fo,seldomly,delt,cruzer,plack,secur,te"
+          ignore_words_list: "aks,atleast,cros,ddress,fiel,ist,nd,ot,pullrequest,ser,shttp,wast,fo,seldomly,delt,cruzer,plack,secur,te,nginx,Nginx,notin"
           path: docs

blog-collector/2015/12-31.md

@@ -1,39 +1,40 @@
 ---
 title: 2015 Archive
-hide_table_of_contents: false
-image: /img/sumo-square.png
+image: https://help.sumologic.com/img/sumo-square.png
 ---
 
 This is an archive of 2015 Collector Release Notes. The current Collector Release Notes are [here](/release-notes-collector).
 
+To view the full archive, [click here](/release-notes-collector/archive).
+
+<!--truncate-->
+
 ---
 ### December 18, 2015 (i19.137-15)
 
 This Collector software minor upgrade contains two important bug fixes. Upgrading Collectors is required to resolve these issues.
 
-**Bug fix | **Fixed an issue that could result in a large number of messages being written into the Collector log file when using Syslog UDP Sources.
+**Bug fix |** Fixed an issue that could result in a large number of messages being written into the Collector log file when using Syslog UDP Sources.
 
-**Bug fix | **Improved error messages during unattended (quiet) installation.
+**Bug fix |** Improved error messages during unattended (quiet) installation.
 
 ---
 ### December 8, 2015 (i19.137)
 
-**New feature | **We're proud to announce an improved Collector installer. New features include:
-
-
+**New feature |** We're proud to announce an improved Collector installer. New features include:
 
 * A new configuration file, named user.properties.
 * Support for Advanced settings (Proxy support, Source setup, etc.)
 * Improved documentation and failure handling within the installer.
 * The Windows Collector Installer is now signed with Microsoft Authenticode to verify that it comes fromSumo Logic.
 
-**New feature | **We have new options for data forwarding, including data forwarding from Installed Collectors.
+**New feature |** We have new options for data forwarding, including data forwarding from Installed Collectors.
 
-**Bug fix | **Passwords containing the # symbol are now supported for Windows users specified in the "Run As" field.
+**Bug fix |** Passwords containing the # symbol are now supported for Windows users specified in the "Run As" field.
 
-**Bug fix | **An issue that could cause Collectors to be incorrectly marked as Offline in the UI has been fixed.
+**Bug fix |** An issue that could cause Collectors to be incorrectly marked as Offline in the UI has been fixed.
 
-**Bug fix | **An issue that could cause Collectors to go Offline for a few seconds after receiving a malformed message from the service has been resolved.
+**Bug fix |** An issue that could cause Collectors to go Offline for a few seconds after receiving a malformed message from the service has been resolved.
 
 ---
 ### August 31, 2015 (i19.127)
@@ -45,11 +46,11 @@ This Collector software update contains two important bug fixes. Upgrading Colle
 
 ---
 ### June 13, 2015 (i19.119)
-Collector software was updated to support our new Onboarding experience. These update don't affect existing Collectors.
+Collector software was updated to support our new Onboarding experience. These update do not affect existing Collectors.
 
 ---
 ### May 26, 2015 (i19.118)
-**New feature | **Local Event Tracing (ETW) Support with Windows Event Channels. This update to the Local Windows Event Log Source allows you to specify the Windows Custom Event Channels you'd like to collect from. This option replaces the "Others" option that previously collected whatever events Sumo Logic could find on a Collector. Learn more about Windows Events Channels.
+**New feature |** Local Event Tracing (ETW) Support with Windows Event Channels. This update to the Local Windows Event Log Source allows you to specify the Windows Custom Event Channels you'd like to collect from. This option replaces the "Others" option that previously collected whatever events Sumo Logic could find on a Collector. Learn more about Windows Events Channels.
 
 ---
 ### April 25, 2015 (i19.115)
@@ -64,12 +65,12 @@ JRE 7 is now included in the Collector package and is installed automatically du
 
 --
 ### February 28, 2015 (i19.110)
-**Change log | **When collecting Windows Events, if event record IDs were greater than four billion, the Collector could hang on a record ID, causing it to re-collect that record in a loop, causing ingestion delays of more recent events.This issue was due to a 32bit limitation that affected 64bit Collectors. This version of Collector software addresses this limitation, so events with record numbers greater than four billion are properly collected.
+**Changelog |** When collecting Windows Events, if event record IDs were greater than four billion, the Collector could hang on a record ID, causing it to re-collect that record in a loop, causing ingestion delays of more recent events.This issue was due to a 32bit limitation that affected 64bit Collectors. This version of Collector software addresses this limitation, so events with record numbers greater than four billion are properly collected.
 
-**New feature | **UTF-16 encoding is now supported for Local File Sources.
+**New feature |** UTF-16 encoding is now supported for Local File Sources.
 
 ---
 ### February 4, 2015 (i19.108)
 **New Feature |** Support for Local Configuration Management. With Local Configuration Management, you can set up and manage all Sources that you’ve set up on a Local Collector using a file that describes each Source’s parameters. The config file then remains on the Collector, and is checked nearly constantly for any changes, making updating Sources a quick process.
 
-**New Feature | **Support for CPU usage Target.You can now choose to set a CPU Target to limit the amount of CPU processing a Collector uses. This option is applied only to for Local and Remote file Sources.
+**New Feature |** Support for CPU usage Target.You can now choose to set a CPU Target to limit the amount of CPU processing a Collector uses. This option is applied only to for Local and Remote file Sources.

blog-collector/2016/12-31.md

@@ -1,11 +1,13 @@
 ---
 title: 2016 Archive
-hide_table_of_contents: false
-image: /img/sumo-square.png
+image: https://help.sumologic.com/img/sumo-square.png
 ---
 
 This is an archive of 2016 Collector Release Notes. The current Collector Release Notes are [here](/release-notes-collector).
 
+To view the full archive, [click here](/release-notes-collector/archive).
+
+<!--truncate-->
 
 ---
 ### November 28, 2016 (19.170-24)
@@ -27,33 +29,27 @@ This is an archive of 2016 Collector Release Notes. The current Collector Releas
 ---
 ### October 17, 2016 (19.170-14)
 
-**Enhanced file system security for installed Collectors.** The log cache and configuration files for an installed Collector can contain sensitive information. To address possible security issues associated with the cache and configuration files, this Collector release introduces an enhanced file system security mode for Collector installation. The enhanced security mode protects the Collector installation folder at the file system level. When enabled, only the users in the **sumologic_collector** group have access to the Collector folder. See [Enhanced File System Security for Installed Collectors](/docs/send-data/installed-collectors/collector-installation-reference/enhanced-file-system-security-installed-collectors).
-
-**Host key verification for Remote File Source.** The Sumo Logic Collector can optionally verify the RSA fingerprint for a remote server against a list of known hosts. When host verification is enabled, the Collector collects from a Remote File Source only if the remote host fingerprint is whitelisted in a **known_hosts** file. See Enable Collector Remote Host Key Verification.
-
-**Cipher formats for Remote Files Sources.** Added support for hmac-sha2-256 and hmac-sha2-512 cipher formats for Remote File Sources.
-
-**RPM and Debian installations.** RPM and Debian Collector installations now support **user.properties** parameters, with backwards compatibility for **/etc/sumo.conf** parameters. See [user.properties](/docs/send-data/installed-collectors/collector-installation-reference/user-properties).
+**Enhanced file system security for installed Collectors**. The log cache and configuration files for an installed Collector can contain sensitive information. To address possible security issues associated with the cache and configuration files, this Collector release introduces an enhanced file system security mode for Collector installation. The enhanced security mode protects the Collector installation folder at the file system level. When enabled, only the users in the **sumologic_collector** group have access to the Collector folder. See [Enhanced File System Security for Installed Collectors](/docs/send-data/installed-collectors/collector-installation-reference/enhanced-file-system-security-installed-collectors).
 
-**Other issues.**
+**Host key verification for Remote File Source**. The Sumo Logic Collector can optionally verify the RSA fingerprint for a remote server against a list of known hosts. When host verification is enabled, the Collector collects from a Remote File Source only if the remote host fingerprint is whitelisted in a **known_hosts** file. See Enable Collector Remote Host Key Verification.
 
+**Cipher formats for Remote Files Sources**. Added support for hmac-sha2-256 and hmac-sha2-512 cipher formats for Remote File Sources.
 
+**RPM and Debian installations**. RPM and Debian Collector installations now support **user.properties** parameters, with backwards compatibility for **/etc/sumo.conf** parameters. See [user.properties](/docs/send-data/installed-collectors/collector-installation-reference/user-properties).
 
+**Other issues**.
 * Fixed an issue where upgrading a collector using the Collector Installer could lead to missing JRE.
 * Syslog source host resolution now use the provided Source host only for locally-emitted events, instead of both remote and local events.
 * Graphite source now supports metrics from the CollectD UDP write_graphite module.
 * Fixed an issue that could cause multi-line messages at the end of a text file to be split incorrectly when there is no trailing newline
 
-**Change Log.**
-
-
-
+**Changelog**.
 * Username and password registration support is removed from the Collector Installer. Instead, use Access Id and Access Key to register a new Collector.
 
 ---
 ### September 23, 2016
 
-**Deprecation of Username/Password for Collector and Source API Authentication.** As of September 28, username and password will no longer be supported for API authentication. The API topics have been updated accordingly. See [API Authentication](/docs/api/getting-started#authentication).
+**Deprecation of Username/Password for Collector and Source API Authentication**. As of September 28, username and password will no longer be supported for API authentication. The API topics have been updated accordingly. See [API Authentication](/docs/api/getting-started#authentication).
 
 ---
 ### August 26, 2016 (19.162-17)
@@ -99,31 +95,31 @@ This version contains the following improvements:
 * Significant update to the Remote Windows Event Log Source:
     * Local and Remote Windows Event Sources now both use the native Windows Event API directly. WMI is no longer used for the Remote Source. This provides significant performance gains, and greatly simplifies configuration.
 
-**Bug Fix |** Issues that sometimes caused Local Windows Event Sources to prevent a Collector from shutting down cleanly are fixed.
+**Bug Fix**. Issues that sometimes caused Local Windows Event Sources to prevent a Collector from shutting down cleanly are fixed.
 
-**Bug Fix |** Fixed a Docker Source bug where the Collector is unable to listen on new containers.
+**Bug Fix**. Fixed a Docker Source bug where the Collector is unable to listen on new containers.
 
-**Change Log | **The collector no longer creates the installerSources directory on installation.
+**Changelog**. The collector no longer creates the installerSources directory on installation.
 
 ---
 ### April 5, 2016 (19.144-9)
 
-**Bug Fix |** Issues that sometimes caused Local Windows Event Sources to prevent a Collector from shutting down cleanly are fixed.
+* **Bug Fix**. Issues that sometimes caused Local Windows Event Sources to prevent a Collector from shutting down cleanly are fixed.
 
-**Bug Fix |** A race condition that could cause the collector's HTTP transmitters to hang is fixed.
+* **Bug Fix**. A race condition that could cause the collector's HTTP transmitters to hang is fixed.
 
-**Bug Fix | **An issue that caused a Collector to catch an infinite loop when trying to request Docker logs/stats from a non-existent container is fixed.
+* **Bug Fix**. An issue that caused a Collector to catch an infinite loop when trying to request Docker logs/stats from a non-existent container is fixed.
 
-**Bug Fix | **A race condition on Docker client causing a Collector to stop collecting from all containers is fixed.
+* **Bug Fix**. A race condition on Docker client causing a Collector to stop collecting from all containers is fixed.
 
-**Bug Fix | **Docker Log Sources properly apply [Processing Rules](/docs/send-data/collection/processing-rules).
+* **Bug Fix**. Docker Log Sources properly apply [Processing Rules](/docs/send-data/collection/processing-rules).
 
-**Bug Fix | **Some Docker Log Sources missed the first few messages for newly started containers. This has been resolved.
+* **Bug Fix**. Some Docker Log Sources missed the first few messages for newly started containers. This has been resolved.
 
 ---
 ### March 2, 2016 (i19.144-6)
 
-**Bug Fix | **Changed the Collector's default TLS settings to avoid connectivity issues with Online Certificate Status Protocol (OCSP) endpoints, which were reported by some users.OCSP) endpoints, which were reported by some users.
+* **Bug Fix**. Changed the Collector's default TLS settings to avoid connectivity issues with Online Certificate Status Protocol (OCSP) endpoints, which were reported by some users.OCSP) endpoints, which were reported by some users.
 
 ---
 ### February 25, 2016 (i19.144-5)
@@ -135,13 +131,15 @@ This version contains the following improvements:
 * Removed a memory leak in the Syslog Source that could cause large memory utilization when receiving TCP data from a very large number of connections.
 * Improved code quality.
 
-**Deprecation warning | **The flag providing access to a legacy Microsoft Event Logging API (local.win.event.collection.flag) is now deprecated.
+:::warning Deprecation warning
+The flag providing access to a legacy Microsoft Event Logging API (`local.win.event.collection.flag`) is now deprecated.
+:::
 
 With the improvements we've introduced in this release, we have consistently observed superior performance by removing this flag, even in single-core scenarios. During the next release of Collector software, this flag will be removed.
 
 ---
 ### January 22, 2016 (i19.137-20)
 
-**Bug fix | **Fixed a bug that could cause the Collector to miss events from Docker environments with more than eight running containers.
+* **Bug fix**. Fixed a bug that could cause the Collector to miss events from Docker environments with more than eight running containers.
 
-**Bug fix | **Fixed a bug that could cause the Collector to miss events from Docker environments when the Collector experiences connection issues to Docker.
+* **Bug fix**. Fixed a bug that could cause the Collector to miss events from Docker environments when the Collector experiences connection issues to Docker.