[DOCS-11576] setParameter is never allowed in Atlas Created: 11/Apr/18  Updated: 01/Oct/18  Resolved: 13/Apr/18

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pooja Gupta (Inactive) Assignee: Ravind Kumar (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Participants:
Days since reply: 5 years, 43 weeks, 5 days ago

 Description   

Hi Team,

setLogLevel command uses setParameter command underneath which is not allowed in Atlas.

When run against a paid Atlas Cluster with atlasAdmin role, say M10, db.setLogLevel(1, "query") gives the following error:

{
	"ok" : 0,
	"errmsg" : "not authorized on admin to execute command { setParameter: 1.0, logComponentVerbosity: { query: { verbosity: 1.0 } } }",
	"code" : 13,
	"codeName" : "Unauthorized"
}

This is because to run setParameter, hostManager role is required which Atlas does not offer.

From our documentation on Unsupported Commands, it appears that setparameter and eventually setLogLevel is available for Clusters M10 and larger, according to the Atlas User Privileges granted. It would be better if we explicitly mention that these commands are never available in Atlas, no matter what the instance size of the Atlas Cluster.

Regards,
Pooja



 Comments   
Comment by Ravind Kumar (Inactive) [ 13/Apr/18 ]

Work has started on DOCSP-2124.

Comment by Pooja Gupta (Inactive) [ 12/Apr/18 ]

Thanks Ravind

Comment by Ravind Kumar (Inactive) [ 11/Apr/18 ]

Thanks for the heads up on this pooja.gupta. I have an existing ticket scheduled for the v20180417 release to provide documentation on this matter.

I will make a note to specifically call out setParameter as one of the commands that Atlas does not support with the current security settings.

As an aside, I believe that modifying the log level on Atlas is generally restricted so as to not interfere with Atlas log collection. I would recommend opening a support ticket or pinging in #atlas for support on what options are available for modifying the Atlas log level.

Generated at Thu Feb 08 08:03:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.