> ## Documentation Index > Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt > Use this file to discover all available pages before exploring further. # Observe your telemetry data export const ServiceNavIcon = props => { return ; }; [Chronosphere Lens](https://chronosphere.io/learn/empower-developer-effectiveness-in-the-cloud-native-age-with-chronosphere-lens/) gives you visibility into the health and performance of your applications by ingesting metrics, traces, and change events that you can observe using [services](/observe/services) and [dashboards](/observe/dashboards). Use Chronosphere Lens to review services and visually examine trends in telemetry data at a high level. Dashboards help visualize data in more specific and custom ways. Incorporate dashboards into your services to tie your data together in ways that make sense for your observability teams and reduce time to mitigate. ## Services Services pages provide opinionated displays of telemetry data that are the most important to your organization. Chronosphere Observability Platform discovers services automatically and provides efficient views into your app services to help you discover ways to explore your data. Service pages take advantage of other Observability Platform features, including [tagged metrics](/overview/types/metrics), [queries](/investigate/querying), [data visualization panels](/observe/dashboards/panels), [teams](/administer/accounts-teams/teams), [collections](/administer/collections), and [change events](/overview/types/change-events). Use [pinned scopes](/navigate/pinned-scopes) to narrow your observed data, and to keep filtering based on that scope as you navigate Observability Platform to triage problems. ## Service level objectives Monitors and alerts help identify when data spikes occur or services become unreliable or unresponsive, and notify the responsible individuals. [Service level objectives (SLOs)](/observe/slo) provide a more dynamic incident detection method that let you trigger alerts based on changes in real user experiences, rather than at an arbitrary threshold. Create SLOs to set explicit reliability targets, paired with an error budget, indicator metrics, and a rolling time window, to measure how services actually behave over time. This comprehensive view helps identify when an error budget is burning, spot trends that monitors might obscure, and keep engineering efforts aligned with your SLO objective for uptime. ## Dashboards Chronosphere Observability Platform dashboards target use cases relevant to service and app monitoring. Analyze your telemetry data by creating visualizations of query results that you can customize, filter, and focus within a dashboard. Use this information to identify and act on trends, correlate changes in data to incidents, and monitor microservice statuses in real time. Observability Platform provides a group of [predefined dashboards](/observe/dashboards/chronosphere-managed-dashboards), and the ability to [create and customize dashboards](/observe/dashboards#create-a-new-dashboard) tailored to the specific needs of your organization and the teams within it. If your organization purchased change event tracking and distributed tracing, you can overlay additional telemetry data on your dashboards to help expedite problem resolution: * [Enable change events in dashboards](/observe/enable-events/dashboards#standard-dashboards) to display change events as a lined annotation on your dashboard panels. * [Query traces directly from a dashboard](/observe/dashboards/query-traces), which lets you search your trace data without having to navigate to Trace Explorer. ## Change events Change events describe changes within your environment or Observability Platform tenant at a specific time so you can answer questions like *When did a particular service deploy last?* or *Which alerts triggered in the last week?* [Enable change events](/observe/enable-events) to overlay them on other areas of Observability Platform, such as lined annotations on dashboard panels. This ability to identify and isolate change events can help remediate issues faster and minimize downstream impacts. You can then [filter change events](/investigate/querying/filter-events) during on-call triage to understand what changes occurred prior to the onset of an issue. ## Working together When creating a service, spend time to research and [design SLOs](/observe/slo) that map to the performance and reliability standards for your organization. In an ideal observability workflow, SLOs are upstream of most other practices, and determine what and how you observe. After the design phase, [create an SLO](/investigate/alerts/manage-slos#create-a-new-slo) for reporting, alerting, and visualizations. When you're getting started using Observability Platform, your workflow might look something like: 1. In the navigation menu select ** System Overview > Services**. 2. Identify an interesting trend or incident. 3. [Explore panels](/observe/services/service-pages#explore-queries) in the service to display queries behind a data visualization. 4. [Create a dashboard](/observe/dashboards#create-a-new-dashboard) and add those queries to new panels. 5. [Edit the queries](/investigate/querying/metrics/explorer#enter-and-run-a-query) and tailor the visualizations to your needs. When an investigation spans multiple pages, use [notebooks](/navigate/notebooks) to gather panels, resource links, and notes in one side panel, and share a link with teammates who need the same context. As you get better at identifying trends and incidents, you can turn those queries and understanding of your telemetry data into [monitors and alerts](/investigate/alerts), reducing on-call escalations and incidents.