That's a good portion of what we are going for. I want it to be as simple as possible for users to make use of their data.
Whether the data is coming from logs, APIs, files or any other source, it should be simple and straightforward to onboard, search, correlate and visualize.
Once, the data is in Flashlight and you have crafted a couple of searches, then it is easy to put that search into a panel of a dashboard and share the dashboard with coworkers.
So, in essence very similar to both Splunk and Datadog, but there are some important distinctions as well.
* Flashlight will be much more affordable.
* Flashlight is self-hosted, so your data stays safe. Built-in and custom permissions also make it easy to share information with only those people you want to have access.
* Flashlight allows you to gradually model your data. Events are a nice, generic text-based data model, but once your data has special requirements, you can break out that data into a seperate model, which will allow you to specify only the specific fields you need, store the data in its own database table, apply custom permissions, generate CRUD API for the model and much more.
* Search commands, in Flashlight, are meant to be a lot more versatile and extensible. For instance, I have a custom Flashlight search command to connect to a group of servers, pull backups and store those backups for later. There is a corresponding custom search command to restore a specific backup later, so I was able to use those search commands in a "System Backup" dashboard with buttons to retrieve or restore backups.
Please let me know if you are having any issues with Flashlight by opening an Issue in the Github Repo.
