Discussion Feed

We are experimenting with docker container monitoring with an eye to deploying this to production in the next couple of weeks. We are currently using a lab environment to make sure we have all of our deployment working properly. We are using RedHat linux with the machine agent running outside of the docker environment. The machine agent is properly configured to capture the docker information and we can view it inside of the controller user interface. Our problem is that whenever the underlying linux server is restarted (it is a lab environment after all), the controller loses all of the data related to the machine and all of the underlying containers. Additionally, the servers page in the controller reverts the server to machine agent (instead of server visibility) level.  What settings do I need to change in order for the metrics to remain and be viewable? Our current docker environment has a number of fixed underlying servers and only the containers running on those servers are transient. Any help that you can give me would be greatly appreciated.   Thanks. ... View more

We have a transaction processing system that is largely implemented using Oracle stored procedures. Each of the transactions are accessed by calling a shell stored procedure where the text does not change. This means that the query ID of the base transaction will never change.  I would like to be able to access the database query data so that I can automatically perform some calculations. I have done enough reading to know that the data I am interested in is stored in Elastic Search.  Here are my questions: - Can I attach Kibana to this Elastic Search instance? If so, what version of Kibana should be used? - Can I query the Elastic Search instance using the standard Elastic Search API? - Has anyone in the community tried to do this? What level of success have you achieved?   Thanks! Dale Chapman ... View more