Skip to content

Google Search Console recommended fixes for SEO and performance #4228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jun 20, 2024
Merged

Google Search Console recommended fixes for SEO and performance #4228

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
22f6a20
Reduce image size to accelerate load time
kimsauce Jun 20, 2024
9198a09
Merge branch 'main' into improve-inp
kimsauce Jun 20, 2024
11dc946
Update docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-fireho…
kimsauce Jun 20, 2024
74f07d9
add 404 fixes
kimsauce Jun 20, 2024
2c56981
Merge branch 'improve-inp' of github.com:SumoLogic/sumologic-document…
kimsauce Jun 20, 2024
7daa79f
Update docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-fireho…
kimsauce Jun 20, 2024
c6c89e9
Update docs/send-data/reference-information/time-reference.md
kimsauce Jun 20, 2024
ddd63c7
Update docs/send-data/reference-information/time-reference.md
kimsauce Jun 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions cid-redirects.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,6 +330,7 @@
"/03Send-Data/Sources/04Reference-Information-for-Sources/Collecting-Multiline-Logs": "/docs/send-data/reference-information/collect-multiline-logs",
"/03Send-Data/Sources/04Reference-Information-for-Sources/Source-Log-Encoding": "/docs/send-data/reference-information/source-log-encoding",
"/03Send-Data/Sources/04Reference-Information-for-Sources/Timestamps,-Time-Zones,-Time-Ranges,-and-Date-Formats": "/docs/send-data/reference-information/time-reference",
"/03Send-Data/Sources/04Reference-Information-for-Sources/Timestamps%252C-Time-Zones%252C-Time-Ranges%252C-and-Date-Formats": "/docs/send-data/reference-information/time-reference",
"/03Send-Data/Sources/04Reference-Information-for-Sources/Using-Wildcards-in-Paths": "/docs/send-data/reference-information/use-wildcards-paths",
"/03Send-Data/Sumo_Logic_Distribution_for_OpenTelemetry": "/docs/send-data/opentelemetry-collector",
"/03Send-Data/Sumo_Logic_OpenTelemetry_Distribution": "/docs/send-data/opentelemetry-collector",
Expand Down Expand Up @@ -1019,6 +1020,7 @@
"/07Sumo-Logic-Apps/14Hosts_and_Operating_Systems/Host_Metrics/Host-Metrics-App-Dashboards": "/docs/integrations/hosts-operating-systems/host-metrics",
"/07Sumo-Logic-Apps/14Hosts_and_Operating_Systems/Linux_Performance": "/docs/integrations/hosts-operating-systems/linux-performance",
"/07Sumo-Logic-Apps/14Hosts_and_Operating_Systems/Linux": "/docs/integrations/hosts-operating-systems/linux",
"/07Sumo_Logic_Apps/14Hosts_and_Operating_Systems/Linux": "/docs/integrations/hosts-operating-systems/linux",
"/07Sumo-Logic-Apps/14Hosts_and_Operating_Systems/Linux/Collect-Logs-for-Linux": "/docs/integrations/hosts-operating-systems/linux",
"/07Sumo-Logic-Apps/14Hosts_and_Operating_Systems/Linux/Linux-App-Dashboards": "/docs/integrations/hosts-operating-systems/linux",
"/07Sumo-Logic-Apps/14Hosts_and_Operating_Systems/Linux/Suggested_Searches_for_Linux_OS": "/docs/integrations/hosts-operating-systems/linux",
Expand Down Expand Up @@ -1054,6 +1056,7 @@
"/07Sumo-Logic-Apps/18SAAS_and_Cloud_Apps/Istio/Install_the_Istio_App_and_view_the_Dashboards": "/docs/integrations/saas-cloud/istio",
"/docs/integrations/saas-cloud/microsoft-exchange-tracelogs": "/docs/integrations/saas-cloud/microsoft-exchange-trace-logs",
"/07Sumo-Logic-Apps/18SAAS_and_Cloud_Apps/Opsgenie": "/docs/integrations/saas-cloud/opsgenie",
"/docs/platform-services/automation-service/app-central/integrations/atlassian-oppsgenie": "/docs/integrations/saas-cloud/opsgenie",
"/07Sumo-Logic-Apps/18SAAS_and_Cloud_Apps/Opsgenie/Collect_Logs_for_Opsgenie": "/docs/integrations/saas-cloud/opsgenie",
"/07Sumo-Logic-Apps/18SAAS_and_Cloud_Apps/Opsgenie/Install_the_Opsgenie_App_and_view_the_Dashboards": "/docs/integrations/saas-cloud/opsgenie",
"/07Sumo-Logic-Apps/18SAAS_and_Cloud_Apps/PagerDuty_V1": "/docs/integrations/saas-cloud/pagerduty-v2",
Expand Down Expand Up @@ -1229,6 +1232,7 @@
"/07Sumo-Logic-Apps/24Web_Servers/Varnish/Collect_Varnish_Logs/Collect_Varnish_Logs_and_Metrics_for_Kubernetes_environments": "/docs/integrations/web-servers/varnish",
"/07Sumo-Logic-Apps/24Web_Servers/Varnish/Collect_Varnish_Logs/Collect_Varnish_Logs_and_Metrics_for_Non-Kubernetes_environments": "/docs/integrations/web-servers/varnish",
"/07Sumo-Logic-Apps/24Web_Servers/Varnish/Varnish_Alerts": "/docs/integrations/web-servers/varnish",
"/07Sumo-Logic-Apps/08App_Development/Varnish/Varnish_Alerts": "/docs/integrations/web-servers/varnish",
"/07Sumo-Logic-Apps/26Apps_for_Sumo": "/docs/integrations/sumo-apps",
"/07Sumo-Logic-Apps/26Apps_for_Sumo/Audit_App": "/docs/integrations/sumo-apps/audit",
"/07Sumo-Logic-Apps/26Apps_for_Sumo/Audit_App/Install-the-Audit-App-and-View-the-Dashboards": "/docs/integrations/sumo-apps/audit",
Expand Down Expand Up @@ -2844,6 +2848,7 @@
"/Manage/Collection/Collector-Upgrade-Best-Practices": "/docs/send-data/collection/upgrade-collectors",
"/Manage/Collection/Download_Customized_Collector_Configuration_File": "/docs/send-data/collection",
"/Manage/Collection/Pause-and-Resume-a-Source": "/docs/send-data/collection/pause-resume-source",
"/docs/send-data/collection/pause-and-resume-source": "/docs/send-data/collection/pause-resume-source",
"/Manage/Collection/Processing-Rules": "/docs/send-data/collection/processing-rules",
"/Manage/Collection/Processing-Rules/Create-a-Processing-Rule": "/docs/send-data/collection/processing-rules/create-processing-rule",
"/Manage/Collection/Processing-Rules/Data-Forwarding-Rules": "/docs/send-data/collection/processing-rules/data-forwarding-rules",
Expand Down Expand Up @@ -3202,9 +3207,11 @@
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/13Update_AWS_Observability_Stack": "/docs/observability/aws/deploy-use-aws-observability/update-aws-observability-stack",
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/01_About_AWS_Observability/AWS_Observability_Resources": "/docs/observability/aws/deploy-use-aws-observability/resources",
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/16AWS_Observability_-_Change_Log": "/docs/observability/aws/deploy-use-aws-observability/changelog",
"/Observability_Solution/AWS_Observability_Solution/01_Deploy_and_Use_AWS_Observability/AWS_Observability_-_Change_Log": "/docs/observability/aws/deploy-use-aws-observability/changelog",
"/Observability_Solution/AWS_Observability_Solution/03_Other_Configurations_and_Tools": "/docs/observability/aws/other-configurations-tools",
"/Observability_Solution/AWS_Observability_Solution/03_Other_Configurations_and_Tools/Add_a_New_AWS_Service_to_the_AWS_Observability_Explore_Hierarchy": "/docs/observability/aws/other-configurations-tools/add-new-aws-service",
"/Observability_Solution/AWS_Observability_Solution/03_Other_Configurations_and_Tools/Add_Fields_to_Existing_Host_Metrics_Sources": "/docs/observability/aws/other-configurations-tools/add-fields-to-existing-host-metrics-sources",
"/Observability_Solution/AWS_Observability_Solution/Add_Fields_to_Existing_Host_Metrics_Sources": "/docs/observability/aws/other-configurations-tools/add-fields-to-existing-host-metrics-sources",
"/Observability_Solution/AWS_Observability_Solution/03_Other_Configurations_and_Tools/Integrate_Control_Tower_Accounts_with_AWS_Observability": "/docs/observability/aws/other-configurations-tools/integrate-control-tower-accounts",
"/Observability_Solution/AWS_Observability_Solution/AWS_Observability_Apps": "/docs/observability/aws/integrations",
"/Observability_Solution/AWS_Observability_Solution/AWS_Observability_Apps/AWS_Classic_Load_Balancer": "/docs/observability/aws/integrations/aws-classic-load-balancer",
Expand Down Expand Up @@ -3472,6 +3479,7 @@
"/07Sumo-Logic-Apps/10Containers_and_Orchestration/Kubernetes/Install_the_Kubernetes_App_and_view_the_Dashboards": "/docs/integrations/containers-orchestration/kubernetes",
"/07Sumo-Logic-Apps/10Containers_and_Orchestration/Kubernetes/Install_the_Kubernetes_App,_Alerts,_and_view_the_Dashboards": "/docs/integrations/containers-orchestration/kubernetes",
"/07Sumo-Logic-Apps/10Containers_and_Orchestration/Kubernetes/Kubernetes_Alerts": "/docs/integrations/containers-orchestration/kubernetes",
"/07Sumo_Logic_Apps/10Containers_and_Orchestration/Kubernetes": "/docs/integrations/containers-orchestration/kubernetes",
"/07Sumo-Logic-Apps/12Databases": "/docs/integrations/databases",
"/07Sumo-Logic-Apps/12Databases/Couchbase/Install_the_Couchbase_Monitors,_App,_and_view_the_Dashboards": "/docs/integrations/databases/couchbase",
"/07Sumo_Logic_Apps/12Databases/MongoDB": "/docs/integrations/databases/mongodb",
Expand Down Expand Up @@ -3703,6 +3711,7 @@
"/Send-Data/Applications-and-Other-Data-Sources/Oracle/00Collect_Logs_for_Oracle": "/docs/send-data/collect-from-other-data-sources/collect-logs-oracle-cloud-infrastructure",
"/Send-Data/Applications-and-Other-Data-Sources/Threat-Intel-Quick-Analysis": "/docs/integrations/security-threat-detection/threat-intel-quick-analysis",
"/Send-Data/Applications-and-Other-Data-Sources/Threat-Intel-Quick-Analysis/Threat-Intel-FAQ": "/docs/integrations/security-threat-detection/threat-intel-quick-analysis",
"/Send-Data/Applications-and-Other-Data-Types/PCI-Compliance-for-Windows/Collecting-Logs-for-PCI-Compliance-for-Windows-App": "/docs/integrations/microsoft-azure/windows-json-pci-compliance",
"/Send-Data/Collect-from-Other-Data-Sources/Azure_Blob_Storage": "/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs",
"/Send-Data/Collect-from-Other-Data-Sources/Azure_Blob_Storage/Collect_Logs_from_Azure_Blob_Storage": "/docs/send-data/collect-from-other-data-sources/azure-blob-storage/block-blob/collect-logs",
"/Send-Data/Data-Types-and-Applications/Docker/01-Collect-Events-and-Statistics-for-the-Docker-App": "/docs/send-data/installed-collectors/sources/docker-sources",
Expand Down
81 changes: 21 additions & 60 deletions docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,13 +35,13 @@ The key difference between the sources is how they get metrics. The CloudWatch s

