With our latest release we are so excited to introduce you to the newest member of the UiPath family, Insights!
A powerful, embedded analytics solution integrated within Orchestrator at the tenant level, Insights helps you measure, optimize and scale your RPA operation and its impact to your business.
Gain operational awareness with a library of out-of-the-box dashboards, customizable with any combination of widgets and/or filters. Dashboards can be shared with all users of an Orchestrator tenant, enabling company-wide visibility while continuing to work from the same dataset and without impacting your original dashboards.
Using the Pulse feature in Insights, you can stay up-to-date with the current status of your RPA deployment’s most important metrics and receive alerts of any errors or anomalies.
@jfrestrepon We are shooting for a cloud release ASAP. Definitely sometime this year. We haven’t worked through licensing for cloud yet, or did you mean how is it currently licensed on prem?
Thanks for your answer @Michelle_Yurovsky!
I meant “UiPath Cloud Orchestrator”. Have you any idea if is there any way to configure “UiPath Cloud Orchestrator” (or use a webhook) to save logs to an external Data Storage service so we can create and custom our own dashboards?
Hi @loginerror. I understood how to manually access and download logs from “UiPath Cloud Orchestrator” (SaaS), and also that is possible to get logs from Robots. But we want to know how “UiPath Cloud Orchestrator” can send logs automatically (direct from cloud) to an external database, just like the “UiPath OnPremise Orchestrator” does.
Does the “UiPath Cloud Orchestrator” (SaaS) has a web.cofig or any other way to configure a Splunk connection?
I think that this is all configured on our end, at least for the Community site of the Cloud Platform. It might be interesting to engage our technical support about the possibility to modify some settings for the Enterprise Cloud Accounts, but I am not immediately aware of such possibility.
Hi @anjab! Great question. Insights works differently from Kibana on both the front-end and the backend. For instance, Kibana receives a more limited data source than Insights does, as it only works with logs. Due to the nature Elasticsearch’s database type (basically NoSQL), it doesn’t play nicely with SQL which means none of the information from the Orchestrator DB is ported there. That means info like robot types, licensing, job information, detailed queue information, etc, is not accessible within Kibana. Insights however, receives information from both the Orchestrator SQL db AND logs. From the frontend, Insights is integrated with the UiPath Orchestrator so you get the integrated tenant security model that isn’t available in Kibana. Insights also has a very useful alerting mechanism called Pulse which allows you to easily add 3 types of alerts for any metric in your dashboards right from the dashboard itself (including Threshold, Anomaly Detection, Always Alerts (aka every db update)), without the need to write complicated queries. In general, Insights is targeted to be more user friendly so that you don’t need to have a technical background to use it. So, there are definitely pros and cons to both. A pro for Kibana is that you don’t need to be a user in Orchestrator. For some, that’s important. In general there’s no reason why you can’t use both tools side by side.