samz-github opened a new issue, #9750: URL: https://github.com/apache/skywalking/issues/9750
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar feature requirement. ### Description In my cooperation, we use skywalking to monitor high traffic microservice. Now everyday there are almost elasticsearch 2TB storage size only for the segment index. And it will be grow more storage size as more related microservices are added to Skywalking system. For now, 2TB in only 1 segment elasticsearch index is too big. It will be better if Skywalking can support fine grained segment index for each monitored microservice but not only 1 segment index each day. ### Use case For example, we use skywalking monitor three microservices: account-svc, payment-svc, product-svc. For now, each day there is 1 segment elasticsearch index to store the Skywalking segment records, index name: sw_segment-20221010, 2TB size for this index. It will be good if skywalking can divide this index to three indices: sw_segment-account-svc-20221010, sw_segment-payment-svc-20221010, sw_segment-product-svc-20221010. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
