We installed the ElasticAgent on Kubernetets as a DeamonSet and everything seems to work fine except a couple of a errors on the Overview dashboard.
Yes, the cluster does not have that role because we don't have a remote cluster. So I dont see the need to enable this. We have a 3 node ES cluster and Kibana on another separate server.
Inspecting the panel I see this error:
Im Superuser and Kibana admin so I would think I have all the permissions.
{
"attributes": {
"type": "status_exception",
"reason": "error while executing search",
"caused_by": {
"type": "security_exception",
"reason": "action [indices:data/read/search] is unauthorized for user [<MYACCOUNT>] with effective roles [kibana_admin,monitoring_user,superuser], this action is granted by the index privileges [read,all]",
"caused_by": {
"type": "illegal_argument_exception",
"reason": "node [LNXELASTIC101-P] does not have the remote cluster client role enabled"
}
}
},
"err": {
"message": "status_exception\n\tCaused by:\n\t\tsecurity_exception: action [indices:data/read/search] is unauthorized for user [<MYACCOUNT>s] with effective roles [kibana_admin,monitoring_user,superuser], this action is granted by the index privileges [read,all]",
"statusCode": 403,
"attributes": {
"type": "status_exception",
"reason": "error while executing search",
"caused_by": {
"type": "security_exception",
"reason": "action [indices:data/read/search] is unauthorized for user [<MYACCOUNT>] with effective roles [kibana_admin,monitoring_user,superuser], this action is granted by the index privileges [read,all]",
"caused_by": {
"type": "illegal_argument_exception",
"reason": "node [LNXELASTIC101-P] does not have the remote cluster client role enabled"
}
}
}
}
}
Yes I noticed the Info panel. But since I see data on other panels I assume kube-state-metrics works. Correct me I im wrong!
Any pointers?