We have set up ELK stack to store our system log messages. Each operation
and each error in the system have associated GUID, so in order to find all
messages related to a certain activity we only need to obtain its
respective ID or the ID of an error in case activity failed. What we can't
figure out is how we can make it easy for users to retrieve information
from Kibana if they have activity or error ID. Kibana Web UI is not REST,
so it looks like there is no way to control Kibana search via URL,
something that would be great for us so we could simply embed incident URL
in error description.
We have set up ELK stack to store our system log messages. Each operation
and each error in the system have associated GUID, so in order to find all
messages related to a certain activity we only need to obtain its
respective ID or the ID of an error in case activity failed. What we can't
figure out is how we can make it easy for users to retrieve information
from Kibana if they have activity or error ID. Kibana Web UI is not REST,
so it looks like there is no way to control Kibana search via URL,
something that would be great for us so we could simply embed incident URL
in error description.
We have set up ELK stack to store our system log messages. Each operation
and each error in the system have associated GUID, so in order to find all
messages related to a certain activity we only need to obtain its
respective ID or the ID of an error in case activity failed. What we can't
figure out is how we can make it easy for users to retrieve information
from Kibana if they have activity or error ID. Kibana Web UI is not REST,
so it looks like there is no way to control Kibana search via URL,
something that would be great for us so we could simply embed incident URL
in error description.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.