Movatterモバイル変換


[0]ホーム

URL:


Loading

A defaultindex lifecycle policy is applied to each APM data stream, but can be customized depending on your business needs. Use theIndex lifecycle phase dropdown to visualize and analyze your storage by phase.

Customizing the default APM index lifecycle policies can save money by specifying things like:

  • The point at which an index can be moved to less performant hardware.
  • The point at which availability is not as critical and the number of replicas can be reduced.
  • When the index can be safely deleted.

SeeIndex lifecycle management to learn more about customizing the default APM index lifecycle policies.

The service size chart displays the estimated size of each service over time. Expand the time filter to visualize data trends and estimate daily data generation.

The service statistics table provides detailed information on each service:

  • A list ofservice environments.
  • Thesampling rate. This value is calculated by dividing the number of sampled transactions by total throughput. It might differ from the configured sampling rate for two reasons: with head-based sampling, the initial service makes the sampling decision, and with tail-based sampling, granular policies allow you to set multiple sample rates.
  • The estimatedsize on disk. This storage size includes both primary and replica shards and is calculated by prorating the total size of your indices by the service’s document count divided by the total number of documents.
  • Number oftransactions,spans,errors, andmetrics — doc count and size on disk.
APM Storage Explorer service breakdown

As you explore your service statistics, you might want to take action to reduce the number of documents and therefore storage size of a particular service.

Reduce the number of transactions

To reduce the number of transactions a service generates, configure a more aggressivetransaction sampling policy. Transaction sampling lowers the amount of data ingested without negatively impacting the usefulness of your data.

Reduce the number of spans

To reduce the number of spans a service generates, enablespan compression. Span compression saves on data and transfer costs by compressing multiple, similar spans into a single span.

Reduce the number of metrics

To reduce the number of system, runtime, and application metrics, tune the APM agent or agents that are collecting the data. You can disable the collection of specific metrics with thedisable metrics configuration. Or, you can set themetrics interval to zero seconds to deactivate metrics entirely. Most APM agents support both options. See the relevantAPM agent configuration options for more details.

Reduce the number of errors

To reduce the number of errors a service generate, work with your developers to change how exceptions are handled in your code.

Privileges

Storage Explorer requires expanded privileges to view. SeeCreate a storage explorer user for more information.

Limitations

Multi-cluster deployments are not supported.


[8]ページ先頭

©2009-2026 Movatter.jp