-
-
-
-
-
-
Data Distribution and Separation (Routing to Multiple Backends)
-
Recommendations for Custom Dashboards (Splunk)
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Recommendations for Custom Dashboards (Splunk)
Why Create Custom Dashboards
uberAgent ships with more than 60 dashboards that visualize every metric uberAgent collects. So why create custom dashboards?
uberAgent’s dashboards need to work for all customers. They must be generic and cannot have dependencies on other apps.
The needs of our customers are as diverse as their networks. Custom dashboards meet the most specific requirements. They provide KPIs and views tailored to a customer’s needs. And custom dashboards can bring data from multiple sources together: uberAgent + X + Y. That is what Splunk calls operational intelligence.
Where to Create Custom Dashboards
Dashboards need to "live" somewhere. In Splunk, a dashboard’s natural habitat is an app. Apps are containers for dashboards and files. Apps allow you to:
- Keep related items in one place
- Add a corporate logo
- Assign permissions
- Publish to Splunkbase
Dashboard Authoring Recommendations
Create Your Own App
At first, people are often tempted to store their custom dashboard files in the uberAgent app directory. That seems to be the easiest way, but it breaks easily when the uberAgent Splunk apps are updated. We recommend hosting custom dashboards in your own app, independent of uberAgent.
Do Not Hard-Code Things
Networks are dynamic, as is uberAgent. New versions may bring new sourcetypes, data models, and fields.
uberAgent provides macros to simplify future upgrades. uberAgent’s macros can be used globally (e.g., in other apps, too). The use of the following macros is highly recommended:
-
uberAgent_index
: stores the name of the uberAgent Splunk index -
uA_DM_dataset
: stores the name of the data model that contains a given dataset
All macros are defined in the file macros.conf
of the uberAgent Splunk dashboard app.
Copy From Us
The best way to get to know the data collected and visualized by uberAgent is to look at the source code of the dashboards that ship with the product. We understand that practical examples can be very helpful and we explicitly recommend to reuse parts of the product’s default dashboards in your custom dashboards.
Professional Services
Help and support services for custom dashboard creation are available through our network of solution partners and consultants. Our partners are competent both with uberAgent and with Splunk. They are able to assist you with PoCs, architecture, customizations as well as quotes and pricing.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.