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

# Administer your tools and users

Administrative users focus on observability tools so that developers can use those
tools to monitor and maintain the health of their distributed system. As an
administrative user, you might focus on one or more of the following tasks.

## Cost control

Track telemetry usage against your contract with the
[License Overview](/administer/limits-licensing/licensing), which
surfaces consumption snapshots and trends for each telemetry type. To investigate
what's driving growth, [analyze consumption](/control/consumption/analyze) across
partitions and budgets. Then use the
[Control Plane](/control/shaping) to shape, sample, and reduce the data you persist.

## Data collection

[Ingest telemetry data](/ingest) into Chronosphere Observability Platform, which can
include metrics, traces, and change events. Your Collector selection depends on the
data you plan to ingest. Chronosphere recommends using the Chronosphere Collector,
but can also ingest data from the OpenTelemetry Collector.

## Data usability

[Explore your data](/investigate) to understand where you can normalize,
sanitize, and optimize telemetry data to make it usable for developers and to filter
out less actionable data. [Analyze usage metrics](/overview/types/metrics) and
implement aggregation rules to improve the quality and reduce the cardinality of
stored metrics data.

## Service level objectives

Define [service level objectives](/observe/slo) (SLOs) that measure your services'
availability from your users' perspective. Effective SLOs combine user-focused
indicators, realistic objectives based on historical performance, and tuned burn
rate alerts that help responders react before error budgets are exhausted.
[Design service level objectives](/administer/design-slos) to choose the right
indicators, set realistic objectives, and configure burn rate alerts for your
services.

## Platform usability

Create and manage [collections](/administer/collections) to group Observability
Platform resources associated with a service or feature you want to monitor. You
create [teams](/administer/accounts-teams/teams) to organize accounts into groups and
define permissions for sensitive management and administrative operations. A team's
accounts have shared responsibility for individual services, which Observability
Platform represents as collections.