LogicMonitor vs SolarWinds
Who this is for
If you're weighing LogicMonitor against SolarWinds in Observability, this page is for you. It puts the facts from both Techarda profiles side by side, with each company's recent stories and any community threads that name them both. It doesn't pick a winner: the questions further down come from our evaluation guide, so you can put the same ones to both.
Stories and counts cover the last 90 days, counted on 23 Oct 2026. Profiles last updated 28 Sept 2026. Want a different line-up? The interactive compare tool takes up to four companies.
The facts side by side
From each company's Techarda profile. Categories they share are marked, with each company's position in the category's leader list.
| LogicMonitor | SolarWinds | |
|---|---|---|
| Founded | 2007 | 1999 |
| Headquarters | Santa Barbara, California, USA | Austin, Texas, USA |
| Parent company | Not listed | Turn/River Capital, since 2025 |
| Categories |
|
|
| What they do | LogicMonitor is a SaaS observability company whose LM Envision platform monitors hybrid IT infrastructure, including networks, servers, cloud services, containers, applications and logs, with AI-driven event correlation through its Edwin AI product. It serves enterprise IT and operations teams and managed service… | SolarWinds is an IT management and observability software company headquartered in Austin, Texas, founded in 1999. It sells SolarWinds Observability for SaaS and self-hosted environments, Network Performance Monitor, Server & Application Monitor, Database Performance Analyzer and service desk software. In 2025… |
| Official site | logicmonitor.com | solarwinds.com |
| Stories, last 90 days | 22 | 27 |
Recent stories from each
What each company has published in the last 90 days, newest first. Each story links to the original source.
How to choose between them
We don't score or rank these two. The questions below come from our Observability evaluation guide, and they work best when you put each one to both companies and compare the answers side by side.
Open collection and data portability
Instrumentation is expensive to redo. Collecting through an open standard keeps the option of changing backends later.
Ask both: Do you accept OpenTelemetry data with no loss of features, which features need your own agent, and can we export raw data, dashboards and alert rules?
Cost as data grows
Pricing by host, by gigabyte ingested, by event or by user behaves differently as you scale. Surprises usually come from logs and high-cardinality metrics.
Ask both: At our current volumes, what would we pay this year and at twice the volume, and which controls let us cut ingest without losing what we need?
Query speed during an incident
When something is down, a query that takes minutes costs money and patience. Speed over long time ranges matters most exactly when it is hardest to deliver.
Ask both: How fast do typical queries return at our data volumes over the last day and the last month, and is older data slower or charged again to query?
Correlation across signals
Jumping between separate tools for logs, metrics and traces slows every investigation down.
Ask both: How do you link a slow trace to the related logs, metrics and deployment, and does that work for services instrumented with OpenTelemetry?
Alert quality
Noisy alerts train people to ignore them. The platform should help you alert on the symptoms users feel.
Ask both: How do you support service level objectives and alerting on them, and what helps us find and remove noisy alerts?
Investigation help from AI
An assistant that restates the dashboard adds nothing. One that narrows down the cause on your own data saves real time.
Ask both: Can we replay two of our past incidents through your assistant during the trial, and what data does it send to which models?
Sensitive data and access control
Logs often contain personal data, tokens and customer identifiers, and everyone with query access can see them.
Ask both: How do you detect and mask sensitive data at ingest, control access by team or data type, and set retention for each data set?
Retention and archiving
Audit, security and regulatory needs can require keeping data far longer than operations needs it, which changes the cost.
Ask both: What retention options do you offer, can we archive to our own storage and bring data back later, and what does bringing it back cost?
The guide also lists red flags to watch for in any Observability vendor, and how to build a shortlist.
Keep going
Each profile has the full detail, and the alternatives pages show who else sits in the same categories.
How this page is put together
Every fact comes from the two Techarda profiles, which our editors check against each company's own site and public records. Rows are left out when neither profile has the detail. Stories are the ones each company published in the last 90 days; review counts include published, moderated reviews only.
Something wrong or out of date? Email engage@techarda.com. Used one of them in production? A short review of LogicMonitor or SolarWinds helps the next team decide.