Skip to content

Commit

Permalink
Default configuration for Shinken 2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
Fred MOHIER committed Mar 6, 2014
1 parent c3fdf98 commit f9a1f67
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion etc/modules/logstore_sqlite.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,10 @@
define module {
module_name logsqlite
module_type logstore_sqlite
database_file /usr/local/shinken/var/livelogs.db
# Shinken 1.4 configuration
# database_file /usr/local/shinken/var/livelogs.db
# Shinken 2.0 configuration
database_file /var/log/shinken/livelogs.db
# Prefer SQL queries if available instead of internal in-memory lookups
# Some corner cases may return invalid or no data. Defaults to 0 if unset.
#use_aggressive_sql 1 ; Set to 1 for large installations
Expand Down

6 comments on commit f9a1f67

@mohierf
Copy link

@mohierf mohierf commented on f9a1f67 Mar 6, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed referencing Issue #2

@Seb-Solon
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well actually, /usr/local/shinken is not "really" 1.4. You can just change path ;)

@mohierf
Copy link

@mohierf mohierf commented on f9a1f67 Mar 6, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but it is default path used with 1.4 version ... it seems necessary that when you shinken install a module with new version, default configuration does not raise any exception, doesn't it ? :-)

@Seb-Solon
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was in 1.4 tarball but I don't think it is a "good" path indeed. Shinken 1.4 installation was, IMO, not really defined, so /usr/local/shinken is a simple example. Moreover, as this file is already in 1.4 maybe it's not necessary to deal with the 1.4 case here.

If somone wants to update the module, he/she should be able to edit config files, what do you think?

@mohierf
Copy link

@mohierf mohierf commented on f9a1f67 Mar 7, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. If someone wants to update he may change the file, but it is really better if the configuration file is ok when we install the module and current default installation for such a file is in /var/log/shinken directory ... so the module may defaulty use this path.

@naparuba
Copy link
Member

@naparuba naparuba commented on f9a1f67 Mar 7, 2014 via email

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.