# Lab resources

![](https://static.scarf.sh/a.png?x-pxid=83d7b072-bdfc-4f7d-810d-3ab42267ff54)

To use these lab resources to their full extent, you'll need to [install](/manual/4.1/installation/downloads.md) resources in your local environment to test and run Fluent Bit.

## O11y workshops by Chronosphere

Chronosphere provides several [open source observability workshops](https://o11y-workshops.gitlab.io/), including a Fluent Bit workshop:

{% embed url="<https://o11y-workshops.gitlab.io/workshop-fluentbit/>" %}
Fluent Bit workshop for getting started with cloud native telemetry pipelines
{% endembed %}

1. [Lab 1 - Introduction to Fluent Bit](https://o11y-workshops.gitlab.io/workshop-fluentbit/lab01.html)
2. [Lab 2 - Installing Fluent Bit](https://o11y-workshops.gitlab.io/workshop-fluentbit/#/4)
3. [Lab 3 - Exploring First Pipelines](https://o11y-workshops.gitlab.io/workshop-fluentbit/#/5)
4. [Lab 4 - Exploring More Pipelines](https://o11y-workshops.gitlab.io/workshop-fluentbit/#/6)
5. [Lab 5 - Understanding Backpressure](https://o11y-workshops.gitlab.io/workshop-fluentbit/#/7)
6. [Lab 6 - Avoid Telemetry Data Loss](https://o11y-workshops.gitlab.io/workshop-fluentbit/#/8)
7. [Lab 7 - Pipeline Integration with OpenTelemetry](https://o11y-workshops.gitlab.io/workshop-fluentbit/#/9)

You can also view the source files for these workshops on [GitLab](https://gitlab.com/o11y-workshops/workshop-fluentbit).

## Logging with Fluent Bit and Amazon OpenSearch workshop by Amazon

This workshop by Amazon goes through common Kubernetes logging patterns and routing data to OpenSearch and visualizing with OpenSearch dashboards.

{% embed url="<https://eksworkshop.com/>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fluentbit.io/manual/4.1/about/resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
