Can I set a logging setting for a single node in a domain via CLI?

[sboscarine]

Hello All,

We are running EAP 6.0.1 in domain mode and have a profile with all our default logging settings.  However, we have a single node in an 8 node cluster which may or may not be causing issues.

How can I set logging for that one node via CLI?  Is there a way to run the command below for just server-one?

#Can I run this only on 'server-one' in an 8 node cluster?
/profile=full-ha/subsystem=logging/logger=com.mydomain.myproblemclass:add(level=DEBUG)  

Thanks!

Steven

[wdfink]

AFAIK not.

The only thing that looks possible for me ATM is to copy the profile and use for this server a different server-group. The server is still in the cluster but you are able to set the logging for exact this server.

If the single node is a random node this will not be a solution

[sboscarine]

It seems odd that all the settings set in a profile cannot be overridden. 

So if I wanted to try the route you suggested and create a profile, can that be done dynamically?  If I have an 8 node cluster and it is in the full-ha profile, is there a way to create a profile named "server-one?"  Can I do it dynamically without a restart...or do I have to create a profile for every single cluster node if I wanted to be able to set Logging settings?

[erasmomarciano]

Hi

Have you got a domain controller?

You can set the logging in domain.xml of domain controller

[sboscarine]

We're running in domain mode.  Our issue is that we have a cloud/multi-tenant offering and therefore host many customers in a few data centers on different continents.  Ideally, we would want 3 levels of settings:  Global, Customer, and Node. 

The first thing that comes to mind is creating profiles that extend one another.  However, we don't care too much how we accomplish it as long as it can be painlessly scripted. 

Right now, it appears that if we have 100 customers, customer A wants to change a minor setting, we have to clone our master settings and manually keep it in sync. 

[brian.stansberry]

In 6.1 you can create the category in the profile but use an expression for the level attribute, e.g. level=${myproblemclass.level:FATAL}. Then to change the level on the desired server:

/host=<thehost>/server-config=<theserver>/system-property=myproblemclass.level:add(value=DEBUG)

I don't believe the logger category level attribute supports expressions in 6.0.1 though.