Possible too short Request Timeout in vmware.health.get due to slow vCenter call

XMLWordPrintable

    • Type: Change Request
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      OS: Rocky Linux 8
      DB: PostgreSQL 15.13 + TimescaleDB 2.19.3
      vCenter 8.0.3.00500/00600
      VMware FQDN Template 7.0-2 (latest)

      Steps to reproduce:

      Setup a vCenter with at least one host, certain conditions may make this vCenter slower than others.

      Result:

      Get Overall Health VC State / vmware.health.get

      Shows one of the two following errors:

      {"health":6,"error":"Failed to get data from API:Error: script execution timeout occurred"}

      {"health":"","error":"Failed to get data from API:Error: cannot get URL: Timeout was reached."}

       

      While debugging this, I discovered that the get_version function (/rest/appliance/system/version) takes 6500ms instead of 160ms on certain systems.

      As far as I understand it the HttpRequest function uses the global timeout.

      Expected:

      Normal data ingest for this item

       

      Overall it would be great if the HttpRequest timeout could be either decoupled or a less used global timeout being used. Increasing the global one unneeded for many other (~500.000) items might not be the best idea.
      Using a seperate proxy might also be an option right now.

       

      Thank you for considering.

            Assignee:
            Unassigned
            Reporter:
            Lukas Magauer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: