What Elasticsearch Indices are viewable by Orchestrator?
For Elasticsearch, Orchestrator only reads logs from indices prefixed by “uipath-*”.
When doing a restore from a snapshot the names of the indices may have changed (i.e. doing a rename on restore) and the log data would not be accessible by Orchestrator.
Aliases for these indices can be created so Orchestrator can see the logs contained in them.
Below is an example request where the index orchestrator-logs contains the data to be accessed, therefore the alias uipath-logs is assigned to it:
POST _aliases
{
"actions": [
{
"add": {
"index": "orchestrator-logs",
"alias": "uipath-logs"
}
}
]
}
Wildcards can also be used in the index parameter of the request. For example, if renaming is performed on restore so that all indices are prefixed by “restored-“, the following request can be used to assign the uipath-logs alias to all of them. Please note wildcard patterns that match both data streams and indices return an error.
POST _aliases
{
"actions": [
{
"add": {
"index": "restored-*",
"alias": "uipath-logs"
}
}
]
}