Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Heartbeat] Add timeout to browser monitors in HB side #32388

Closed
emilioalvap opened this issue Jul 18, 2022 · 2 comments · Fixed by #32434
Closed

[Heartbeat] Add timeout to browser monitors in HB side #32388

emilioalvap opened this issue Jul 18, 2022 · 2 comments · Fixed by #32434
Assignees
Labels
bug Team:obs-ds-hosted-services Label for the Observability Hosted Services team

Comments

@emilioalvap
Copy link
Collaborator

emilioalvap commented Jul 18, 2022

Describe the enhancement:

Add a configurable timeout for synthetic monitors, in case node process goes unresponsive. This timeout will be used from HB to kill synthetic monitor's in case node goes unresponsive, as seen in #32387. HB will wait for node process to exit and will proceed to kill it with SIGKILL if it doesn't do it before timeout is reached.

Additionaly, a sensible default should be used so this timeout can kick in before container eviction timeout inside synthetics service. @andrewc suggested ~14 min.

ACs:

  • Timeout is configurable from heartbeat.yml.
  • Test run is marked as failed if timeout is reached and appropriate summary is included in the monitor run.
@emilioalvap emilioalvap added enhancement Team:obs-ds-hosted-services Label for the Observability Hosted Services team labels Jul 18, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/uptime (Team:Uptime)

@vigneshshanmugam
Copy link
Member

POST FF testing LGTM
Screen Shot 2022-08-01 at 11 42 40 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Team:obs-ds-hosted-services Label for the Observability Hosted Services team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants