-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Observability predefined roles #90806
Comments
Pinging @elastic/uptime (Team:uptime) |
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
Pinging @elastic/apm-ui (Team:apm) |
LogsRead only userCan be tested by hitting {
"elasticsearch":{
"cluster":[],
"indices":[
{
"names": ["logs-*", "filebeat-*", "kibana_sample_data_logs*"],
"privileges":["read", "view_index_metadata"]
}
]
},
"kibana":[
{
"base": [],
"feature": {
"logs": ["read"],
"ml": ["read"]
},
"spaces": ["*"]
}
]
} (This user will not be able to create alerts, create / recreate ML jobs, or edit the logs source configuration). Power userCan be tested by hitting {
"elasticsearch":{
"cluster":[],
"indices":[
{
"names": ["logs-*", "filebeat-*", "kibana_sample_data_logs*"],
"privileges":["read", "view_index_metadata"]
}
]
},
"kibana":[
{
"base": [],
"feature": {
"logs": ["all"],
"ml": ["all"]
},
"spaces": ["*"]
}
]
} |
Thanks @Kerry350 . WDYT about updating the issue description with the logs permission to keep it all in a single declaration? (just leave your comment. It's probably good to have both a combined and separate) |
APMRead only user{
"elasticsearch": {
"cluster": [],
"indices": [
{ "names": ["apm-*"], "privileges": ["read", "view_index_metadata"] },
{ "names": ["logs-apm*"], "privileges": ["read", "view_index_metadata"] },
{ "names": ["metrics-apm*"], "privileges": ["read", "view_index_metadata"] },
{ "names": ["traces-apm*"], "privileges": ["read", "view_index_metadata"] },
]
},
"kibana": [
{
"base": [],
"feature": {
"apm": ["read"],
"ml": ["read"]
},
"spaces": ["*"]
}
]
} Power user{
"elasticsearch": {
"cluster": [],
"indices": [
{ "names": ["apm-*"], "privileges": ["read", "view_index_metadata"] }
]
},
"kibana": [
{
"base": [],
"feature": {
"apm": ["all"],
"ml": ["all"]
},
"spaces": ["*"]
}
]
} |
@sqren Sure, I didn't want to assume and ruin your description 😅 I've merged Logs in with APM in the main declaration. |
Updated issue description with Metrics permissions. |
Thanks @Zacqary ! Can you add just the Metrics definition as a comment here, also? That looks like a good convention. |
MetricsRead onlyTo test: hit {
"elasticsearch":{
"cluster": [],
"indices": [
{
"names": ["metrics-*", "metricbeat-*"],
"privileges": ["read", "view_index_metadata"]
}
]
},
"kibana": [
{
"base": [],
"feature": {
"infrastructure": ["read"],
"ml": ["read"]
},
"spaces": ["*"]
}
]
} Power userTo test: hit {
"elasticsearch":{
"cluster": [],
"indices": [
{
"names": ["metrics-*", "metricbeat-*"],
"privileges": ["read", "view_index_metadata"]
}
]
},
"kibana": [
{
"base": [],
"feature": {
"infrastructure": ["all"],
"ml": ["all"]
},
"spaces": ["*"]
}
]
} |
Thanks, looks great! |
@bytebilly I'd utilised the same format as APM, so I'll defer to @sqren on whether there was a technical reason. Would your preference be adherence to this API? |
@Kerry350 yes that would be my preferred one, since roles are not Kibana related and will be "translated" into the Elasticsearch DSL anyway. |
@sqren for the apm user we also want to add user-experince kibana feature i think. |
@shahzad31 isn't the User Experience app bundled inside the existing |
No preference from my side. From conversations with you and the security team (who already did this) it was my impression this was the preferred format but I might have misunderstood something. |
Yes, the permissions for UX app are already handled via the apm permissions. |
UPTIMERead only user{
"elasticsearch": {
"cluster": [],
"indices": [
{ "names": ["heartbeat-*"], "privileges": ["read", "view_index_metadata"] },
{ "names": ["synthetics-*"], "privileges": ["read", "view_index_metadata"] },
]
},
"kibana": [
{
"base": [],
"feature": {
"uptime": ["read"],
},
"spaces": ["*"]
}
]
} Power user{
"elasticsearch": {
"cluster": [],
"indices": [
{ "names": ["heartbeat-*"], "privileges": ["read", "view_index_metadata"] },
{ "names": ["synthetics-*"], "privileges": ["read", "view_index_metadata"] },
]
},
"kibana": [
{
"base": [],
"feature": {
"uptime": ["all"],
},
"spaces": ["*"]
}
]
} |
This is part of the effort of providing better default roles for end users.
Progress
Following solutions have added privileges:
Read only user
Power user
Superuser
Default superuser: Access to everything
The text was updated successfully, but these errors were encountered: