Request a Software Demo

See why EMA says "FixStream is a vendor to watch very closely."

Please share your email to download the report

Download Document

Download Document

Download Document

Application Performance Monitoring for IT Operations

FixStream AIOps platform does multi-layer correlation between the business layer, the application layer, and the infralayer to be able to respond to specific business KPI & SLA violation which is triggered by either problems in the application domain or the infrastructure domain.

And, it does that by hierarchically grouping the applications into a business process context. For example, in this case ecommerce is a business process that is running on four different applications billing, customer management, online self-service, and provisioning. If you click on ecommerce you see the entire application map across all entities within the application stack and the infrastructure stack that supports the ecommerce business process. The platform also can detect the transaction metrics by integrating with existing APM tools and then collecting all the business process metrics around the end-user transactions. For example, the by-service create-account, and pay-bill, their corresponding transaction rate, and the success and failure rate, the response time in the time series and then subsequently what the platform does, is has an open API platform where by you can ingest the business KPIs and the business metrics. For example, within the eCommerce business stack, one of the how many number of orders being processed within a given time, their status, and based on the KPIs of response time and when the completion time of a business process event, the platform has the ability to correlate in the application layer and the infrastructure layer to detect problems that may be causing that. For example, if you go to the eCommerce case it has three different layers. They are infra health which is predicated by the number of fault, critical, and tickets including a score. The number of transactions in failure state in the time window. And, then the business metric app. You can click on that it shows you the hierarchical relationship between the business process and the application and the corresponding operational details for each of the entities.

Now, if you click on the business process it tells you between the start and end date, and time, what are the different orders being processed, and pending and the failure state. For example, if I click on the failed number of order, it further breaks it down into different KPIs which is ingested through the open API in an hierarchical view on which is now called the platform to get to this point. Let’s say for example within the TV orders you have 33% in the fail status. If you click on that, it takes you to a time series view that shows you by each hour how many orders are in the failed status. As you can see there is something that happened during this time where to buy the number of failed transactions dramatically increased. Now if I click on that, it takes you to the event correlation screen whereby it can pinpoint exactly at the time when the number of Errors went up what was happening within the application under infrastructure stack. All the sequence of events, leading to the point where the number of errors went up and the number orders starting to fail. You can very quickly understand that and take actions to solve it.

So at a very high level the platform is doing correlation business KPIs starting with the business process label SLA and the KPI metrics from there and then correlating that to all the underlying application entities and then to the infrastructure entity. It creates a very powerful view where you can answer any KPI issues that may be triggered from an application problem or an infra problem.  Thank you

Submit to Download

>