This topic provides answers to some frequently asked questions (FAQ) about the Elasticsearch-compatible API of Simple Log Service. This topic also describes the common errors and how to troubleshoot the errors.
This topic is proprietary information of Alibaba Cloud, and describes the capabilities that are provided by Alibaba Cloud to interact with third-party services. Therefore, the names of third-party companies and services may be referenced in this topic.
FAQ
Q: Does Elasticsearch need to perform index rollovers when I call an Elasticsearch-compatible API operation?
A: No. In most cases, Elasticsearch rotates indexes every day to generate new indexes. This prevents the size of an index from being too large. The capacity of a Simple Log Service Logstore is large. Elasticsearch does not need to perform index rollovers.
Common errors
Error message | Description | Solution |
index config doesn't exist | The indexing feature is not enabled for the specified Logstore. | Create indexes for the Logstore and configure field indexes for the fields that you want to analyze. For more information, see Create indexes. |
xxx is not configed in index | The field indexing feature is not enabled for the xxx field in Simple Log Service. | Configure field indexes for the fields that you want to analyze. For more information, see Create indexes. |
logstore xxx does not exist" | The specified Logstore does not exist. | Check whether the name of the index pattern in Elasticsearch is valid. You must specify a name in the |
please set user/password, use Aliyun accessKeyId/accessKeySecret as user/password | The authentication failed. | Check whether the UserName and Password parameters in BasicAuth are valid when you call an Elasticsearch-compatible API operation. |