Add Elasticsearch as datasource for Application logs #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are adding Elasticsearch as second datasource besides Prometheus.
Elasticsearch can be used to query the logs of our applications. For
that we extend the Applications CRD with a logs field, which can be used
to define Elasticsearch queries to retrieve the logs of an application.
In the kobs UI we added a new tab "logs" for the applications view,
where a user can select the defined queries for an application. When a
query is selected, the query is run against Elasticsearch and the logs
are shown in a table view. Next to the query we also run an aggragation,
so show the distribution of the logs in the selected time range in a bar
chart.
Next to the support of Elasticsearch in the applications view, we also
added an interface to query the configured Elasticsearch datasource
directly.