Arsenal got the win they needed on Wednesday, but the more immediate concern was not the 2-1 result over Slavia Prague. It was Ezri Konsa, who was seen holding his knee and limping before being taken off just past the hour-mark.
That kind of substitution tends to matter more when a player has already become central to the rhythm of a team. Konsa has logged over 1,000 minutes across all competitions this season, so any fitness problem is worth attention even if the first signs of the issue looked manageable.
What happened to Konsa
Konsa lasted 62 minutes before Mikel Arteta decided to remove him. After the match, Arteta said Konsa had some issues and that Arsenal chose to take him off. He also noted that Konsa has been playing a lot, with so many games in the last few weeks.
The timing adds another layer to the concern. Before Saturday's clash with Hull City, Konsa is expected to undergo further testing, and Arsenal have one more match left before the November international break. That gives the club a little room to breathe, but it does not remove the uncertainty.
Why the timing matters
This is not just about one night in the Champions League. In August, before Ezri Konsa completed his transfer from Aston Villa, Arsenal played two matches that he did not appear in. Since then, he has become a high-use part of the squad, and the workload has clearly stacked up.
For Arsenal, the best-case scenario is that the issue is minor and the two-week break offers enough time for recovery if needed. The worst-case scenario is that a player who has been heavily used all season now needs a reset right before the schedule offers one. Either way, the next update on Konsa will matter more than the scoreline did.
