diff --git a/blog-cse/2024/12-31.md b/blog-cse/2024/12-31.md index 1a9602edc9..814c8da551 100644 --- a/blog-cse/2024/12-31.md +++ b/blog-cse/2024/12-31.md @@ -76,7 +76,7 @@ This content release: - Alert Logic - Google G Suite Alert Center - Microsoft Defender Advanced Hunting - - Azure Provisioning, Alert, ResourceHealth, and ServiceHealth events + - Azure Provisioning, Alert, ResourceHealth, and Service Account events Changes are enumerated below. diff --git a/docs/api/health-events.md b/docs/api/health-events.md index bf4334e663..8f408aca79 100644 --- a/docs/api/health-events.md +++ b/docs/api/health-events.md @@ -1,8 +1,8 @@ --- -id: health-events -title: Health Events Management APIs -sidebar_label: Health Events -description: Use HTTP endpoints to view your account's health events. +id: account-events +title: Account Events Management APIs +sidebar_label: Account Events +description: Use HTTP endpoints to view your account's account events. --- import useBaseUrl from '@docusaurus/useBaseUrl'; @@ -11,7 +11,7 @@ import ApiRoles from '../reuse/api-roles.md'; Thumbnail icon -The [Health Events](/docs/manage/health-events) Management API allows you to view the health of your Collectors and Sources from HTTP endpoints. +The [Account Events](/docs/manage/account-events) Management API allows you to view the health of your Collectors and Sources from HTTP endpoints. ## Documentation @@ -19,15 +19,15 @@ The [Health Events](/docs/manage/health-events) Management API allows you to vie | Deployment | Documentation URL | |:------------|:------------------------------------------------------| -| AU | https://api.au.sumologic.com/docs/#tag/healthEvents | -| CA | https://api.ca.sumologic.com/docs/#tag/healthEvents | -| DE | https://api.de.sumologic.com/docs/#tag/healthEvents | -| EU | https://api.eu.sumologic.com/docs/#tag/healthEvents | -| FED | https://api.fed.sumologic.com/docs/#tag/healthEvents | -| JP | https://api.jp.sumologic.com/docs/#tag/healthEvents | -| KR | https://api.kr.sumologic.com/docs/#tag/healthEvents | -| US1 | https://api.sumologic.com/docs/#tag/healthEvents | -| US2 | https://api.us2.sumologic.com/docs/#tag/healthEvents | +| AU | https://api.au.sumologic.com/docs/#tag/accountEvents | +| CA | https://api.ca.sumologic.com/docs/#tag/accountEvents | +| DE | https://api.de.sumologic.com/docs/#tag/accountEvents | +| EU | https://api.eu.sumologic.com/docs/#tag/accountEvents | +| FED | https://api.fed.sumologic.com/docs/#tag/accountEvents | +| JP | https://api.jp.sumologic.com/docs/#tag/accountEvents | +| KR | https://api.kr.sumologic.com/docs/#tag/accountEvents | +| US1 | https://api.sumologic.com/docs/#tag/accountEvents | +| US2 | https://api.us2.sumologic.com/docs/#tag/accountEvents | ## Required role capabilities diff --git a/docs/api/index.md b/docs/api/index.md index 1e4666ce00..6bd9abffcb 100644 --- a/docs/api/index.md +++ b/docs/api/index.md @@ -96,7 +96,7 @@ Use the Sumo Logic Application Programming Interfaces (APIs) to interact with ou
- Thumbnail icon

Health Events

+ Thumbnail icon

Account Events

