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

[Persistence] How to Store Edited Flows to Specific Elasticsearch Index #5437

Open
jasonlee1119 opened this issue May 24, 2024 · 1 comment

Comments

@jasonlee1119
Copy link

Hi there, I'm just a newbie to ELSA. As far as I know, the edited flows are stored in Sqlite on my local device. If I want to store persistence data to specific ES server and specific ES index. I didn't see any documentation about this setting. I think I need to set

And how do I debug for the request ELSA sends to the ES server?

Thank you

Copy link

glime-ai bot commented May 24, 2024

To store persistence data in a specific Elasticsearch (ES) server and index using Elsa, you would typically need to configure the Elsa persistence provider to use Elasticsearch. However, as of my last update, Elsa does not natively support Elasticsearch for persistence out of the box. Persistence in Elsa is usually done through database providers like Entity Framework Core with SQL Server, MySQL, PostgreSQL, or SQLite.

If you want to use Elasticsearch, you would likely need to implement a custom persistence provider for Elsa that interacts with Elasticsearch. This would involve creating classes that implement the necessary interfaces to store and retrieve workflow definitions and instances in your Elasticsearch indices.

Regarding the settings you mentioned (Server Endpoint, Username, Password, Index Name), these would be part of your custom implementation. You would need to use the Elasticsearch .NET client (NEST or Elasticsearch.Net) to configure the connection to your ES server and perform the necessary operations.

For debugging the requests that Elsa sends to the ES server, you would use the logging capabilities of the Elasticsearch client and potentially the logging features of Elsa itself to capture the details of the HTTP requests and responses.

Since this is a custom solution, you would need to refer to the documentation and resources for the Elasticsearch .NET client and potentially seek community support for guidance on implementing a custom persistence provider for Elsa.

If you're looking for more specific guidance or examples, I would recommend checking the official Elsa documentation, the Elsa GitHub repository for any community-contributed providers, or reaching out to the Elsa community for assistance.

This comment was generated by Glime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant