Logging in Salt

Configurations Settings

You can use the following parameters for logging various types of events.

LOG_FILE

This parameter is used for identifying where the log files should be stored. The files are passed through the file that can contain the local path name (like master or minion path name) as well as the external server path. 

Make the following configuration to store the data in Master 

log_file: /var/log/salt/master

Make the following configuration to store the data in Minion

log_file: /var/log/salt/minion

Make the following configuration to store the data in External network or server. 

log_file: udp://loghost:port

LOG_LEVEL

This parameter is used to identify which event is to be logged. Various log events are - all, garbage, trace, debug, profile, info, warning, error and critical. 

Make the following configurations if you want to log all the errors. 

log_level: error

Set the LOG_LEVEL to quite if you want to disable the logging. 

log_level: quite

LOG_LEVEL_LOGFILE

This parameter is used to identify which level of messages should be sent to the log file. Various levels are - all, garbage, trace, debug, profile, info, warning, error, critical and quit. 

Make the following configurations to log all the warning messages: 

log_level_logfile: warning

By default, this parameter is set to info level. 

LOG_DATEFMT

Use this parameter to set the format for the time format for the logged messages. 

Make the following configurations to set the time:

log_datefmt: '%H:%M:%S'

By Default the format is %H:%M:%S. 

LOG_DATEFMT_LOGFILE

Use this configuration to set the log messages' date and time format. 

Make the following configurations to set the date and time:

log_datefmt_logfile: '%Y-%m-%d %H:%M:%S'

By Default the format is %Y-%m-%d %H:%M:%S. 

Frequently Asked Questions

How do I determine whether my Salt master is active?

We can determine it by using Salt-Master Live Profiling. Salt-master will report the results' filename if executed in the foreground. The results are typically stored in c:temp on Windows systems and /tmp on Unix-based devices.

How can I check whether my salt system is functioning properly?

The core idea of Salt is that of a Master who commands one or more Minions. The Master is the Central Management System. Executed on managed systems, the Salt minion communicates with Salt Master via instructions and configurations. Linux is the default operating system for the Salt Master, although any other system can be a minion.

What ports is SaltStack running on?

The ports 4505 and 4506, used by the Salt master, need to be open in order to receive incoming connections.  With a persistent connection to the publisher port, all Salt minions wait for messages using port 4055.

Conclusion

Pat yourself on the back for finishing this article. In this article, we discussed the different ways of logging events in Salt. We started by discussing the various log levels and then discussed some parameters that can be used to configure the event logs. 

Do not stop learning! We recommend you read these articles -

🔥 Job Cache in Salt

🔥 Introduction to Salt

🔥 About Salt 

Head to the Guided Path on the Coding Ninjas Studio and upskill in Data Structures and Algorithms, Competitive Programming, System Design, and many more courses.

If you want to Practice top Coding Problems, attempt mock tests, or read interview experiences, head to the Coding Ninjas Studio, our practice platform.

We wish you Good Luck!🎈 Please upvote our blog 🏆 and help other ninjas grow.