How to Read Your Healer Logs in Mythic+

"How do I actually read my healer logs?" is one of those questions that resurfaces on r/CompetitiveWoW every few months with no satisfying answer in the replies - usually a handful of "just look at your parse" comments that don't actually explain anything. Parse percentile and HPS are the numbers Warcraft Logs puts in front of you first, so they're the numbers people fixate on. They're also close to useless for figuring out whether you actually healed well.

Why parse % and HPS don't tell you much

Your parse percentile ranks your log against other players of your spec on that same boss or key-level bracket, within the current ranking partition - it's a measure of how your effective throughput compares to other healers playing your spec who logged that content, not a measure of whether you played your kit well. The pull where the tank stood in everything and the group needed constant AoE healing is the one that earns a green parse. A clean pull where nobody took avoidable damage gives you far less to heal, and ranks you lower for it.

HPS (healing per second) is effective healing per second. Warcraft Logs excludes overheal from it, so a heal thrown at someone already at full health adds essentially nothing to the number - HPS is not a count of everything you cast. The reason it still doesn't tell you much is a different one: how much healing there was to do is mostly a fact about the pull rather than about you. Damage taken sets the ceiling, so a group that stands in things hands its healer a bigger number, whoever is in the slot.

It also says nothing about when. Two healers with identical HPS can differ completely in whether a major cooldown landed on the pull that actually needed it. And the healing that works best barely shows up at all: a dispel that lands before the damage does, a mechanic answered, a group kept out of the pool in the first place. Every one of those lowers your HPS. A healer who prevents damage instead of repairing it posts a smaller number and is playing better.

That is also why group composition and pull difficulty move both numbers around run to run. A well-played key with a strong group needs less healing than a scrappy key that's barely staying alive, so the same healer can post very different HPS numbers in two runs where their actual play didn't change. None of this means parse and HPS are meaningless - they're just answering a different question ("how much did I heal, relative to everyone else") than the one most people actually want answered ("did I play my healer well").

What to check instead

1. HoT / maintenance buff uptime

For HoT-based specs, uptime - the percentage of active combat time that a HoT is active on at least one target - is a much better signal than throughput. It's measured against combat time, not raw fight time, so downtime between pulls doesn't drag the number down artificially. A HoT that keeps dropping and getting reapplied from scratch is worse than one that's refreshed just before it expires (a "pandemic" refresh), because the refresh preserves part of the remaining duration instead of resetting it.

2. Overhealing %

Every heal event reports both the healing that actually landed and the healing that "overhealed" - exceeded the target's missing health. Overheal % is the share of your total raw healing that was wasted this way. It's not automatically bad (some overheal is unavoidable when healing through burst damage), but a healer with persistently high overheal relative to others at the same key level is probably casting reactively instead of reading the fight.

3. Mana management

Three things matter here: your average mana % across the fight, whether you went fully OOM at any point (a binary failure signal, not a gradient), and your mana efficiency - effective healing produced per point of mana spent. Going OOM mid-key is one of the more diagnostic problems in a log, because it usually means either your rotation is too mana-hungry for the pace of the key or you're casting more than the pull actually required.

4. Boss-mechanic response

This is the one thing no throughput number captures at all: did you use the right tool before a dangerous mechanic landed, not just react to the damage afterward? Pre-casting a HoT or popping a cooldown a few seconds ahead of a known burst mechanic is the difference between smoothing out the damage and playing catch-up for the rest of the pull.

5. Interrupts and dispels

Depending on your spec, you're also expected to help with interrupts on priority casts and dispel dangerous debuffs. A missed interrupt that leads to a damage spike will tank your healing numbers for reasons that have nothing to do with your healing - it's worth checking whether a "bad" HPS moment in the log was actually a missed interrupt from someone else in the group.

What "good" looks like - percentiles, not pass/fail

None of the metrics above have a single universal target. What counts as strong Lifebloom uptime at a +15 is a different number than at a +25, because higher keys demand more active healing and change how much uptime is realistically achievable. The useful comparison isn't against a fixed threshold someone posted in a Discord once - it's against real logs from top performers at your key level, in your dungeon.

That's the whole idea behind Healper's performance score: instead of grading you against an arbitrary number, it compares your HoT/buff uptime, mana management, and overhealing against percentile distributions built from real top-performing logs, stratified by dungeon and key level bracket, then layers in how you responded to that dungeon's specific dangerous mechanics.