-
-
-
-
-
-
-
How to Separate Data from Different Types of Machines
-
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!
How to Separate Data from Different Types of Machines
If you are monitoring different types of machines with uberAgent, say XenDesktop/VDI clients and XenApp/RDS servers, you may want to separate the data in the dashboards so that you only see data from one group of machines or the other.
Temporary Separation
To temporarily view only data from a group of machines enter that part of the computer names that uniquely define machines in the desired group in the Filter expression input box on the dashboard. E.g. to filter for machines whose names start with the string RDS:
Permanent Separation
To permanently separate data from a group of machines utilize uberAgent’s multi-tenancy capabilities.
Splunk stores data in containers called indexes. By default uberAgent stores all its data in the index uberagent. But you can easily configure one group of machines to store data in an index called uberagent-clients and another to store in uberagent-servers. The only requirement is that all index names should start with a common prefix, otherwise the dashboards will not work.
By default uberAgent’s dashboards search all indexes whose names start with uberagent. But you can configure individual Splunk user accounts so that they only have permissions to search in the index of one machine group, not the other. Depending on the user account you log on to Splunk with you see data from different machine groups.
For details on how to implement this please see this article.
Alternative for Permanent Separation
As an alternative to separating data into multiple indexes, you can always create custom dashboards that use some other means of differentiating between different types of machines. You could, for example, use a lookup table that stores a mapping between machine groups and computer name regexes.
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.