icinga Product Support Model ?
Software Cycle for infra?
Regular Release by Developers form ICINGA?
When was the Last release?
How frequently do they release updates?
Justification , why every Server need internet Connection?
What kind of Certificate used in ICINGA at the time of installation?
How the Server-Server communication happens?
do we have Container Concept in ICINGA?
User in ICINGA , are they from Application layer/OS layer? Application layer
Clarification on Replication Bi-directional/unidirectional for DB,LB,WEB?
Who will support for infra? apac-infra team
would like to know about iCinga Certificate processing
would like to know about iCinga product support
Is Icinga a well-maintained software?
Are there regular/frequent product release & patch release plans from the original software developer(s)?
What’s its release history? Are bugs (esp. security-related) being fixed swiftly?
Icinga uses other FOSS software (e.g. PostgresQL, Apache web server). Can Icinga support newer versions of these software? Or does Icinga have very tight integration with these software and does not support discrete installations?