docs: add Latitude observability integration

[guillemwilly]

Summary

Adds a Latitude observability integration guide, alongside the existing CrewAI observability integrations (Langfuse, Arize Phoenix, Langtrace, etc.).

• New page: docs/en/observability/latitude.mdx — instruments CrewAI with the OpenInference CrewAIInstrumentor and exports OTLP spans to Latitude. Modeled on the existing Arize Phoenix / Langfuse pages (same "What is...?" intro, 5-step structure, References).
• Overview: adds a Latitude card to docs/en/observability/overview.mdx under Monitoring & Tracing Platforms.
• Navigation: adds en/observability/latitude after en/observability/langfuse in docs/docs.json (all English versions).

About Latitude

Latitude is an open-source (MIT-licensed) platform for improving production AI agents — observability, search, and evaluation. Its ingestion endpoint speaks standard OpenTelemetry (OTLP over HTTP), so CrewAI traces flow in via the OpenInference instrumentor without a vendor-specific library.

Test plan

• Page renders under Observability in the docs nav
• Latitude card appears on the Observability overview page
• Code sample follows the same OpenInference pattern as the Arize Phoenix page

Summary by CodeRabbit

• Documentation
  • Added a new "Latitude Integration" guide covering installation, required environment variables, OpenTelemetry setup examples, tracing workflow, and references.
  • Added Latitude to the observability overview's monitoring & tracing platforms.
  • Updated documentation navigation/index to surface the new Latitude pages within observability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: eb6fc3e0-4b90-4d6c-a609-8769d0b9e18b

📥 Commits

Reviewing files that changed from the base of the PR and between 92ba121 and 1312352.

📒 Files selected for processing (1)

• docs/docs.json

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/docs.json

---

📝 Walkthrough

Walkthrough

This PR introduces documentation for integrating Latitude observability with CrewAI. It adds a comprehensive integration guide covering setup, configuration, and example workflows, updates the documentation navigation index to include the new page, and adds a reference card to the observability overview.

Changes

Latitude Integration Documentation

Layer / File(s)	Summary
Latitude integration guide docs/en/observability/latitude.mdx	New MDX documentation page with front matter, introduction to Latitude + CrewAI integration via OpenTelemetry/OpenInference, step-by-step installation and environment variable setup, OTLP HTTP trace exporter initialization with TracerProvider and CrewAIInstrumentor, a complete CrewAI example with agents and tasks, dashboard viewing instructions with shutdown guidance for short-lived scripts, and references to Latitude, CrewAI, and OpenInference documentation.
Documentation index and navigation wiring docs/docs.json	Adds the new "en/observability/latitude" slug to multiple observability-related list blocks throughout the navigation index, positioned consistently after "en/observability/langfuse" and before "en/observability/langtrace".
Observability overview platform card docs/en/observability/overview.mdx	Adds a new Latitude card to the Monitoring & Tracing Platforms card grid, including title, icon, and destination link, positioned after the Weave card.

🎯 3 (Moderate) | ⏱️ ~20 minutes

🐰 A fuzzy guide to traces hops in,
Latitude shines through OpenTelemetry's grin,
Agents observe their journey with care,
Traces bloom where the exporters dare,
Docs lead the way — follow the hare!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: add Latitude observability integration' clearly and accurately summarizes the main change: adding documentation for a new Latitude observability integration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/en/observability/latitude.mdx`:
- Around line 107-117: Update the hard-coded year in the Task sample: change
task1's description (the Task instance referenced as task1 and its description
string) to remove "in 2024" and use a year-agnostic phrase such as "latest" or
"recent advancements" (e.g., "Conduct a comprehensive analysis of the latest
advancements in AI" or "Conduct a comprehensive analysis of recent advancements
in AI"), ensuring the expected intent and wording remain the same and no other
references to the year are left in the Task definition.
- Around line 24-37: Add SERPER_API_KEY to the environment setup so the example
can run from a clean environment and remove the hardcoded phrase "AI in 2024" in
the Task description; specifically, update the env block to set SERPER_API_KEY
(used by SerperDevTool()) alongside LATITUDE_API_KEY, LATITUDE_PROJECT, and
OPENAI_API_KEY, and replace the stale wording "latest advancements in AI in
2024" with a timeless prompt (e.g., "latest advancements in AI") in the Task
text where SerperDevTool is instantiated.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f45a6842-a5a7-48d7-a200-9686638fbf61

📥 Commits

Reviewing files that changed from the base of the PR and between 774fd87 and 56adaf9.

📒 Files selected for processing (3)

• docs/docs.json
• docs/en/observability/latitude.mdx
• docs/en/observability/overview.mdx

[guillemwilly]

Thanks for the review! Addressed both in f2558c6:

• Added SERPER_API_KEY to the Step 2 env block so the example runs from a clean environment (it's used by SerperDevTool() in Step 4).
• Replaced the hard-coded "AI in 2024" with a year-agnostic prompt.