---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Chart error states

# Chart error states {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Understand the different error states that the charts in Service Observability might display and how to fix them.
{#chart-error-states__table_fc1_pj3_zdc__entry__2}

| Error message | Fix |
|-|-|
| Set up this service's observability data mapping | Observability mapping hasn't been configured for the service by an admin. See [Create and manage data mappings](https://servicenow-prod.fluidtopics.net/HYIXjutsl~r6FQOV1gv~1g "Map your services to the data from a connected external observability vendor instance, and view it in charts for the service."). |
| Data mapping is not configured | Observability mapping hasn't been configured for the service by an admin. See [Create and manage data mappings](https://servicenow-prod.fluidtopics.net/HYIXjutsl~r6FQOV1gv~1g "Map your services to the data from a connected external observability vendor instance, and view it in charts for the service."). |
| Authentication failed | Service Observability can't connect to the data source. See [Connect a Service Observability data source](https://servicenow-prod.fluidtopics.net/nLQDmN9XD6_07ekdPuQduw "Connect Service Observability to an external observability system. Service Observability displays metrics in the Service Operations Workspace (SOW) from that observability instance."). |
| No results found | No metrics were found for the chart. |
| Something went wrong | Connection to the data source was successful, but the observability instance didn't respond. This error might be due to a connection timeout on the observability vendor side. |
| No impacted systems found (Impacted systems chart on the Overview page) | Only services found on your service map can be displayed. Update your service map to include all services that should be included in the chart. See [Service Mapping](https://servicenow-prod.fluidtopics.net/i01SxxMdD7M2O~EeEIvbzQ "The ServiceNow Service Mapping application discovers all application services in your organization and builds a comprehensive map of all devices, applications, and configuration profiles used in these application services."). |
| Set up objectives (SLO Error Budget chart on the Overview page) | SLOs haven't been configured for Service Reliability Management. See [Create SLOs, SLIs, and error budget policies](https://servicenow-prod.fluidtopics.net/RIPYihn~X_oMHIeK5CAfaQ "Define service level objectives (SLOs), service level indicators (SLIs), and error budget policies to monitor service health. These tools help you and your teams track performance and respond when needed."). |
[ ]

{#chart-error-states__table_fc1_pj3_zdc}