diff --git a/docs/get-started/sumo-logic-ui-classic.md b/docs/get-started/sumo-logic-ui-classic.md index 35e76203e5..c120bf8ed4 100644 --- a/docs/get-started/sumo-logic-ui-classic.md +++ b/docs/get-started/sumo-logic-ui-classic.md @@ -242,7 +242,7 @@ To manage data in Sumo Logic, do the following: * **Collection.** [Manage collectors and sources](/docs/send-data/collection). * **Logs.** Manage [fields](/docs/manage/fields), [field extraction rules](/docs/manage/field-extractions), [partitions](/docs/manage/partitions), [scheduled views](/docs/manage/scheduled-views), [connections](/docs/alerts/webhook-connections), and [data forwarding](/docs/manage/data-forwarding). * **Metrics.** Manage metrics rules, [logs-to-metrics](../metrics/logs-to-metrics.md), and [metrics transformation rules](../metrics/metrics-transformation-rules.md). - * **Monitoring.** [Monitors](/docs/alerts/monitors), [connections](/docs/alerts/webhook-connections), and [health events](/docs/manage/health-events). + * **Monitoring.** [Monitors](/docs/alerts/monitors), [connections](/docs/alerts/webhook-connections), and [account events](/docs/manage/account-events). ### Admin: Manage accounts, users, and security diff --git a/docs/get-started/sumo-logic-ui.md b/docs/get-started/sumo-logic-ui.md index d8bf6a8c89..d4a830e1b9 100644 --- a/docs/get-started/sumo-logic-ui.md +++ b/docs/get-started/sumo-logic-ui.md @@ -89,7 +89,7 @@ Use the **Go To...** menu for quick access to settings and features. config.png -* **Collection**. [Collection](/docs/send-data/collection/), [OpenTelemetry Collection](/docs/send-data/opentelemetry-collector/), [Source Template](/docs/send-data), [Status](/docs/manage/ingestion-volume/collection-status-page/), [Ingest Budget](/docs/manage/ingestion-volume/ingest-budgets/), [Health Events](/docs/manage/health-events/), [Archive](/docs/manage/data-archiving/archive), [Data Archiving](/docs/manage/data-archiving/). +* **Collection**. [Collection](/docs/send-data/collection/), [OpenTelemetry Collection](/docs/send-data/opentelemetry-collector/), [Source Template](/docs/send-data), [Status](/docs/manage/ingestion-volume/collection-status-page/), [Ingest Budget](/docs/manage/ingestion-volume/ingest-budgets/), [Account Events](/docs/manage/account-events/), [Archive](/docs/manage/data-archiving/archive), [Data Archiving](/docs/manage/data-archiving/). * **Logs**. [Fields](/docs/manage/fields/), [Field Extraction Rules](/docs/manage/field-extractions/), [Partitions](/docs/manage/partitions/), [Scheduled Views](/docs/manage/scheduled-views/), [Data Forwarding](/docs/manage/data-forwarding/), [Threat Intelligence](/docs/security/threat-intelligence/). * **Metrics**. [Metrics Rules](/docs/metrics/metric-rules-editor/), [Logs-to-Metrics](/docs/metrics/logs-to-metrics/), [Metrics Transformation Rules](/docs/metrics/metrics-transformation-rules/). * **Monitoring**. [Connections](/docs/alerts/webhook-connections). diff --git a/docs/integrations/saas-cloud/sumo-collection.md b/docs/integrations/saas-cloud/sumo-collection.md index 6f983bbe55..09446e9f05 100644 --- a/docs/integrations/saas-cloud/sumo-collection.md +++ b/docs/integrations/saas-cloud/sumo-collection.md @@ -18,7 +18,7 @@ This app includes [built-in monitors](#sumo-collection-monitors). For details on ::: :::tip -For related info on collector health events, see [this doc](/docs/manage/health-events). +For related info on collector account events, see [this doc](/docs/manage/account-events). ::: ## Log types diff --git a/docs/manage/health-events.md b/docs/manage/health-events.md index a4e3e83abf..f813fd1b2b 100644 --- a/docs/manage/health-events.md +++ b/docs/manage/health-events.md @@ -1,6 +1,6 @@ --- -id: health-events -title: Health Events +id: account-events +title: Account Events description: Monitor the health of your Collectors and Sources. --- @@ -11,50 +11,49 @@ description: Monitor the health of your Collectors and Sources. | CloudFlex | Professional, Enterprise | | Credits | Trial, Essentials, Enterprise Operations, Enterprise Security, Enterprise Suite | -Health events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues.  +System events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues.  This framework includes the following: -* Health event logs indexed in the [System Event Index](/docs/manage/security/audit-indexes/system-event-index). -* A [health events table](#health-events-table) on the Alerts page. -* A health status column on the [Collection page](#collection-page). +* Account event logs indexed in the [Account Event Index](/docs/manage/security/audit-indexes/account-event-index). +* A [account events table](#account-events-table) on the Alerts page. +* A account status column on the [Collection page](#collection-page). -Health events are sent from Installed Collectors on version 19.308-2 and -later. +Account events are sent from Installed Collectors on version 19.308-2 and later. ## Alerts -Alerts for specific health events are easy to create in the Health Events Table. The details pane of an event provides a **Create Scheduled Search** button to automatically generate the required query. +Alerts for specific account events are easy to create in the Account Events Table. The details pane of an event provides a **Create Scheduled Search** button to automatically generate the required query. -## Health events +## Account events -Health events are created when an issue is detected with a Collector or Source. Events are indexed and searchable in a separate partition named **sumologic_system_events** in the [System Event Index](/docs/manage/security/audit-indexes/system-event-index). For details on what information is available in a health event, see the [common parameters](#common-parameters) table. +Account events are created when an issue is detected with a Collector or Source. Events are indexed and searchable in a separate partition named **sumologic_system_events** in the [Account Event Index](/docs/manage/security/audit-indexes/account-event-index). For details on what information is available in a health event, see the [common parameters](#common-parameters) table. -### Health events table +### Account events table -The health events table allows you to easily view and investigate problems getting your data to Sumo. +The account events table allows you to easily view and investigate problems getting your data to Sumo. -On the health events table, you can search, filter, and sort incidents by key aspects like severity, resource name, event name, resource type, and opened since date. +On the account events table, you can search, filter, and sort incidents by key aspects like severity, resource name, event name, resource type, and opened since date. -[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access the health events table, in the main Sumo Logic menu select **Manage Data > Monitoring > Health Events**. +[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access the account events table, in the main Sumo Logic menu select **Manage Data > Monitoring > Health Events**. -[**New UI**](/docs/get-started/sumo-logic-ui/). To access the health events table, in the top menu select **Configuration**, and then under **Data Collection** select **Health Events**. You can also click the **Go To...** menu at the top of the screen and select **Health Events**. +[**New UI**](/docs/get-started/sumo-logic-ui/). To access the account events table, in the top menu select **Configuration**, and then under **Data Collection** select **Account Events**. You can also click the **Go To...** menu at the top of the screen and select **Account Events**. -![health events table.png](/img/health-events/health-events-table.png) +![account events table.png](/img/health-events/health-events-table.png) Click on a row to view the details of a health event. ![health event detail.png](/img/health-events/health-event-detail.png) -Click the **Create Scheduled Search** button on the details pane to get alerts for specific health events. The unique identifier of the resource, such as the Source or Collector, is used in the query. See [Schedule a Search](../alerts/scheduled-searches/schedule-search.md) for details. +Click the **Create Scheduled Search** button on the details pane to get alerts for specific account events. The unique identifier of the resource, such as the Source or Collector, is used in the query. See [Schedule a Search](../alerts/scheduled-searches/schedule-search.md) for details. Under the **More Actions** menu you can select: * **Event History** to run a search against the **sumologic_system_events** partition to view all of the related event logs. * **View Object** to view the Collector or Source in the Collection page related to the event. -### Health events severity +### Account events severity Events are categorized by two severity levels, warning and error. The severity column has color-coded error and warning events so you can quickly determine the severity of a given issue. @@ -71,7 +70,7 @@ common parameters in the order that they are found in health event logs. |:--|:--|:--| | status | Either `Healthy` or `Unhealthy` based on the event. | String | | details | The details of the event include the type as `trackerId`, the `name` of the event, and a `description`. | JSON object of Strings | -| eventType | Health events have a value of `Health-Change`. | String | +| eventType | Account events have a value of `Health-Change`. | String | | severityLevel | Either `Error` or `Warning` based on the event. | String | | accountId | The unique identifier of the organization. | String | | eventId | The unique identifier of the event. | String | @@ -110,9 +109,9 @@ common parameters in the order that they are found in health event logs. } ``` -## Search health events +## Search Account events -To search all health events run a query against the internal partition +To search all account events run a query against the internal partition named **sumologic_system_events**. For example, ```sql @@ -120,12 +119,12 @@ _index=sumologic_system_events "Health-Change" ``` :::tip -Create a scheduled search to get alerts for specific health events. +Create a scheduled search to get alerts for specific account events. ::: ### Metadata assignment -Creating a query that defines built-in metadata field values in the scope can help improve search performance and limit results to what you're investigating. [Metadata](../search/get-started-with-search/search-basics/built-in-metadata.md) fields are assigned to health event logs as follows: +Creating a query that defines built-in metadata field values in the scope can help improve search performance and limit results to what you're investigating. [Metadata](../search/get-started-with-search/search-basics/built-in-metadata.md) fields are assigned to account event logs as follows: | **Metadata Field** | **Assignment Description** | |:--|:--| @@ -139,9 +138,9 @@ A **Health** column on the Collection page shows color-coded healthy, error, a The **status** column now shows the status of Sources manually paused by users. -![Collection health column.png](/img/health-events/Collection-health-column.png) +![Collection account column.png](/img/health-events/Collection-health-column.png) -* Hover your mouse over a Collector or Source to view a tooltip that provides the number of health events detected on the Collector or Source. +* Hover your mouse over a Collector or Source to view a tooltip that provides the number of account events detected on the Collector or Source. ![health tooltip.png](/img/health-events/health_tooltip.png) diff --git a/docs/manage/index.md b/docs/manage/index.md index 85311ffd28..54a4098869 100644 --- a/docs/manage/index.md +++ b/docs/manage/index.md @@ -23,7 +23,7 @@ This topic describes features and options that give you administration over acco
- icon

