Skip to content
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

Clarify the permissions required for the jmx exporter user #3283

Open
rgl opened this issue Oct 21, 2024 · 0 comments
Open

Clarify the permissions required for the jmx exporter user #3283

rgl opened this issue Oct 21, 2024 · 0 comments

Comments

@rgl
Copy link

rgl commented Oct 21, 2024

Description

in order to use the prometheus jmx exporter we need a user, but its not clear to me which permissions should this user have. in theory, this user would only require some kind of read-only permissions, correct?

can you please clarify which permissions should be granted to a hypothetical jmx_exporter role?

the instructions at https://apim.docs.wso2.com/en/latest/observe/api-manager/metrics/jmx-based-monitoring/#starting-the-wso2-product-with-jmx has this informational note:

Make sure that the user ID you are using for JMX monitoring is assigned a role that has the Server Admin permission. See Configuring Roles for further information about configuring roles assigned to users. Any user assigned to the admin role can log in to JMX.

But I'm sure sure what "Server Admin permission" means. Is it the "Server Admin" from the Carbon new role creation page:

image

Instead of "Server Admin", shouldn't we use "Read Only" (under All Permissions, Super Admin Permissions, Server Admin, Java Management Extensions) instead?

If so, can the documentation be updated with this information? And maybe also include an jmx_exporter role out-of-the-box?

Affected Component

APIM

Version

4.3.0

Environment Details (with versions)

N/A

Related Issues

No response

Suggested Labels

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant