Unassigned shard in "nagioslogserver_history" index

[Shuster]

I have a single-instance deployment of v2.1.15. After setting up alerts, I noticed that the cluster status went from "green" to "yellow." This appears to be due to an unassigned shard in the "nagioslogserver_history" index. Trimming the index resets the cluster status to green, but it reverts to yellow as soon as an alert runs. Any thoughts on why this is happening?

"nagioslogserver_history" : {
"status" : "yellow",
"number_of_shards" : 1,
"number_of_replicas" : 1,
"active_primary_shards" : 1,
"active_shards" : 1,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 1

[danderson]

Thanks for reaching out @Shuster,

If you reference this link here:
https://support.nagios.com/kb/article/n ... h-469.html
I think what is happening is by default, a single instance will always be yellow.

Let me know if this answers your questions.

[Shuster]

Thanks for reaching out @Shuster,

If you reference this link here:
https://support.nagios.com/kb/article/n ... h-469.html
I think what is happening is by default, a single instance will always be yellow.

Let me know if this answers your questions.

Thank you for your response! Prior to enabling alerts, I was able to achieve green status by following the guide below. But the workaround doesn't seem to be effective for the nagioslogserver_history index.

https://assets.nagios.com/downloads/nag ... oyment.pdf