As of December 3rd, 2018, PHP 7.0 has reached its end of life. This means it will no longer have security support and could be exposed to unpatched security vulnerabilities.
Additionally, as of December 31st, 2018, PHP 5.6 also reached its end of life. By the way, the first version 5.0 was launched 14 years ago.
root360 continues to provision PHP 7.0 and PHP 5.6 until mid of 2019 at no extra costs. This enables all customers to plan and migrate to PHP 7.1 or higher and regain security support. During your upgrade phase and required testing, we recommend to first update your local development or staging installation.
Get back to us at https://support.root360.cloud if we can support you planning your upgrade to PHP 7.1+.
Today will implement a feature that many of our docker customers have requested.
Until now a failed deployment caused a rollback to a previous version and returned exitcode 0 to your CI/CD pipelines. This caused troubles since your initial deployment did fail and the failure couldn't automatically be recognized by your toolchain. Therefor we changed the behavior so that a rollback is no longer marked as "OK". The rollback will now return exitcode 3.
A docker deployment can now reach the following states:
If you have further questions feel free to contact us at support.root360.cloud.
root360 offers for all managed environment a central logging service  to support flexible cloud resources.
The free logging service merges logs from all instances to one place at bastion host for each environment - this happens at real time for all registered log files of all roles and instances. Also the service automatically masks IP addresses in the compressed log files used for long-term logging. With this feature central logging service ensures compliance with GDPR (DSGVO) requirements and stores only masked IP addresses like 162.158.xxx.xxx
Starting today we will roll out a hotfix for the root360 central logging system which prevents mixed logs during masking process for some customers. The new process adds multiple validations which causes a slightly higher resource consumption at affected bastion hosts.
It might be required to reboot the bastion host which causes a very short downtime.
This might break any persistent SSH connections (e.g. SSH tunnel/OpenVPN) to your bastion host so you will be required to reconnect your service.
We plan to finish the whole roll out until 15th of February.
If you have further questions, please get in touch with us at https://support.root360.cloud
We are currently experiencing failing deployments due to a broken Ubuntu package. At the moment all deployments will fail. This has no impact on your currently running releases, so no downtime or other issues are to be expected. Nether the less please do not run deployments until further notice.
We will keep you updated.
18:02 We have successfully recovered package availability for all deployments and started internal measures to prevent further service disruptions caused by package maintainers.
We are always working to provide best and most efficient services at AWS for all customers.
In order to provide most recent features, higher security and higher performance for your application, we have updated our default settings to the following:
This change will NOT affect already provisioned resources but will be automatically applied when new resources are created.
When you have further questions, please get back to us at https://support.root360.cloud
19.11.2018: Additionally we have increased default version for memcached to 1.5 with AWS support (https://aws.amazon.com/about-aws/whats-new/2018/11/memcached15nowavailableonamazonelasticache/)
We released new features for our dashboard "Orbiter". The Orbiter now offers the possibilty to list all existing snapshots of a database instance. Further the public ip address of the bastion host is shown in the Orbiter.
By clicking the snapshots button all snapshots will be displayed in a separeted pop-up.
The pop-up shows all available snapshots with additional information about them, including the important time of creation. By clicking the relevant snapshot identifier a new view will be displayed.
This view provides the ability to copy the restore command for the specific snapshot. This command has to be run on the bastion host to create a new database beside the exisiting to access the restored data.
The Orbiter now shows the public ip address of the bastion host. There is a link to our knowledge base, which discribes how to connect via ssh to the environment, too.
With the release of Tideways 5, our customers now have the opportunity to use the new features of Tideways 5 to monitor the performance of their applications and to debug them on their server.
Tideways 5 now offers a more detailed view of the metrics:
Analyse traces to find long lasting querys and which component is involved:
If you already use Tideways and would like to upgrade to version 5, then you can contact our support and upgrade them.
For questions about Tideways, please contact our customer service at https://support.root360.cloud
Find more information about Tideways 5 on https://tideways.com/profiler/...
capturing more data in monitoring mode
always capture the total performance of SQL, HTTP, Redis, Memcache, File I/O and other downstream services for monitoring purposes
simpler and better transaction naming
On Monday we released new features for our dashboard “Orbiter”. Now, it offers even more details about your AWS infrastructure in one compressed view.
With the update “Orbiter” gives you more insights in your Docker containers. You can keep an eye on the workload of your containers run on ECS on our own. If you think limits should be adjusted, just let us know.
You can also monitor your CDN and Elastic Search in the “Orbiter”.
Our work at the “Orbiter” is still not finished. In the next release we are planning to add ECS Log Files and an overview about backups and how to restore.
Integration of ECS (Elastic Container Service)
Integration of CDN (CloudFront) & Elastic Search
Storage information for EC2 instances
We got a lot of feature requests concerning the default configuration of our servers.
Today we'll release changes that implement most of those requests.
The new configuration includes: