Integration

SolarWinds Observability integration

SolarWinds Observability SaaS public API: search the entities the platform monitors, list metric definitions and pull their measurements, search log events and list log archives, inspect synthetic website checks with their outage history and individual test results, list the synthetic probe locations, record a change event on the timeline and list the configured integrations. The credential carries the data centre region so the tools reach the right host.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SolarWinds Observability.Built from the 18 SolarWinds Observability tools below, on the connection you add once.

Common SolarWinds Observability use cases

  • charting CPU over the last day
  • building a monthly uptime report
  • cleaning up an obsolete derived metric
  • discovering which metric name to chart
  • investigating an incident by error text
  • checking whether a host is in maintenance
  • finding which region is seeing slow responses
  • auditing which technologies are being collected
  • choosing a valid type before searching entities
  • reporting the current status of a monitored site

What you can do with SolarWinds Observability

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Metric, 5 operations

  • create_composite_metricCreate composite metricPOSTCreates a metric whose values are computed from a PromQL formula.
  • delete_metricDelete metricDELETEDeletes a metric definition by name.
  • get_entity_type_metricsGet entity type metricsGETLists the metric definitions that entities of a given type report.
  • get_metricGet metricGETReads a single metric definition, including its unit and last reported time.
  • list_metricsList metricsGETLists metric definitions with their units and descriptions.

Entity, 2 operations

  • get_entityGet entityGETReads a single monitored entity, including its health state and attributes.
  • search_entitiesSearch entitiesGETSearches monitored entities by type, name or free text.

Change event, 1 operation

  • create_change_eventCreate change eventPOSTRecords a deployment, configuration change or other event on the timeline.

Entity type, 1 operation

  • list_entity_typesList entity typesGETLists the entity type names accepted by the entity search.

Integration, 1 operation

  • list_integrationsList integrationsGETLists configured integrations with their type, parameters and matched entities.

Log archive, 1 operation

  • list_log_archivesList log archivesGETLists log archive files, each with a download URL.

Log event, 1 operation

  • search_logsSearch logsGETSearches log events by text, group or entity over a time window.

Measurement, 1 operation

  • get_metric_measurementsGet metric measurementsGETReads time series or scalar measurements for one metric, grouped by attribute.

Metric attribute, 1 operation

  • list_metric_attributesList metric attributesGETLists the attribute names a metric carries, for use in groupBy or filter.

Outage, 1 operation

  • list_website_outagesList website outagesGETLists the up, down, maintenance and paused periods of a website check.

Probe, 1 operation

  • list_probesList probesGETLists the synthetic probe locations that run website and URI checks.

Test result, 1 operation

  • list_website_test_resultsList website test resultsGETLists per-probe synthetic test results with response time and failure phase.

Website, 1 operation

  • get_websiteGet websiteGETReads a synthetic website check with its URL, status and last test times.

Use SolarWinds Observability from Claude Code, Cursor or Codex

Connect SolarWinds Observability in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SolarWinds Observability operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SolarWinds Observability

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect SolarWinds Observability once

    Add your SolarWinds Observability connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

SolarWinds Observability integration FAQ

What can you do with the SolarWinds Observability integration?

LiveContext exposes 18 operations on SolarWinds Observability, covering metric, entity, change event and entity type. Common uses include charting CPU over the last day, building a monthly uptime report and cleaning up an obsolete derived metric.

Popular integrations

Browse the whole catalog