In the documentation for doing a silent managed cluster install (https://www.dynatrace.com/support/help/dynatrace-m...)there are three datastore parameters:
--datastore-dir — Full path to the Dynatrace installation space directory. All Dynatrace data is kept here. It's recommended that you use a dedicated drive or partition for this directory.
--cas-datastore-dir — Full path to the Dynatrace metrics repository directory. If you specify this location, metrics data will be kept here instead of in the main data location.
--svr-datastore-dir — Full path to Dynatrace raw transaction store directory. If you specify this location, raw transaction data will be kept here instead of in the main data location.
--cas-datastore-dir is designated for Cassandra, that makes sense.
However, where would the other two data structures (PurePath transactional data and ElasticSearch visit data) fit in this picture?
According to the comment, I would assume --svr-datastore-dir is for PurePaths, but where do the ElasticSearch visits go?
Additional question: in the sizing table on https://www.dynatrace.com/support/help/dynatrace-m... 2 disk requirements are mentioned: Transaction Storage and Long Term Metrics Store. Transaction Store would be PurePaths and thus maps to svr-datastore; Long Term Metrics Store maps to Cassandra and thus cas-datastore. Where does ElasticSearch fit in? How is this sized?
Thanks for your answers.
Solved! Go to Solution.
currently ElasticSearch path is not customizable by the installer. ElasticSearch data is stored together with PurePaths on the path specified by --svr-datastore-dir - in "elasticsearch" subdirectory.
The team plans to improve this and make it customizable, but I have no concrete date when this is available.
Hi Kristof, I have double checked the path details and I have to correct my previous answer as it was not accurate.
First of all, the ElasticSarch path can be customized, but only in interactive installer mode. The team will prioritize adding this as a parameter for silent mode as well.
Regarding path parametrization, we have 5 configurable paths:
1) For binaries (--binaries-dir)
2) Default datastore (--datastore-dir) - there are things like logs, temporary files, installers downloads in auto-update process. More importantly, this is also the default location for all Dynatrace Managed data, but can be further customized
3) Long-term metrics storage (Cassandra) (--cas-datastore-dir) - time-series data stored in Cassandra, cluster configuration is also persited there. If path is not customized, default datastore path is used
4) Transaction storage (--svr-datastore-dir) - this is where raw data/PurePaths are stored. If path is not customized, default datastore path is used
5) ElasticSearch (no parameter for silent mode!) - this is where user sessions are stored. If path is not customized, default datastore path is used. So actually, for silent mode, since ElasticSearch customization was not possible, the fallback was default datastore, not the server as I wrote previously.
You are absolutely right that this should be better documented. We will take care of that.