The benefits of a streaming source over a polling source include:

* No API throttling—The Kinesis Firehose for Metrics source doesn’t consume your AWS quota by making calls to the AWS CloudWatch APIs. This offers both efficiency and cost benefits.
* Automatic retry mechanism—Kinesis Firehose has an automatic retry mechanism for delivering metrics to the Kinesis Firehose for Metrics source. In the event of a glitch, the metrics are re-sent after the service is restored. If  that fails, Firehose stores all failed messages in a customer-owned S3 bucket for later recovery.
* Latency is the same for all metrics, whether new, old, sparse, or continuous. This is a benefit over the AWS CloudWatch Metrics source, which doesn’t reliably ingest old or sparsely published metrics.
* High resolution—The Kinesis Firehose streams all metrics at a 1-minute resolution. The AWS CloudWatch Metrics source supports scans as low as 1 minute, but that resolution can result in AWS account throttling and higher AWS bills
* **No API throttling**. The Kinesis Firehose for Metrics source doesn’t consume your AWS quota by making calls to the AWS CloudWatch APIs. This offers both efficiency and cost benefits.
* **Automatic retry mechanism**. Kinesis Firehose has an automatic retry mechanism for delivering metrics to the Kinesis Firehose for Metrics source. In the event of a glitch, the metrics are re-sent after the service is restored. If  that fails, Firehose stores all failed messages in a customer-owned S3 bucket for later recovery.
* **Consistent speed**. Latency is the same for all metrics, whether new, old, sparse, or continuous. This is a benefit over the AWS CloudWatch Metrics source, which doesn’t reliably ingest old or sparsely published metrics.
* **High resolution**. The Kinesis Firehose streams all metrics at a 1-minute resolution. The AWS CloudWatch Metrics source supports scans as low as 1 minute, but that resolution can result in AWS account throttling and higher AWS bills

