@Marvin I am running a self hosted Prefect, however can't get artifacts shown in the UI. The same code to create artifacts works in the cloud but not on self hosted solution. Is there an extra argument to configure?

It seems like you're having issues with artifacts not appearing in the UI for your self-hosted Prefect setup. Here are some insights and potential steps to address the problem: 1. Configuration Check: Ensure that your self-hosted Prefect server is correctly configured to store and render artifacts. Artifacts are stored in Prefect Cloud or Prefect Server and rendered in the Prefect UI. Double-check your server settings to confirm that it supports artifact storage and rendering. 2. UI Rendering: Artifacts should be visually rich annotations available in the UI. Ensure that your UI is updated and properly connected to your Prefect server. 3. Documentation: Review the Prefect documentation on artifacts to verify that your implementation aligns with the expected setup for artifacts. 4. GitHub Issues: There aren't specific open issues directly addressing artifacts not showing in the UI for self-hosted setups. However, staying updated with the Prefect GitHub repository issues might provide insights into similar problems others are facing. If you've verified your configuration and the issue persists, consider reaching out to the Prefect community or support for more tailored assistance.

@Marvin elaborate on 1. What configuration should I check? Where and how are artifacts saved?

To ensure that artifacts are displayed correctly in your self-hosted Prefect setup, consider the following configuration aspects: 1. Prefect Server Setup: - Your self-hosted Prefect server must be properly configured and running. You can start it using the

prefect server start

command. The server should be backed by a database and a UI, similar to Prefect Cloud. - Ensure that your Prefect server is accessible via the correct URL (typically

<http://127.0.0.1:4200>

by default). 2. Artifact Storage: - Artifacts are stored within the Prefect server's database. Ensure that your database is correctly set up and accessible by the Prefect server. - If you're using Kubernetes, check the Helm chart configuration for your Prefect server to ensure it's set up to handle artifact storage. 3. Python SDK Client: - The Prefect Python SDK client should be correctly configured to communicate with your self-hosted Prefect server. Verify that the client is pointing to your server's URL rather than Prefect Cloud. 4. Artifact Creation and Retrieval: - Artifacts are created and managed using the Prefect SDK. Make sure that your code for creating artifacts is correctly implemented and that the Prefect server can access this data. - You may want to review the artifact interface in the Prefect source code to understand how artifacts are created and stored. For more detailed guidance, refer to the Prefect documentation on self-hosting and artifacts. These resources provide comprehensive instructions on setting up and managing your Prefect server and artifacts.