Could you provide any reason why this is a must feature? Simply for checking on what is running you can see which neighbour runs on which area, and area is tied to instance, so in theory there is no need for separate state for instance.
I use the state in my script Visualize OSPF state via LEDs.
Fine with the change, just wanted an official confirmation this is expected. I will update my script then.
Well, this is more complicated than I thought...
An instance can have several areas, an area can have several neighbors. So I have a evaluation this in a loop, right?
Yes you need to lop through the neighbours and areas. But we will add in one of the next versions a flag for the instance that will show running state if there is at least one active OSPF neighbour.