:::note
The AWS CloudWatch Metrics source uses AWS’s [GetMetricStatistics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html) API and as a result, supports the `Unit` parameter. (When a request includes the `Unit` parameter, only metrics with the unit specified, for example, bytes, Microseconds, and so on, are reported. The Kinesis Firehose for Metrics does not currently support the `Unit` parameter.
The AWS CloudWatch Metrics source uses AWS’s [GetMetricStatistics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html) API and as a result, supports the `Unit` parameter. When a request includes the `Unit` parameter, only metrics with the unit specified, for example, bytes, Microseconds, and so on, are reported. The Kinesis Firehose for Metrics does not currently support the `Unit` parameter.
:::

## Step 1: Set up the source
Expand All @@ -51,12 +51,9 @@ In this step, you create the AWS Kinesis Firehose for Metrics source.
1. <!--Kanso [**Classic UI**](/docs/get-started/sumo-logic-ui/). Kanso--> In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <!--Kanso <br/>[**New UI**](/docs/get-started/sumo-logic-ui-new/). In the Sumo Logic top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**. Kanso-->
1. Click **Add Source** next to a Hosted Collector. 
1. Select **AWS Kinesis Firehose** for Metrics.

![kinesis-aws-source.png](/img/send-data/kinesis-aws-source.png)

1. Enter a **Name** for the source.
1. (Optional) Enter a **Description**.
1. For **Source Category**, enter any string to tag the output collected from this Source. Category metadata is stored in a searchable field called `_sourceCategory`.
1. For **Source Category**, enter any string to tag the output collected from this Source. Category metadata is stored in a searchable field called `_sourceCategory`.<br/><img src={useBaseUrl('img/send-data/kinesis-aws-source.png')} alt="kinesis-aws-source.png" style={{border: '1px solid gray'}} width="500"/>
1. For **AWS Access** of a Kinesis Metric source, the role requires `tag:GetResources` permission. The Kinesis Log source does not require permissions.
1. Click **Save**.

Expand All @@ -65,36 +62,20 @@ In this step, you create the AWS Kinesis Firehose for Metrics source.
In this step, you set up the AWS Metric Streams service to stream metrics to Kinesis Data Firehose using a [CloudFormation template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-whatis-concepts.html#w2ab1b5c15b7):

1. Go to **Services > CloudFormation** in the AWS console.
1. On the **CloudFormation > Stack** page, click **Create stack**.

![create-stack-icon.png](/img/send-data/create-stack-icon.png)

1. On the **CloudFormation > Stack** page, click **Create stack**.<br/> ![create-stack-icon.png](/img/send-data/create-stack-icon.png)
1. On the **Create stack** page:

1. Click **Template is ready**.
1. Click **Amazon S3 URL** and paste this URL into the URL field:  https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/KinesisFirehoseCWMetrics.template.yaml.
1. Click **Next**.

![step4a.png](/img/send-data/step4a.png)

1. Click **Next**.<br/> ![step4a.png](/img/send-data/step4a.png)
1. On the **Specify stack details** page:

* **Stack name**. Enter a name for the stack. 
* **Sumo Logic Kinesis Firehose Metrics Configuration.** (Required) Enter the URL of the AWS Kinesis Firehose for Metrics source.
* **Select Namespaces to collect AWS CloudWatch Metrics**. Enter a comma-delimited list of the namespaces from which you want to collect AWS CloudWatch metrics.
* **Failed Data AWS S3 Bucket Configuration**. Enter "Yes" to create a new bucket, or "No" if you want to use an existing bucket.
* **Failed Data AWS S3 Bucket Configuration**. Enter **Yes** to create a new bucket, or "No" if you want to use an existing bucket.
* **AWS S3 Bucket Name for Failed Data**. Provide the name of Amazon S3 bucket to create, or the name of an existing bucket in the current AWS Account.
* Click **Next**.

![stack.png](/img/send-data/stack.png)

1. Click **Create stack**.

![final-create-icon.png](/img/send-data/final-create-icon.png)

1. The AWS console displays the resources in the newly created stack.

![resources-in-stack.png](/img/send-data/resources-in-stack.png)
* Click **Next**.<br/> ![stack.png](/img/send-data/stack.png)
1. Click **Create stack**.<br/> ![final-create-icon.png](/img/send-data/final-create-icon.png)
1. The AWS console displays the resources in the newly created stack.<br/> ![resources-in-stack.png](/img/send-data/resources-in-stack.png)

## Filter CloudWatch metrics during ingestion

Expand All @@ -106,40 +87,20 @@ Inclusive and exclusive filters can’t be combined. You can choose namespaces t

### Include metrics by namespace

1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch.
1. Open the [CloudWatch console](https://console.aws.amazon.com/cloudwatch).
1. In the navigation pane, choose **Metrics**.
1. Under **Metrics**, select **Streams**.

![metric_stream_1.png](/img/send-data/metric_stream_1.png)

1. Select the metric stream and click **Edit**.

![metric-stream_2.png](/img/send-data/metric-stream_2.png)

1. Click **Selected namespaces**. 

![metric-stream_4.png](/img/send-data/metric-stream_4.png)

1. From the list of AWS namespaces, select the namespaces whose metrics you want to receive. In the screenshot below “S3” and “Billing” are selected.

![metric-stream-5.png](/img/send-data/metric-stream-5.png)

1. Click **Save changes** at the bottom of the page.

![metric-stream-6.png](/img/send-data/metric-stream-6.png)
1. Under **Metrics**, select **Streams**. <br/> ![metric_stream_1.png](/img/send-data/metric_stream_1.png)
1. Select the metric stream and click **Edit**.<br/> ![metric-stream_2.png](/img/send-data/metric-stream_2.png)
1. Click **Selected namespaces**. <br/>![metric-stream_4.png](/img/send-data/metric-stream_4.png)
1. From the list of AWS namespaces, select the namespaces whose metrics you want to receive. In the screenshot below “S3” and “Billing” are selected.<br/> ![metric-stream-5.png](/img/send-data/metric-stream-5.png)
1. Click **Save changes** at the bottom of the page.<br/> ![metric-stream-6.png](/img/send-data/metric-stream-6.png)

### Exclude metrics by namespace

1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch.
1. Open the [CloudWatch console](https://console.aws.amazon.com/cloudwatch).
1. In the navigation pane, choose **Metrics**.
1. Under **Metrics**, select **Streams**.

![metric_stream_1.png](/img/send-data/metric_stream_1.png)

1. Select the metric stream and click **Edit**.

![metric-stream_2.png](/img/send-data/metric-stream_2.png)

1. Under **Metrics**, select **Streams**.<br/> ![metric_stream_1.png](/img/send-data/metric_stream_1.png)
1. Select the metric stream and click **Edit**.<br/> ![metric-stream_2.png](/img/send-data/metric-stream_2.png)
1. Click **All metrics** and select the **Exclude metric namespaces** option.
1. From the list of AWS namespaces, select the namespaces whose metrics you do not want to receive.
1. Click **Save changes** at the bottom of the page.
Loading
Loading