humanloop.com No paid content found

LLM observability is the practice of capturing, tracing, and evaluating every model and agent run so you can see what your application actually did — not just whether it was up. It matters when you run multi-step agents, route across multiple models, or ship prompt changes regularly, because uptime and error-rate dashboards won't tell you why an answer was wrong or which step burned the tokens. If your application is a single stateless prompt with no tool calls, basic logging may be enough; the more steps, models, and tools involved, the more you need structured traces and evals.

Observability vs. traditional monitoring

Traditional monitoring answers "is the service responding?" LLM observability answers "what happened inside this run, and was the output any good?"

The two are complementary. You still want uptime and latency alerting; observability adds the layer that explains output quality.

Core signals to capture

Instrument at the level of the individual model call and the surrounding workflow step, then roll up. The signals worth capturing on every run:

• Prompts and completions — the actual input sent and output returned, including system messages and any retrieved context.
• Latency — per call and per span, so you can separate model time from tool time from your own code.
• Token cost — input and output tokens per call, attributed to a model, a feature, or a user.
• Tool calls — which tools were invoked, with what arguments, and what came back.
• Errors — provider errors, timeouts, malformed tool arguments, and schema validation failures.

Capturing prompts and completions is what makes debugging possible; capturing cost and latency per span is what makes optimization possible.

How tracing connects multi-step agent workflows

A single trace represents one end-to-end run. Inside it, each step is a span: a model call, a retrieval, a tool invocation, a routing decision. Spans nest, so a parent span for "answer user question" can contain child spans for "retrieve documents," "call model," and "call calculator."

That structure is what lets you trace a failure to a specific step. If the final answer is wrong, the trace shows whether retrieval returned irrelevant documents, whether the model ignored them, or whether a tool returned an error that the agent silently swallowed. Without spans, you only see the bad final output and have to guess.

For agents that route across multiple models — for example, sending easy requests to a cheaper model and hard ones to a stronger model — the trace should record which model handled each call. Respan describes itself as an AI router with built-in observability and automated evals, which is the pattern to look for: routing decisions and observability data captured in the same place, so you can compare cost and quality across the models you route between.

Turning traces into quality signals with evals

Traces tell you what happened; evals tell you whether it was good. Automated evals score runs — against reference answers, rubrics, or model-based judges — and attach those scores to the trace. Over time, that gives you a quality trend line you can compare across prompt versions, model versions, and releases.

The practical loop:

1. Capture traces for every run.
2. Score a sample (or all) of them with automated evals.
3. Compare scores across prompt or model changes.
4. Ship the version that scores best, and keep monitoring after release.

This is why "ship the version that scores best" and "know the moment things change" belong together: evals give you the comparison, and continuous monitoring tells you when a previously good version starts degrading — for example, after a provider silently updates a model.

What to check when observability data looks wrong or missing

If traces are incomplete or scores look off, work through these common causes:

• Uninstrumented calls. A code path that calls a model directly, bypassing your gateway or SDK wrapper, produces no span. Audit for direct provider clients.
• Dropped spans. Async or background work that finishes after the parent run closes can lose its span. Check that spans are flushed before the trace is finalized.
• Missing context. If prompts are logged but retrieved documents aren't, you can't tell whether a bad answer came from bad retrieval. Instrument retrieval as its own span.
• Sampling gaps. If you sample traces, make sure eval scores and cost totals account for the sampling rate rather than reporting sampled numbers as totals.
• Clock and ordering issues. Out-of-order timestamps make latency attribution misleading; verify timestamps come from a consistent source.

Choosing what to instrument first

Start with the signals that map to decisions you actually make. If you're optimizing cost, instrument tokens and model routing per call. If you're debugging quality, instrument prompts, completions, retrieval, and tool calls, and add evals. If you're managing reliability, instrument errors and latency per span. A platform that combines routing, tracing, and automated evals — as Respan positions itself — reduces the work of stitching those layers together, but the signals above are what you need regardless of which tool provides them.

Artificial insemination (AI) with frozen semen lets you breed a Connemara mare to a stallion that may be standing hundreds or thousands of miles away — or no longer alive. The trade-off is that frozen semen demands much tighter management than natural cover or fresh/chilled semen. In practice, you need a veterinarian experienced in equine reproduction, precise monitoring of the mare's cycle, and realistic expectations about success rates. This article walks through what actually happens, step by step, and helps you judge whether AI is the right route for your breeding plan.

What "AI with frozen semen" actually means

AI is simply placing semen into the mare's reproductive tract by instrument rather than by natural cover. The semen itself comes in three broad forms:

• Fresh: collected and used within hours.
• Chilled: extended and shipped, typically used within 24–48 hours.
• Frozen: processed with cryoprotectants and stored in liquid nitrogen, potentially for years.

