> ## 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.

# Extend services

After configuring a service and reviewing its
[service page](/observe/services/service-pages), extend the service with change event
overlays, dependency maps, and connected monitors or dashboards. These capabilities
add operational context to each service so you can correlate changes, trace
dependencies, and surface related resources during an investigation.

## Display change events

<Note>
  To overlay change events, your organization must purchase
  [change event tracking](https://chronosphere.io/platform/change-event-tracking/)
  and have it enabled in your tenant.
</Note>

You can enable [change events](/observe/enable-events/services) to
display them on panels for each of your services. This capability lets you visualize
changes in your environment relative to a specific service.

## View dependencies

<Note>
  To view dependency maps for trace data in service pages, your organization must
  purchase [distributed tracing](https://chronosphere.io/platform/distributed-tracing/)
  and have it enabled in your tenant.
</Note>

When receiving an alert about your service, you need to identify and fix the issue as
quickly as possible. If the issue isn't with your service, you want to inform the
responsible team so they can investigate the issue.

Use *dependency maps* to view a perspective that's scoped to an individual service,
including its upstream and downstream dependencies. These maps visualize trends in
duration, requests, and errors, so you can
[understand trends](/observe/services/service-pages#understand-trends)
to focus your investigation. See
[Service exploration](/observe/services/service-exploration) for an example of how to
use dependency maps to help identify issues.

## View connected resources

In addition to displaying monitors and dashboards
[owned by a service](/observe/services/service-pages#visualization-panels), you can
also connect these resources to a service, even when they're owned by another
service. Connecting monitors and dashboards to services can help you identify issues
in upstream or downstream services.

Tables in a service page's sidebar list its associated dashboards and monitors,
and include management tools to connect existing resources to the currently viewed
service. Dashboards and monitors owned by the selected service prepopulate the lists.

### Connect a resource to a service without transferring ownership

To connect an existing resource to the currently viewed service without changing
the resource's ownership:

1. Next to **Dashboards** or **All Monitors**, click **Manage**.
2. Select **Connections** to open the **Manage connections** panel.
3. Search for a resource using the following methods:
   * Scroll the list until you find the dashboard.
   * Type the resource name in the **Search dashboards** box.
   * Use the **Select a team** menu to choose a specific
     [team](/administer/accounts-teams/teams).
   * Use the **Select an owner** dropdown to choose a collection or service.
4. Select the checkboxes on the rows of the resources you want to associate with
   the service. You can select multiple resources at once.
5. Click **Connect *`<RESOURCES>`***. *`<RESOURCES>`* reflects the type of resource
   you're managing, such as **Connect dashboards** or **Connect monitors**.

After resources are connected to a service, the **Connected *`<RESOURCES>`*** table
on the **Manage connections** panel displays them.

### Edit a connected resource

1. Next to **All monitors** or **Dashboards**, click **Manage**.
2. Select **Manage connections**.
3. Make changes in the **Connected *`<RESOURCES>`*** table.

### Remove a connection to a dashboard or monitor

1. Next to **All monitors** or **Dashboards**, click **Manage**.
2. Select **Manage connections**.
3. In the **Connected *`<RESOURCES>`*** section, select the checkboxes on the rows
   of the resources whose connections you want to remove.
4. Click **Delete *`<RESOURCE>`* connections**.
5. Click **Delete** to confirm.

### Connect a resource to a service by transferring ownership

<Warning>
  Changing a resource's ownership removes its association with its current owner.
  Make sure any other users who rely on that association are aware of ownership changes
  to the resource.
</Warning>

To connect an existing resource to the currently viewed service by changing the
resource's ownership to the service:

1. Next to **Dashboards** or **All Monitors**, click **Manage**.
2. Select **Owned \_`<RESOURCE>`** to open the **Manage ownership** panel.
   *`<RESOURCES>`* reflects the type of resource you're managing, such as
   **Owned dashboards** or **Owned monitors**.
3. Search for a resource using the following methods:
   * Scroll the list until you find the dashboard.
   * Type the resource name in the **Search dashboards** box.
   * Use the **Select a team** menu to choose a specific
     [team](/administer/accounts-teams/teams).
   * Use the **Select an owner** dropdown to choose a collection or service.
4. Select the checkboxes on the rows of the resources you want to associate with
   the service. You can select multiple resources at once.
5. Click **Update ownership**.

After resources are connected to a service, the **Owned *`<RESOURCES>`*** table
on the **Manage ownership** panel displays the resources.

### Affect service health

When viewing a connected monitor, toggle **Affects service health** to include
this resource in the service status.