In this project phase, your web site is live and visitors are generating data (e.g., form submissions, web analytics, etc.), editors are producing new content, and you are enhancing the website's features. These are important activities and you need to monitor the website's environment, application, and data in order to maintain peak performance and stay ahead of issues.
Monitoring the website keeps you informed about the health of the site and helps identify what can be optimized and improved.
- Monitor resource utilization on the server (e.g., CPU, RAM, HDD).
- Consider tools like App Insights, etc.
- Monitor web site availability with uptime services.
- Monitor web site responsiveness / performance.
- Consider checking the performance from different geographic locations.
- Monitor application errors, warnings, 404 errors, etc.
- Use event log notifications or create custom report in the reporting module.
- Keep an eye on web analytics and online marketing data.
- Monitor all data, like visitors and their activities, page views, conversions, etc. as those can grow fast when the site traffic is high.
- Configure inactive contact deletion rules.
- Make sure that the scheduled tasks deleting old data are configured and running (e.g., for analytics data and inactive contacts).
- Consider separating the online marketing data to another database if the size of the data is causing performance issues on the rest of the site.
- It is more important to keep contact data than web analytics as 3rd party tools (e.g. Google Anayltics) can be used to keep long term analytic data.
- Keep online marketing data for 6 to 12 months to provide the necessary data for marketing automation and other online marketing features.
- Monitor the size of the database tables.
- Define rules to handle outdated content.
- Monitor content for broken links.
Analyze the data you gather from monitoring to determine what actions to take. Focus on optimizations of content and performance.
- Define backup strategy (SQL, file system, disaster restore / recovery plan).
- Perform SQL maintenance (shrink transaction log, rebuild indexes).
- Plan outages and take necessary steps to notify the appropriate people.
- Review and address performance issues.
- Keep software patched and up-to-date including Kentico, the operating system, SQL server, etc.
- Decide whether to upgrade or not.
- Archive old data.
- Remove unnecessary objects (e.g., old content versions, unused media files, inactive contacts, old web analytics, staging tasks, unsent emails, old online marketing activities, etc.).
- Update and optimize content (e.g., update outdated content, fix broken links, perform AB tests, etc.).
- Deploy new content and changes from staging to production.
For additional information about maintenance in Kentico please refer to the Maintenance in Kentico article.