Health Events

+ icon

Account Events

Monitor the health of your Collectors and Sources.

diff --git a/docs/manage/ingestion-volume/ingest-budgets/daily-volume.md b/docs/manage/ingestion-volume/ingest-budgets/daily-volume.md index 4312bf8cca..af29232560 100644 --- a/docs/manage/ingestion-volume/ingest-budgets/daily-volume.md +++ b/docs/manage/ingestion-volume/ingest-budgets/daily-volume.md @@ -257,11 +257,11 @@ Search for only capacity usage logs: _index=sumologic_audit _sourceName=VOLUME_QUOTA _sourceCategory=account_management "Budget" "last reset" ``` -### Health events +### Account events -Health events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues. See [Health events](/docs/manage/health-events.md) for details. +Account events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues. See [Account events](/docs/manage/account-events.md) for details. -Ingest budgets that have exceeded their capacity are placed in an **Error** health state. The following are two common queries used to investigate the health of ingest budgets. +Ingest budgets that have exceeded their capacity are placed in an **Error** account state. The following are two common queries used to investigate the health of ingest budgets. A query to search for all ingest budgets that are over capacity. diff --git a/docs/manage/manage-subscription/fedramp-capabilities.md b/docs/manage/manage-subscription/fedramp-capabilities.md index ff70e5a489..2b10e6febd 100644 --- a/docs/manage/manage-subscription/fedramp-capabilities.md +++ b/docs/manage/manage-subscription/fedramp-capabilities.md @@ -102,6 +102,6 @@ The following table shows the capabilities included with Sumo Logic’s FedRAMP | Manage Data - Metrics | [Metrics Rules](/docs/metrics/metric-rules-editor/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| | Manage Data - Metrics | [Metrics transformation rules](/docs/metrics/metrics-transformation-rules/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| | Manage Data - Monitoring | [Connections](/docs/alerts/webhook-connections/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| -| Manage Data - Monitoring | [Health events](/docs/manage/health-events/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| +| Manage Data - Monitoring | [Account events](/docs/manage/account-events/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| | Manage Data - Monitoring | [Monitors](/docs/alerts/monitors/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| | Manage Data - Monitoring | [SLOs](/docs/observability/reliability-management-slo/) |![check](/img/reuse/check.png)|![check](/img/reuse/check.png)| diff --git a/docs/manage/security/audit-indexes/system-event-index.md b/docs/manage/security/audit-indexes/system-event-index.md index 649c6fbe31..d8a79ebb62 100644 --- a/docs/manage/security/audit-indexes/system-event-index.md +++ b/docs/manage/security/audit-indexes/system-event-index.md @@ -54,7 +54,7 @@ _index=sumologic_system_events _sourceCategory=alerts | [Automation Service and Cloud SOAR](/docs/platform-services/automation-service/automation-service-audit-logging/) | `oar*` | | [Cloud SIEM](/docs/cse/administration/cse-audit-logging/) | `cse*` | | [Fields](/docs/manage/fields) | `fieldManagement` | -| [Health Events](/docs/manage/health-events/) | `Collection` | +| [Account Events](/docs/manage/account-events/) | `Collection` | | [Monitors](/docs/alerts/monitors) | `monitors` | | [Tracing Ingest](/docs/apm/traces/tracing-ingest) | `tracingIngest` | diff --git a/docs/metrics/introduction/metric-formats.md b/docs/metrics/introduction/metric-formats.md index 648b265ffc..cbdd440e0a 100644 --- a/docs/metrics/introduction/metric-formats.md +++ b/docs/metrics/introduction/metric-formats.md @@ -97,7 +97,7 @@ cluster=cluster-1 node=node-1 cpu=cpu-1 metric=cpu_idle 97.29 1460061337 ### Mandatory metric name -Unlike Prometheus, Carbon 2.0 format doesn't enforce the presence of a metric name. It also cannot be reliably inferred automatically. Therefore, Sumo Logic requires a `metric` key to be present among `intrinsic_tags`. All metrics without a `metric` key specified will not be ingested to Sumo Logic and a `MetricsMetricNameMissing` Health Event for the associated Metric Source will be triggered (for more information on Health Events, see [About Health Events](/docs/manage/health-events#health-events)). +Unlike Prometheus, Carbon 2.0 format doesn't enforce the presence of a metric name. It also cannot be reliably inferred automatically. Therefore, Sumo Logic requires a `metric` key to be present among `intrinsic_tags`. All metrics without a `metric` key specified will not be ingested to Sumo Logic and a `MetricsMetricNameMissing` Account Event for the associated Metric Source will be triggered (for more information on Account Events, see [About Account Events](/docs/manage/account-events#account-events)). For example, the following metric will be correctly ingested to Sumo Logic: ``` diff --git a/docs/search/index.md b/docs/search/index.md index c5831bbdfb..b3abc93c02 100644 --- a/docs/search/index.md +++ b/docs/search/index.md @@ -119,11 +119,11 @@ In this micro lesson, learn about the ingestion pipeline and the journey that a ## Partitions and Views -Logs collected by Sumo Logic are indexed in Partitions and Scheduled Views. In addition, there are internal indexes such as Health Events, Archive, Audit, and Volume indexes. +Logs collected by Sumo Logic are indexed in Partitions and Scheduled Views. In addition, there are internal indexes such as Account Events, Archive, Audit, and Volume indexes. * A Partition stores your data in an index separate from the rest of your account data so you can [optimize searches](optimize-search-performance.md), [manage variable retention](/docs/manage/partitions/manage-indexes-variable-retention), and specify certain [data to forward to S3](/docs/manage/data-forwarding/amazon-s3-bucket). See how to [Run a Search Against a Partition](/docs/search/optimize-search-partitions). * Scheduled Views speed the search process subsets of your data by functioning as a pre-aggregated index. See how to [Run a Search Against a Scheduled View](/docs/manage/scheduled-views/run-search-against-scheduled-view). -* Health Events monitor the health of your Collectors and Sources. See how to [Search Health Events](/docs/manage/health-events). +* Account Events monitor the health of your Collectors and Sources. See how to [Search Account Events](/docs/manage/account-events). * Archive allows you to forward log data from Installed Collectors to Amazon S3 buckets to collect at a later time. See how to [Search ingested Archive data](/docs/manage/data-archiving/archive). * Audit and Event Audit provide information on the internal events that occur in Sumo Logic. See how to search the Audit and [Audit Event Index](/docs/manage/security/audit-indexes/audit-event-index). * Data Volume gives you visibility into how much data you are sending to Sumo Logic, allowing you to proactively manage your systems’ behavior and to fine tune your data ingest with respect to the data plan for your Sumo Logic subscription. See [Data Volume Index](/docs/manage/ingestion-volume/data-volume-index) for details. diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/source-info.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/source-info.md index b139762af4..569e1171e7 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/source-info.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/source-info.md @@ -19,9 +19,9 @@ If the Source has any issues during any one of these states, it is placed in an When you delete the Source, it is placed in a **Stopping** state. When it has successfully stopped, it is deleted from your Hosted Collector. -On the [Collection page](/docs/manage/health-events#collection-page), the Health and Status for Sources is displayed. Use [Health Events](/docs/manage/health-events.md) to investigate issues with collection. +On the [Collection page](/docs/manage/health-events#collection-page), the Health and Status for Sources is displayed. Use [Account Events](/docs/manage/account-events.md) to investigate issues with collection. -Hover your mouse over the status icon to view a tooltip with a count of the detected errors and warnings. You can click on the status icon to open a Health Events panel with details on each detected issue. +Hover your mouse over the status icon to view a tooltip with a count of the detected errors and warnings. You can click on the status icon to open a Account Events panel with details on each detected issue. ## Metadata fields @@ -37,7 +37,7 @@ The checkbox only shows up if you have Cloud SIEM and if the C2C already has Clo ## Error Types -When Sumo Logic detects an issue it is tracked by Health Events. The following table shows the three possible error types, the reason the error would occur, if the Source attempts to retry, and the name of the event log in the Health Event Index. +When Sumo Logic detects an issue it is tracked by Account Events. The following table shows the three possible error types, the reason the error would occur, if the Source attempts to retry, and the name of the event log in the Health Event Index. | Type | Reason | Retries | Retry Behavior | Health Event Name | |:--|:--|:--|:--|:--| diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sumo-collection-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sumo-collection-source.md index 3c23f381d8..e76bd189b2 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sumo-collection-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sumo-collection-source.md @@ -18,7 +18,7 @@ Sumo Logic's Cloud-to-Cloud (C2C) framework enables seamless data integration by This source supports both Installed and Hosted Collectors configured within a C2C environment. By using Sumo Logic’s API, it provides centralized, real-time visibility into collector and source health, operational status, and configuration metrics—helping teams proactively monitor deployments, troubleshoot issues, and maintain a reliable data collection pipeline. :::tip -For related info on collector health events, see [this doc](/docs/manage/health-events). +For related info on collector account events, see [this doc](/docs/manage/account-events). ::: ## Data collected diff --git a/docs/send-data/hosted-collectors/google-source/gcp-metrics-source.md b/docs/send-data/hosted-collectors/google-source/gcp-metrics-source.md index 47850e377e..c5e61aafcb 100644 --- a/docs/send-data/hosted-collectors/google-source/gcp-metrics-source.md +++ b/docs/send-data/hosted-collectors/google-source/gcp-metrics-source.md @@ -173,9 +173,9 @@ The minimum sample period for GCP metrics is 60 seconds, in which only 1 data po | BOOL | N/A | N/A | Count | -## Health Events +## Account Events -Health events are provided for the following: +Account events are provided for the following: * Connection to the GCP server fails: This connection error may be due to incorrect or invalid credentials or the project has been deleted, including incorrect project id, private key, client email, and access. * No metric is found to ingest due to source configuration: The source may include a custom service that does not exist or match data (due to typos or incorrect name). Verify your source configuration against available GCP metrics. diff --git a/docs/send-data/installed-collectors/sources/streaming-metrics-source.md b/docs/send-data/installed-collectors/sources/streaming-metrics-source.md index f7482cf2d1..68cdd83652 100644 --- a/docs/send-data/installed-collectors/sources/streaming-metrics-source.md +++ b/docs/send-data/installed-collectors/sources/streaming-metrics-source.md @@ -111,7 +111,7 @@ For example: metric=request_rate site=mydomain mtype=rate unit=Req/s host=web12 agent=statsdaemon1 234 1234567890 ``` -Unlike Prometheus, Carbon 2.0 format doesn't enforce the presence of a metric name. It also cannot be reliably inferred automatically. Therefore, Sumo Logic require a `metric` key to be present among `intrinsic_tags`. All metrics without a `metric` key specified will not be ingested to Sumo and a `MetricsMetricNameMissing` Health Event for the associated Metric Source will be triggered (for more information on Halth Events, see [About Health Events](/docs/manage/health-events#health-events)). +Unlike Prometheus, Carbon 2.0 format doesn't enforce the presence of a metric name. It also cannot be reliably inferred automatically. Therefore, Sumo Logic require a `metric` key to be present among `intrinsic_tags`. All metrics without a `metric` key specified will not be ingested to Sumo and a `MetricsMetricNameMissing` Health Event for the associated Metric Source will be triggered (for more information on Halth Events, see [About Account Events](/docs/manage/account-events#account-events)). For example, the following metric will be correctly ingested to Sumo Logic: ``` diff --git a/sidebars.ts b/sidebars.ts index dcb4096a99..3637df51d4 100644 --- a/sidebars.ts +++ b/sidebars.ts @@ -3,7 +3,7 @@ Add content to the following sections in this sidebar Navigation file: Manage: Admin level options, collection, connections, etc - Dashboards & Visuals: NDashboards, Library of Dashboards, Alerts, Monitors, Alerts, Monitors, SLOs, Health Events, Connections + Dashboards & Visuals: NDashboards, Library of Dashboards, Alerts, Monitors, Alerts, Monitors, SLOs, Account Events, Connections Searches & Logs: Log Search, All Log Searches, Livetail, Lookup, Log Config Metrics & Logs: Metrics Search, All Metrics Searches, Config Infrastructure Monitoring: Kubernetes, AWS Observability, Root Cause Explorer,