maxVQLWindowSize setting value, then some analytics queries will not consider the entire dataset. The interaction between maxVQLWindowSize and the given query is complex, and in many cases the results will be correct. However, in this state it's possible that the server will return incomplete results. If you wish to use MongoDB alone to analyze large data sets, then set maxVQLWindowSize to some arbitrarily large number. Also be aware of the globalMongoTimeout setting, which controls the maximum amount of time a query may process.| Setting Name |
Discussion
|
elasticSearchServer |
The connection string to Elasticsearch. This is always a web address, for example,
http://192.168.1.2:9200. It should include the port number on which Elasticsearch is listening, unless that port is the default port for the given protocol (80 for HTTP and 443 for HTTPS). It should not include a path. If your Elasticsearch deployment is configured to use authentication, then supply the name and password as HTTP basic authentication parameters in URL form. For example, https://username:password@myserver.org:9200. |
elasticReconnectTimeout |
A human interval like
30 seconds. The time after which the server will attempt to reconnect to Elasticsearch when a connection fails to be established. Default: 30 seconds. |
esIndexExtensions |
Should xAPI extensions be included in the Elasticsearch mapping? Default:
true. Because xAPI allows arbitrary data to be included in extensions, it is possible to generate data that Elasticsearch cannot ingest. This can happen when extensions change the data type at a particular path, such as using a string in some statements, but an integer in others. In these cases, Elasticsearch will drop the data. This can lead to large elasticMissingRatioError values. Eventually, if too much data fails to be stored in this way, then the LRS will assume the Elasticsearch index is "unhealthy" and refuse to use it. |
elasticTimeout |
A human interval like 30 seconds. The maximum amount of time the LRS will wait for a response from Elasticsearch. Requests longer than this time will be canceled. Default: 20 seconds. When such a request times out, downstream effects will occur. You may experience dashboard graphs disappear or render the "No data to display" error message. |
elasticMissingRatioError |
A number between
0 and 1. Defines the ratio of the count of statements between Elasticsearch and MongoDB that is considered normal. Default: 0.99. This means that by default, an Elasticsearch index containing 99% of the MongoDB statements is healthy enough to use. While it may be tempting to set this value to 1.0 for maximum consistency, when under load statements are always stored in MongoDB before Elasticsearch. This can lead to a situation where Elasticsearch never has the same count as MongoDB, because of the ongoing traffic. Lower this ratio if, under high load, you see a notification describing the index as unhealthy. |
esDynamicExtensions |
When the LRS encounters xAPI extensions, if
esIndexExtensions is true, then how are they treated? Default: true. Use true for regular Elasticsearch dynamic mapping or runtime to use runtime mapping. A discussion of the ramifications of each selection is beyond the scope of this document. |
esKeywordMaxLength |
A number. Strings beyond this length will be truncated in the mapping. Default:
256. Increase this value if you have identifiers that are very long. Too short a value can lead to different xAPI objects, agents, or activities to be considered the same when their IDs differ. |
It looks like this server does not have an Elasticsearch connection. While optional, an Elasticsearch connection is highly recommended.
The analytics index for this LRS seems to be missing data. If this persists for more than a few minutes, please use the database management page to rebuild the analytics index.
The analytics index was built with a previous version of the LRS and needs to be rebuilt. Please use the database management page to rebuild the analytics index.