Create Indices on custom interval instead of daily

[kunalekawde]

Hello Team,
Wanted to know if there is a way to create indices for custom interval instead of daily?

We have an issue where, when the daily index is created for jaeger-search, it's missing some of the services (although spans for these services are received by collector). If the collector pod is restarted, services get added to the index correctly.
To debug this, we want to lower the daily index creation to hours may be to reproduce quickly.

Thanks

[dosubot[bot]]

Hello @kunalekawde! 👋 I'm here to assist you with any bugs, questions, or contributions you have. Let's squash those bugs together!

Yes, you can create indices for a custom interval such as hourly in Jaeger. You can achieve this by setting the es.index-rollover-frequency-services and es.index-rollover-frequency-spans options to "hour". This will rotate the Jaeger service and span indices over an hourly period, creating indices like "jaeger-service-yyyy-MM-dd-HH" and "jaeger-span-yyyy-MM-dd-HH" ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[dosubot[bot]]

The valid values for the es.index-rollover-frequency-services and es.index-rollover-frequency-spans settings in Jaeger are hour and day. Setting the frequency to minutes is not supported ^[1][2].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[kunalekawde]

@dosu I set the frequency to hour and see that jaeger-service index is not getting generated (only if collector pod is restarted, the jaeger-service index is created), jaeger-span is getting generated, how to debug ? Logs are not providing information.

[dosubot[bot]]

To debug the issue where the jaeger-service index is not being generated hourly, you can try the following steps:

1. Verify Configuration: Double-check that the es.index-rollover-frequency-services is correctly set to "hour" in your configuration and that the Jaeger collector pod has been restarted after making this change.

2. Check Collector Logs: Although you mentioned that logs are not providing information, ensure that the logging level is set to a more verbose level, such as DEBUG, to capture more detailed logs. This might provide insights into any issues during index creation.

3. Elasticsearch Connectivity: Ensure that the Jaeger collector has proper connectivity to Elasticsearch and that there are no issues with permissions or network connectivity that might prevent index creation.

4. Elasticsearch Rollover Settings: Check if there are any specific rollover settings or policies in Elasticsearch that might affect the creation of the jaeger-service index. Ensure that these settings are compatible with the hourly rollover configuration.

5. Resource Availability: Ensure that there are sufficient resources (CPU, memory) allocated to the Jaeger collector pod, as resource constraints might affect its ability to perform operations like index creation.

If these steps do not resolve the issue, consider checking for any known issues or limitations in the version of Jaeger you are using that might affect hourly index creation for jaeger-service indices.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[kunalekawde]

@dosu How to create static index for jaeger-service such that it never rolls over at day mark ?

[dosubot[bot]]

Jaeger does not natively support setting a static index name that never rolls over for jaeger-service. By default, Jaeger uses daily indices, and rollover can be managed using Elasticsearch's rollover feature or Index Lifecycle Management (ILM) policies. However, if you want to maintain a static index that doesn't roll over, you would need to manage this manually in Elasticsearch by creating a custom index and configuring your Jaeger setup to write to this index without using the rollover or ILM features. This approach would require careful management of data retention and performance implications, as a static index could grow indefinitely without rollover policies.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}