Simple Log Service:How do I reduce index traffic fees?

The following methods help reduce index traffic fees in Simple Log Service. For more information, see Create indexes.

• Disable the full-text indexing feature and configure field indexes.

  Simple Log Service supports both full-text indexes and field indexes.

  • If you configure full-text indexes, all field names and field values are stored as text, and both are included in the index traffic. Field names and field values form key-value pairs.

  • If you configure field indexes of the long or double type, the field names are not included in the index traffic, and each field value is counted as 8 bytes. You can use field indexes to reduce index traffic fees. Examples:

    • If you configure an index of the text type for the request_uri field and the field value is /request/path-2/file-7, the string request_uri and the value /request/path-2/file-7 are both included in the index traffic.

    • If you configure an index of the long type for the status field and the field value is 400, the string status is not included in the index traffic, and the value 400 is counted as 8 bytes in the index traffic.

• Configure indexes only for important fields.

  If raw logs contain many fields but only some are used for queries and analysis, configure indexes only for those fields.

• Disable LogReduce.

  Enabling LogReduce increases the total index traffic by 10%. The following table provides examples.

  Size of raw logs	Index percentage	Size of index traffic generated by LogReduce	Total index traffic
  100 GB	20% (20 GB)	100 GB×10%	30 GB
  100 GB	40% (40 GB)	100 GB×10%	50 GB
  100 GB	100% (100 GB)	100 GB×10%	110 GB

  If you no longer need LogReduce, disable it as soon as possible. For more information, see LogReduce.