Question about Indeni release 6.4.1.3

Indeni
#1

In order to test an Ind script, I upgraded my Indeni to be 6.4.1.3. I used to run the following to make sure the ind script gets run.

tail -f /usr/share/indeni-collector/logs/collector.log

But after upgrading, the log stopped displaying anything related the script run.

Any ideas ?

#2

Starting with 6.3.3 the collector logging has changed in order to separate the collector process related logs from the logs that are related to specific devices.


This release also returns the ability to change debug configuration on-the-fly without
the need to restart the relevant process.


A new folder called “devices” was create to hold the device related logs:
/usr/share/indeni-collector/logs/devices


The device logs have the name .log and the are rolled into .log.x.gz
where x is 1 to 10. By default there is only one rolled up file, which limits the data to short period.


The logback.xml has the following changes:


New section:
<appender name="DEVICES_FILES" class="ch.qos.logback.classic.sift.SiftingAppender">

Change the following to increase the number of rolled files
<maxIndex>1</maxIndex>


New section to enable debug for all device, by default the level is set to INFO
<!-- Sets the default log-level for all the device loggers -->
<logger name="devices" level="DEBUG">
<appender-ref ref="DEVICES_FILES"/>
</logger>


New section to enable log level per device
<!-- Overrides the default log-level for a specific device log -->
<!-- <logger name="device_127.0.0.1" level="DEBUG"/> -->
Add a new line without comments to enable debug
<logger name="device_10.3.3.56" level="DEBUG"/>

#3

Thanks for sharing, Shouky! I was curious if we need to still adjust the following:

                <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
                    <fileNamePattern>${indeni.path.logs}/devices/${device-ip}.log.%i.gz</fileNamePattern>
                    <minIndex>1</minIndex>
                   **<maxIndex>50</maxIndex>**
                </rollingPolicy>
                <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
                   **<maxFileSize>50MB</maxFileSize>**
                </triggeringPolicy>
#4

thanks so much. I will dig a little on this.