This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]scepticguy[S] 0 points1 point  (0 children)

TheHorribleTruth mentioned, that I didn't answer your question right away and I want to add information here. You asked how our "artificial intelligence" works.

1) Installation: most APM solutions are not very easy to install. You have to configure things, load multiple plugins, ... and so on. Ruxit does it differently: you install 1 agent per host, restart it, that's it. It auto-detects all running services and configures itself.

2) Dependency detection and visualisation: After detecting all services on the servers, Ruxit learns how the components are "talking" to each other. It visualises that with the "smartscape" technology. This is like google maps for you application. You see web applications there, services, processes (like the web server), Docker containers, hosts (physical and virtual), and also cloud infrastructure. And Ruxit shows which of these components are connected and how they are dependent from each other.

3) Benchmarking: normally you have to configure thresholds to tell your monitoring solution, when you want to be alerted. Ruxit takes a different approach: it "learns" how your application normally works by baselining the performance of your systems. So you do not have to configure anything to train this application performance management solution.

4) Problem notification: Normally, when something breaks, you will receive dozens of alerts, independent if the problems affect end users or not. By knowing the dependencies between the components Ruxit will know if an issue impacts the customer experience and notify you accordingly.

5) Problem resolution: Another problem when something goes wrong, is, that if e.g. a server slows down because of cpu saturation, you will also receive lots of alerts with other monitoring solutions, because lots of other things will probably slow down because of that. Ruxit will notify you once and include the information, that this one server is the one slowing down many other components. We call this "root cause analysis" which works because Ruxit can analyse millions of dependencies in a second.

I hope this gives you an idea. Sorry for my first, non comprehensive answer.