Client configurations?

[brockn]

From the base log appender:

curl -X POST -H 'Content-Type: application/json' -d '{"category": "'$category'","timestamp": '$timestamp', "level": "'$level'", "message": "'$message'", "threadName": "'$threadName'"}' http://0.0.0.0:9005/log?application=$application

It'd be nice to get this from a client config, eg /etc/pulse/conf/env.sh so I'll I'd have to use as a user is:

source /opt/cloudera/parcels/PULSE/lib/appenders/logger.sh

and I'd be running.

[bpmcd]

Another client asked today about the same possibility, but for the log4j configuration in a Spark app.

[afoerster]

@brockn task created

@bpmcd task created, for this to work we would have to reload log4j configuration at runtime so a little more challenging.

[brockn]

reload log4j configuration at runtime so a little more challenging.

feels like a non-goal

[afoerster]

I haven't quite figured this one out yet. I can create an environment file using the parcel, but that doesn't have information about the host running the log-collector role. The descriptor.sdl has a 'peerConfigGenerator' to get hostnames running a role, but it will only share the peer config with other roles of the same type.

If Pulse was depending on another service this would be easy, for example Kafka depends on Zookeeper so it's easy for Kafka to get the Zookeeper hosts.