after searching how it can be integrated with the inciga checks, the simplest way I have found is to create a script that periodically query logstash to get the statistics and return this status in this cases:

• GREEN: neither non_retryable_failures, with_errors or failures fields founds on the json
• WARNING: failures field found
• CRITICAL: non_retryable_failures or with_errors field found

Build has FAILED

rebase

• Set SSO Session Idle to one week

I have simulated different situations locally on the vagrant environment:

root@logstash0:~# curl -s http://localhost:9600/_node/stats/pipelines | jq '.pipelines.main.plugins.outputs'
[
  {
    "id": "c49a6902391a456022af4c89f0972781900d01d70cd5f312b292cb20c0d345eb",
    "documents": {
      "non_retryable_failures": 112,
      "successes": 103692
    },
    "events": {
      "out": 103804,
      "in": 103804,
      "duration_in_millis": 3529049
    },
    "name": "elasticsearch",
    "bulk_requests": {
      "responses": {
        "200": 2028
      },
      "failures": 3,
      "with_errors": 110,
      "successes": 1918
    }
  }
]

It starts well. The build is stuck [1]

In D5704#144807, @zack wrote:

Why 6 hours and not, say, 1 week or even 1 month?
It is very common these days to remain connected for that long, and the UX in having to relogin often is a lot worse.

Why 6 hours and not, say, 1 week or even 1 month?
It is very common these days to remain connected for that long, and the UX in having to relogin often is a lot worse.

Build has FAILED

rebase

Build has FAILED

Make the number of (single-object insertion) retries configurable

LGTM

Build is green

thanks, adapted.

Adapt according to review

Build is green

rebase

Looks good to me.

failures are unrelated

• split procedure per firewall
• clarify the initial status before each section
• fix minor typos

Build is green

Rebase

upgrade done without any problem:

• CARP maintenance activated on pushkin -> glyptotek elected as primary
• pushkin upgrade done
• CARP maintenance deactivated on pushkin -> pushkin re-elected as primary
• nothing wrong detected after a safety period of 1 hour
• CARP maintenance mode activated on glyptotek to avoid an unexpected rebalance during the upgrade
• glyptotek upgrade done
• CARP maintenance mode deactivated on glyptotek

Build is green

Rebase and improve if condition

Looks good to me !

thanks

Build is green