Frozen semen is the most logistically flexible and the most biologically demanding. The freezing and thawing process kills a large proportion of sperm cells, and the survivors have a shorter functional lifespan in the mare's tract than fresh sperm. That is the single most important fact to understand before you commit.

The basic steps, in order

1. Confirm the mare is a suitable candidate

Before anything else, a reproductive examination is worthwhile. A vet typically checks:

• General health and body condition
• Reproductive tract via ultrasound and/or speculum exam
• Cervical and uterine status
• Any history of previous foaling or breeding problems
• Uterine culture or cytology if infection is suspected

Older mares, mares with a history of endometritis, or mares that have never conceived are all higher-risk. This does not rule them out, but it changes the odds and the level of veterinary input required.

2. Source the frozen semen

Frozen Connemara semen is available from some studs and via semen banks, though the pool is smaller than in warmblood or Thoroughbred breeding. When enquiring, ask for:

• Stallion registration details and studbook
• Number of doses available per breeding
• Post-thaw motility figures (a quality indicator, not a guarantee)
• Breeding contract terms, including live foal guarantees if offered
• Shipping and storage arrangements for the liquid nitrogen dewar

If you are breeding for a registered Connemara foal, check the relevant studbook's rules on AI and on frozen semen specifically. Registration bodies differ in what they accept and what documentation they require from the stallion owner.

3. Monitor the mare's cycle closely

This is where frozen semen differs most from natural cover. Because thawed sperm survive only a short time, insemination must happen very close to ovulation — often within a window of roughly 12 to 24 hours before or around ovulation, depending on the protocol your vet uses.

Typical monitoring involves:

• Teasing with a stallion or a reliable teaser to detect oestrus
• Ultrasound scanning every 24–48 hours once the mare is in season
• Tracking follicle size to predict imminent ovulation
• Possible ovulation induction with a hormone injection to tighten the timing

Some vets also use deep-horn or hysteroscopic insemination, which places a small volume of semen directly at the tip of the uterine horn. This can improve results with low-dose or poor-quality frozen samples, but it requires specialised equipment and skill.

4. Thaw and inseminate

Thawing follows the semen processor's instructions exactly — usually a specific water bath temperature and time. Deviating from the protocol damages sperm. The insemination itself is quick and is performed by the vet.

5. Post-breeding management

Depending on the mare's history, the vet may recommend:

• Oxytocin treatment to help clear fluid from the uterus
• Anti-inflammatory medication
• A post-breeding scan to confirm ovulation and check for fluid

Pregnancy is normally confirmed by ultrasound around 14–16 days after ovulation, with a follow-up check later to monitor the pregnancy.

Why timing is the hard part

With natural cover, sperm can remain viable in the mare for a day or more, so a slightly mistimed breeding still has a chance. With frozen semen, that buffer largely disappears. If you inseminate too early, the sperm are gone before the egg arrives. Too late, and the egg has already aged.

This is why frozen semen breeding is often described as a timing exercise as much as a fertility one. It also explains why success rates vary so widely between mares, cycles, and clinics. Published per-cycle pregnancy rates for frozen semen in horses are generally lower than for fresh or chilled semen, and outcomes depend heavily on mare fertility, semen quality, and the skill of the team managing the cycle.

Practical considerations before you decide

Questions to ask yourself

• Do I have a vet with equine reproduction experience nearby? Without one, frozen semen AI is impractical.
• Can I commit to frequent scanning appointments? Cycles can require several visits over a few days.
• Is the stallion I want only available frozen? If a suitable stallion is available fresh or chilled, that is usually the easier path.
• What does the studbook require? Confirm AI and frozen semen are accepted and what paperwork is needed.
• What is my budget for a possibly repeated process? Frozen semen breeding can take more than one cycle.

When AI makes sense — and when it doesn't

AI with frozen semen is a reasonable choice when:

• The stallion you want is geographically distant, deceased, or in heavy competition
• You want to preserve genetics from a specific pony
• Natural cover is impossible for health, safety, or management reasons
• You have access to good reproductive veterinary care

It is a poor fit when:

• No experienced equine vet is available
• The mare has known fertility problems and you want the easiest route
• You cannot manage the monitoring schedule
• A suitable stallion is available locally for natural cover or fresh semen

A realistic way to proceed

1. Have your mare examined and get an honest assessment of her breeding soundness.
2. Confirm the studbook's rules on AI and frozen semen.
3. Contact stallion owners or semen banks and request post-thaw quality data and contract terms.
4. Line up a reproductive vet before you buy semen, not after.
5. Plan the breeding for a time of year when you can attend appointments and when the vet's schedule allows.
6. Budget for more than one cycle, and treat the first attempt as a learning cycle rather than a certainty.

Frozen semen AI is a powerful tool for Connemara breeders, but it rewards preparation far more than improvisation. If you have the veterinary support and the patience for precise timing, it opens up stallion choices you could never access otherwise. If you don't, natural cover or fresh semen will usually be the more straightforward route to a foal.