-
-
-
Upgrading uberAgent
-
-
-
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!
Upgrading uberAgent
When a new version of uberAgent is available you need to do the following in order to update your existing installation.
Understand What is New and Changed
Please read the changelog. Changes might affect uberAgent’s configuration, for example.
Depending on the nature of the changes made for a new version it may be necessary to update custom apps that make use of the data collected by uberAgent.
uberAgent Splunk Indexer and Dashboard Apps
Before upgrading from version 6, delete the Splunk KV store lookup lookup_hostinfo2
by running the following Splunk search:
| outputlookup lookup_hostinfo2
<!--NeedCopy-->
Also, run the following commands one after another to delete obsolete KV Store collections of the experience scores. Starting with 6.1, scores are stored in an index.
| outputlookup lookup_score_per_machine
<!--NeedCopy-->
| outputlookup lookup_score_historic_per_machine
<!--NeedCopy-->
| outputlookup lookup_score_per_session
<!--NeedCopy-->
| outputlookup lookup_score_historic_per_session
<!--NeedCopy-->
| outputlookup lookup_score_per_application
<!--NeedCopy-->
| outputlookup lookup_score_historic_per_application
<!--NeedCopy-->
Delete the uberAgent app directories:
$SPLUNK_HOME\etc\apps\uberAgent
$SPLUNK_HOME\etc\apps\uberAgent_ESA
$SPLUNK_HOME\etc\apps\uberAgent_indexer
<!--NeedCopy-->
Install the new versions of the Splunk apps as described here.
Restart Splunk.
Starting with uberAgent 6.1, we added a second index called score_uberagent_uxm
in addition to the existing index uberAgent
.
This is because uberAgent now uses index storage for scores on the Experience Score dashboard instead of the KV Store. So please make sure to update the uberAgent_indexer
app as well.
This is especially important when using Splunk Cloud. Details are available here.
uberAgent on the Endpoints
In uberAgent 7.0, host and user tags are collected through dedicated timers instead of a static interval. Please adjust your configuration and implement a timer as described here to continue collecting user and host tags after upgrading to uberAgent 7.0.
uberAgent’s MSI installer has all the logic to upgrade an installation automatically preserving the current settings. Just run the installer again using your deployment method of choice as described here.
Note: customizations to the configuration in the installation directory are not retained during an upgrade. Such customizations must be re-applied after the upgrade. We recommend to store the configuration files outside the installation directory.
Elasticsearch
New uberAgent versions generally come with additional fields. This makes it necessary to update the index template. To do that, overwrite the existing index template with the new version. Please note that templates are applied to new indexes only. Existing indexes keep their templates.
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.