On this Page

MetricsHub
MetricsHub Community Connectors 1.0.22

afterAll (Section)

When To Use

Use afterAll for teardown work that should run once at the end of the connector cycle.

Typical use cases:

  • Session logout.
  • Temporary resource cleanup.
  • Finalization calls that should not be repeated per monitor.

Syntax

afterAll:
  logout:
    type: http
    method: delete
    path: /rest/login-sessions/current
    resultContent: http_status

Properties

Property Required Default Description
afterAll Yes None Object containing named sources executed after monitor tasks.
<sourceName> Yes None Standard source definition (http, commandLine, etc.).
  • Keep actions idempotent so retries are safe.
  • Prefer lightweight status checks (resultContent: http_status) for cleanup calls.
  • Avoid dependencies on monitor output unless strictly needed.

Common Mistakes

  • Running heavy collection logic in afterAll.
  • Building teardown logic that fails if called twice.
  • Assuming afterAll output is part of monitor mappings.

Examples

No current community connector uses afterAll.

Note

afterAll is fully supported and useful for modern REST connectors with explicit login/logout flows.

afterAll connector lifecycle cleanup metricshub community connector hardware system
Searching...
No results.