Umbraco 15 is out – and as always, we have upgraded our integration to support the new Umbraco version 👌

Besides the support of Umbraco 15, the new package also contains some new features and fixes, like support for the new RTE editor and the option to remove trailing slashes in the URLs. 

So, make sure to check out the Enterspeed package on Umbraco marketplace.

OBS, if you are using Umbraco 9 to 15, make sure to get the right package version 😉

Version 5.x is for Umbraco version is 14 or higher.
Version 4.x is for Umbraco version 9 to 13.

Umbraco has launched Umbraco 14 – and we have launched our integration for it 👌

The Umbraco 14 upgrade is a pretty significant step forward in their back office, which is now based on modern frontend technologies – but in the tried and tested Umbraco back office we all know (and love).

The Enterspeed Umbraco package is now updated and supports all versions from Umbraco 7 to Umbraco 14.

So, no matter if you’re looking to migrate a legacy Umbraco site or wish to utilise Enterspeed in a new and modern Umbraco 14 stack, we can support it 😊

In the Enterspeed Management App, we've introduced an Activity log. You find it under Settings > Activity logs. The Activity log allows you to go back in time and see all activities, such as the creation, updating, and deletion of schemas, environments, source groups, and more. You can see who made the changes and when they were made. For many logs, you can even compare the new and previous values before the change.

The new Activity log is based on the new Logs UI we introduced a couple of months ago, but the default columns and filters are adjusted to fit the purpose of an activity log. Just like you know it from the logs, you can filter on different properties, set a time interval, and add or remove columns in the list. For example, you can filter by user (actor) to see all changes by a specific user within a time interval. Selecting a log message brings up the side panel, where you can see more details about the log and use shortcuts to add columns to the list or filter by specific values.

Our hope is that the Activity log can be yet another tool to help you get a better overview of what's happening on your Enterspeed tenant.

You can now sign in to Enterspeed using your Microsoft Entra ID account! If you have a work account with Microsoft Entra ID, we encourage you to start using it for the Enterspeed app.

Setting it up is a simple two-step process:

• Click the Entra ID sign-in button
• Contact us via your Slack support channel or email us at support@enterspeed.com.

While we’re working our magic to associate your Entra ID sign-in with your tenants, you can still use your regular login and password—no need to panic ☺️

For more details, check out our Docs.

If you have logged in to your Enterspeed tenant this week, we are sure that you have already noticed what we are now announcing. But we enjoy launch announcements too much to just drop the feature without a post!

We have included 5 key metrics for your Enterspeed tenant:

• Number of source entities
• Number of Delivery API requests
• Data storage usage
• Queued jobs
• Delivery API availability and server response time

Keep an eye on your plan usage

All Enterspeed tenants have an associated plan, and instead of only being notified when you have crossed your usage limits, you can now keep an eye on your usage directly from the dashboard.

For source entities, this is a simple number of source entities currently ingested and a tick marking the limit on your specific plan.

The graph for Delivery API requests includes two numbers. First, the actual number of used Delivery API requests in the current month. Secondly, we calculate the projected number of Delivery API requests for the current month. It uses a simple forecast model by looking at the previous usage in the current month and projecting that to the end of the month. The tick marks the limit of Delivery API requests.

The third metric shows the current data storage for your tenant. The data storage is the size of all the ingest source entities and again, the tick marks the limit.

Queued jobs

Enterspeed prepares all data asynchronously so that website visitors don't have to wait. When new data is ingested or a schema is deployed, this triggers the processing and one or more jobs are added to the queue. When you ingest a large amount of source entities or deploy one or more schemas that trigger on a large number of source entities, you can now monitor the progress from the app.

Delivery API stats

Availability and performance are the foundation of Enterspeed, and we track these metrics rigorously internally. Now all of our users can follow the global availability and performance metrics across all tenants from the dashboard.

We want to add a small note to the Server response time metric. We monitor this from the Enterspeed application, so we can't include network latency, DNS, and SSL handshaking in this metric. If you want to monitor this, you need to use your own APM tools from the client side.

Let us know what you think

If you have any questions or feedback regarding the metrics dashboard, then we highly appreciate if you share it with us. Please reach out on your Slack support channel or via support@enterspeed.com

Enterspeed is no different from other software; things go wrong, and then you need to figure out why. So we are very happy to announce that you can now access the logs for our destinations the Enterspeed Management app.

If you just want to see how it works, then head over to Settings and the Logs section ➡️

If you want to read more about the feature, then we recommend reading our What to Do When Things Go Wrong blog post?

We're thrilled to announce this update: Destinations can now be configured via the management app 🎉

What are Destinations? They're your gateway to effortless integration with third-party services like Algolia and for custom integrations with Azure Service Bus, and Webhooks. With Destinations, pushing data where it's needed has never been easier.

Previously a feature by request, Destinations are now available to all tenants via the Enterspeed Management App.

Curious to learn more? Dive into our documentation on integrating with Enterspeed.

We are now opening for a public beta of an updated Management App: https://app.beta.enterspeed.com. We would very much appreciate your feedback on the new app, so please try it out and shoot us a message using your Slack support channel or via support@enterspeed.com.

Initially, you will not notice a lot of changes, but we have cleaned up the codebase to allow us new possibilities in the future. For now, we want to focus on delivering the same capabilities as you know today. We do want to highlight one feature that many users have requested: in the beta, it is now possible to sort source entities by updated date!

It is a beta, and we need your help to weed out the last potentially blocking bugs. We have been using the beta internally for a few weeks and already had a couple of our partners help test it out. Currently, all features more or less work as expected. We are aware of dark mode bugs, layout issues, and other minor issues. For example, signing up using the beta app is not supported.

You can simply go to https://app.beta.enterspeed.com and start using this as the primary app. You can use this URL until we launch this new app as the new default. We are particularly interested in knowing if you run into anything that makes you want to revert to the existing one. But any feedback is welcome!

Using the new app is very low risk, as you can always switch back to https://app.enterspeed.com if something is misbehaving.

And finally, a note for users who have been with us for a long time. You may risk being prompted by an "Unsupported Tenant" popup. This will happen if you are using a non-source group tenant. The popup will include a link to the old app, so it looks scarier than it is. All active tenants that are in scope for this popup have been contacted directly.

One of our essential focuses in Enterspeed has always been delivering content at high speed (heck, even our name includes speed). 

We want our customers and their users to be able to fetch content blazingly fast. To achieve this, we need to have the content deployed in the region where the user is located.

Most of our customers and their users are in the WEU region (West Europe), but we have also been lucky enough to serve customers in the SEA region (Southeast Asia).

Since our focus always has been speed, it seemed natural to deploy all of our customers' content to both regions to ensure the fastest speeds.

However, this is where our main focus conflicts with one of our other focuses - helping reduce our customers' carbon footprint by processing their data upfront. 

To achieve this, we must be mindful of where to store this data since delivering fast content takes processing power and storage. 

We're doing this by changing which delivery regions are enabled by default for our users.

As of today, the default delivery region for all new and existing tenants will be set to the WEU region (West Europe). 

This change will not affect tenants actively using the SEA region (Southeast Asia).

The SEA region (Southeast Asia) will still be available, but it will be enabled by request rather than by default.