Replies: 2 comments
-
@Lorygold may I have your views on this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Discussion closed because the task has been accepted → related issue: #202 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
BuffaLogs currently supports Elasticsearch as its sole data ingestion source. As part of my GSoC project, I am expanding its capabilities to support additional data sources, with OpenSearch being one of the first major additions.
OpenSearch, an open-source, community-driven fork of Elasticsearch, is a really similar search and analytics engine. It is widely used by organizations worldwide as a scalable and flexible alternative to Elasticsearch, particularly after Elastic changed its licensing model. So it makes sense to onboard it in parallel to Elasticsearch.
I already made a
docker-compose.opensearch.yaml
file to create a local instance of OpenSearch to simplify testing, which looks something of this sort:I have also created a new
OpenSearchIngestion
class that is similar to how Elasticsearch is implemented. Here's a code snippet for the same with an example of theprocess_users()
function, which can be extended to other functions:Before opening a Pull Request, I’d love to hear your feedback on the implementation—any suggestions, improvements, or potential issues you foresee.
Beta Was this translation helpful? Give feedback.
All reactions