Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: deploy langfuse for development #347

Merged
merged 14 commits into from
Feb 10, 2025
Merged

Conversation

friedrichwilken
Copy link
Collaborator

Description

Changes proposed in this pull request:

  • add docs how to deploy langfuse locally and on a k8s cluster for dev work.

Related issue(s)
#49

@friedrichwilken friedrichwilken requested a review from a team as a code owner January 22, 2025 08:28
Copy link

Note(s) for PR Auther:

  • The integration test will be skipped for the PR. You can trigger it manually after adding the label: run-integration-test.
  • The evaluation test will be skipped for the PR. You can trigger it manually after adding the label: evaluation requested.
  • If any changes are made to the evaluation tests data, make sure that the integration tests are working as expected.
  • If any changes are made to how to run the unit tests, make sure to update the steps for unit-tests in the create-release.yml workflow as well.

Note(s) for PR Reviewer(s):

  • Make sure that the integration and evaluation tests are working as expected.

@friedrichwilken friedrichwilken linked an issue Jan 22, 2025 that may be closed by this pull request
5 tasks
@friedrichwilken friedrichwilken changed the title Doc langfuse deployment docs: deploy langfuse for development Jan 22, 2025
docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated

### Set up Redis

A local instance of LangFuse will bring it's own instance of `Redis` with some basic authentication setup. The password defaults to `myredissecret` (if you do not specify the env var `REDIS_AUTH`) and LangFuse will automatically use the database number `0` of that Redis instance (remember that it comes by default with 16 databases, 0 to 15).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A local instance of LangFuse will bring it's own instance of `Redis` with some basic authentication setup. The password defaults to `myredissecret` (if you do not specify the env var `REDIS_AUTH`) and LangFuse will automatically use the database number `0` of that Redis instance (remember that it comes by default with 16 databases, 0 to 15).
A local instance of LangFuse brings its own Redis instance with some basic authentication setup. The password defaults to `myredissecret` (if you do not specify the env var `REDIS_AUTH`) and LangFuse automatically uses the database number `0` of that Redis instance (remember that by default, it comes with 16 databases, 0 to 15).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could also link to LangFuse official docs in the first mention.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea, I will add this.

docs/langfuse.md Outdated

A local instance of LangFuse will bring it's own instance of `Redis` with some basic authentication setup. The password defaults to `myredissecret` (if you do not specify the env var `REDIS_AUTH`) and LangFuse will automatically use the database number `0` of that Redis instance (remember that it comes by default with 16 databases, 0 to 15).
If you also run a local instance of `Redis` for the `Companion`, you have two options.
a) You let the `Companion` use the Redis instance that comes with Langfuse and addressing database `1` by adding these lines in your `config/config.json`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
a) You let the `Companion` use the Redis instance that comes with Langfuse and addressing database `1` by adding these lines in your `config/config.json`:
1. You let the Companion use the Redis instance that comes with LangFuse and addressing database `1` by adding these lines in your `config/config.json`:

To double-check if I get it right: the Redis instance comes with LangFuse and database 1? What is it addressing? Did you mean "corresponding"?

Copy link
Collaborator Author

@friedrichwilken friedrichwilken Feb 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LangFuse comes with Redis. Redis has multiple Databases, 0 to 16. We want to set the Companion to use database 1.
Maybe:

1. You let the Companion use the Redis instance that comes with LangFuse by addressing database `1` in `config/config.json`

docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated Show resolved Hide resolved
docs/langfuse.md Outdated Show resolved Hide resolved
friedrichwilken and others added 10 commits February 7, 2025 11:17
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
Co-authored-by: Małgorzata Świeca <[email protected]>
@kyma-bot kyma-bot added the lgtm label Feb 10, 2025
@kyma-bot kyma-bot merged commit 529ddeb into main Feb 10, 2025
4 checks passed
@friedrichwilken friedrichwilken deleted the doc-langfuse-deployment branch February 10, 2025 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

blocked: Setup the tracing infrastructure for agents
3 participants