LLM Observability documentation fixes: Broken links, grammar, and spelling

[areibman]

@qingyun-wu @ekzhu @sonichi

Why are these changes needed?

3 pages in the AutoGen documentation have clarity, spelling, and formatting issues.

1. Broken links
https://microsoft.github.io/autogen/docs/notebooks/agentchat_agentops/

In the AgentChat AgentOps notebook, several images are not rendering because they point to invalid URLs:

We've replaced these URLs so they now render correctly by pointing to GitHub raw user content links.

2. Updated the LLM Observability link for clarity:

The current LLM Observability section doesn't do an adequate job explaining observability or why it's important. The English in this page has been updated to make it easier for developers to understand its purpose and the tools available in AutoGen to add observability.

3. Updated the AgentOps example notebook

Several images in this notebook were pointing to the wrong URL and were not rendering. Also updated text for clarity + removed an API key in the notebook

Related issue number

Closes: #2994

Checks

• I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11616921	Triggered	Generic High Entropy Secret	4ddda11	notebook/agentchat_agentops.ipynb	View secret
11616921	Triggered	Generic High Entropy Secret	7afe9d9	notebook/agentchat_agentops.ipynb	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[areibman]

@microsoft-github-policy-service agree [company=“{AgentOps}"]

…

On Jun 21, 2024, at 4:02 PM, microsoft-github-policy-service[bot] ***@***.***> wrote: @microsoft-github-policy-service agree [company="{your company}"]

[areibman]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id GitGuardian status Secret Commit Filename
11616921 Triggered Generic High Entropy Secret 4ddda11 notebook/agentchat_agentops.ipynb View secret
11616921 Triggered Generic High Entropy Secret 7afe9d9 notebook/agentchat_agentops.ipynb View secret
🛠 Guidelines to remediate hardcoded secrets
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

There are no secrets being leaked in this PR. They are false positives pointing to GUIDs in a few GitHub URLs

[qingyun-wu]

Thanks for the quick fix! Looks great!