|
| 1 | +[[storage-explorer]] |
| 2 | +=== Storage explorer |
| 3 | + |
| 4 | +beta::[] |
| 5 | + |
| 6 | +Analyze your APM data and manage costs with **storage explorer**. |
| 7 | +For example, analyze the storage footprint of each of your services to see which are producing |
| 8 | +large amounts of data--then change the sample rate of a service to lower the amount of data ingested. |
| 9 | +Or, expand the time filter to visualize data trends over time so that you can better forecast |
| 10 | +and prepare for future storage needs. |
| 11 | + |
| 12 | +[role="screenshot"] |
| 13 | +image::apm/images/storage-explorer-overview.png[APM Storage explorer] |
| 14 | + |
| 15 | +[float] |
| 16 | +==== Index lifecycle phases |
| 17 | + |
| 18 | +A default {apm-guide-ref}/ilm-how-to.html[index lifecycle policy] is applied to each APM data stream, |
| 19 | +but can be customized depending on your business needs. |
| 20 | +Use the **Index lifecycle phase** dropdown to visualize and analyze your storage by phase. |
| 21 | + |
| 22 | +Customizing the default APM index lifecycle policies can save money by specifying things like: |
| 23 | + |
| 24 | +* The point at which an index can be moved to less performant hardware. |
| 25 | +* The point at which availability is not as critical and the number of replicas can be reduced. |
| 26 | +* When the index can be safely deleted. |
| 27 | + |
| 28 | +See {apm-guide-ref}/ilm-how-to.html[Index lifecycle management] to learn more about customizing |
| 29 | +the default APM index lifecycle policies. |
| 30 | + |
| 31 | +[float] |
| 32 | +==== Service size chart |
| 33 | + |
| 34 | +The service size chart displays the estimated size of each service over time. |
| 35 | +Expand the time filter to visualize data trends and estimate daily data generation. |
| 36 | + |
| 37 | +[float] |
| 38 | +==== Service statistics table |
| 39 | + |
| 40 | +The service statistics table provides detailed information on each service: |
| 41 | + |
| 42 | +* A list of **service environments**. |
| 43 | +* The **sampling rate**. This value is calculated by dividing the number of sampled transactions by total throughput. |
| 44 | +It might differ from the configured sampling rate for two reasons: with head-based sampling, |
| 45 | +the initial service makes the sampling decision, and with tail-based sampling, |
| 46 | +granular policies allow you to set multiple sample rates. |
| 47 | +* The estimated **size on disk**. This storage size includes both primary and replica shards and is |
| 48 | +calculated by prorating the total size of your indices by the service's document count divided by |
| 49 | +the total number of documents. |
| 50 | +* Number of **transactions**, **spans**, **errors**, and **metrics** — doc count and size on disk. |
| 51 | + |
| 52 | +[role="screenshot"] |
| 53 | +image::apm/images/storage-explorer-expanded.png[APM Storage explorer service breakdown] |
| 54 | + |
| 55 | +As you explore your service statistics, you might want to take action to reduce the number of |
| 56 | +documents and therefore storage size of a particular service. |
| 57 | + |
| 58 | +[float] |
| 59 | +===== Reduce the number of transactions |
| 60 | +To reduce the number of transactions a service generates, configure a more aggressive |
| 61 | +{apm-guide-ref}/sampling.html[transaction sampling policy]. Transaction sampling lowers |
| 62 | +the amount of data ingested without negatively impacting the usefulness of your data. |
| 63 | + |
| 64 | +[float] |
| 65 | +===== Reduce the number of spans |
| 66 | +To reduce the number of spans a service generates, enable |
| 67 | +{apm-guide-ref}/span-compression.html[span compression]. Span compression saves on data |
| 68 | +and transfer costs by compressing multiple, similar spans into a single span. |
| 69 | + |
| 70 | +[float] |
| 71 | +===== Reduce the number of metrics |
| 72 | +To reduce the number of system, runtime, and application metrics, |
| 73 | +tune the APM agent or agents that are collecting the data. |
| 74 | +You can disable the collection of specific metrics with the **disable metrics** configuration. |
| 75 | +Or, you can set the **metrics interval** to zero seconds to deactivate metrics entirely. |
| 76 | +Most APM agents support both options. |
| 77 | +See the relevant {apm-agents-ref}[agent configuration options] for more details. |
| 78 | + |
| 79 | +[float] |
| 80 | +===== Reduce the number of errors |
| 81 | +To reduce the number of errors a service generate, |
| 82 | +work with your developers to change how exceptions are handled in your code. |
| 83 | + |
| 84 | +[float] |
| 85 | +==== Privileges |
| 86 | + |
| 87 | +Storage explorer requires expanded privileges to view. |
| 88 | +See <<apm-app-storage-explorer-user-create>> for more information. |
| 89 | + |
| 90 | +[float] |
| 91 | +==== Limitations |
| 92 | + |
| 93 | +Multi-cluster deployments are not supported. |
0 commit comments