Yes, it can be enabled but enabling this parameter will effect how the Database Engine treat tablespace files. With this setting each table will have its own .ibd file or tablespace. It should be transparent to any application using the database, in this case our Foglight application.
Please note that changing this parameter will only effect newly created tables and not existing tables.
To make this change, please go through backup restore procedure (with mysqldump), where before restore this option is enabled - similar to
Enable innodb_file_per_table & Fix Old Databases
In Foglight 5.7 the server will be updated to use MySQL 5.6 with the innodb_file_per_table option enabled. The only issue that was encountered was, that some query operations ended up being slower if the server created temporary tables, because the database would create a new data file for the temporary table which is an fairly expensive operation. The server was modified to specify a storage engine other than the InnoDB engine when creating temporary tables.
In Foglight 5.6 the temporary tables are created using the default storage engine of the database. So if the default is set to the InnoDB storage engine, then similar performance problems may be encountered. A workaround for better performance is to change the default storage engine to MyISAM.