Once you have upgraded your GroundWork Monitor 7.1.0 installation with Log Bridge to 7.1.1, there are several post-upgrade tasks you must do. If you aren't using Log Bridge, there is no need to do these steps.
Post-upgrade tasks for Log Bridge installations
The following steps just show the minimal files for a default install. If you have more feeder endpoints configured, you will have more files to migrate.
Restore the master configuration files logbridge_feeder.conf and gwevents_to_es.conf from the installer backup config directory (e.g., /usr/local/groundwork/backup-2016-12-02/config). For example:
cp <the groundwork backup directory>/foundation/container/jpp/standalone/deployments/portal-groundwork-base.war .
jar xf portal-groundwork-base.war WEB-INF/portlet.xml
rm -f portal-groundwork-base.war
cp /usr/local/groundwork/foundation/container/jpp/standalone/deployments/portal-groundwork-base.war /tmp
jar uf portal-groundwork-base.war WEB-INF/portlet.xml
cp portal-groundwork-base.war /usr/local/groundwork/jpp/standalone/deployments/portal-groundwork-base.war
service groundwork restart
Install the latest versions of logbridge_feeder.pl and gwevents_to_es.pl into /usr/local/groundwork/foundation/feeder. Note that it is no longer necessary to build the Search::Elasticsearch Perl module.