Enterspeed Product Updates logo

Product Updates

See the latest new features, improvements, and product updates

Subscribe to Updates

Labels

  • All Posts
  • Fix
  • Feature
  • Improvement
  • Announcement
  • Product Update
  • 🤫 Teaser
  • 🛠 Service
  • 💡 Tip

Jump to Month

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • April 2023
  • January 2023
  • November 2022
  • September 2022
  • June 2022
  • March 2022
  • January 2022
  • December 2021
  • November 2021
Powered️ byAnnounceKit

Create yours, for free!

Announcement
8 months ago

Sign in with Microsoft Entra ID Now Available

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.

Avatar of authorEnterspeed
Improvement💡 Tip
9 months ago

Do you know what route is actually being used?

Sometimes, you end up creating duplicates, when you create URLs and handles from a large CMS installation and various other sources in the Enterspeed Management app. In the app, URLs and handles are collectively referred to as routes, and these routes are created during processing. Enterspeed allows developers a lot of flexibility in creating routes, but since Enterspeed relies on the source systems, it'll generate duplicate routes if that’s how the data is structured.

It requires careful developers consideration, when you create the correct route since everything happens asynchronously, without direct human oversight, and across multiple data sources. Over the past few months, we've tweaked almost every part of our route processing to provide developers with clear insights into the routes that are created.

Below is an example from the Route inspector that shows the duplicates, the schema, and the source entity from which the route originates.




Avatar of authorEnterspeed
FeatureImprovement
9 months ago

Easier debugging of JavaScript schemas with console support

When debugging JavaScript it's often useful to use the console object to print out values to the console.

With the latest update, we've now added support for this when using the Test schema feature in the Enterspeed Management App. We hope this'll make it easier for you to debug and test your schemas.

You can read more about the console object support and see examples on the Enterspeed doc site.

Avatar of authorEnterspeed
Feature
9 months ago

Working with strongly typed custom properties in your schemas

By default, you get IntelliSense in the Enterspeed JavaScript schemas by the @type expression defined in the top of the schemas (/** @type {Enterspeed.FullSchema} */). However, this only provides IntelliseSense for the functions and the known properties of the source entity – not the custom properties containing all the data of a source entity.

With the introduction of the new generic versions of the Enterspeed schema types, you can now work with strongly typed custom properties in your schemas by providing a type for your source entity described in JSDoc (/** @type {Enterspeed.FullSchema} */).

If you are working with strict types of your source entities, this could be useful and make it easier for you to work with your schemas as you get IntelliSense and defined types on custom properties which could also prevent potential errors.

You can read more about the JSDoc support and see examples on the Enterspeed doc site.


Avatar of authorEnterspeed
FeatureImprovement
10 months ago

Log improvements: Filters and custom columns

The log viewer in the Enterspeed Management App just received a huge update 🪵

The update focuses on two things: Making it easier to find the right logs, and making it easier to get an overview of the logs.

With the new update, you can now filter on a long list of properties – and not only level, service, and source entity id as before. You can add multiple filters, select operators like is, is not and in – and you can even add filters directly from a specific log entry in order to find logs with similar values. This should improve your chance of finding the log entries you are logging for quite a bit. And not only a single log entry, but also other log entries leading up to the event in order to figure out what started it.

The log list has a set of default columns (Timestamp, Level, Service and Message), but from a specific log entry, you can now toggle any property to be visible in the list as well. This'll give you a better overview when you begin to dig into the list of log entries.

Besides the two new main features, there's a long list or minor improvements, like filtering on relative time intervals, improved navigation options to related objects, and more readable teaser messages.

Go ahead and check it out. We hope you enjoy the new update 🚀

Avatar of authorEnterspeed
Feature
a year ago

Search in schemas: Find the schemas you are looking

Quickly finding the right file is important in order to work efficiently in any code base and the same goes for the schemas in Enterspeed.

On the Schemas page you can now click the small Search in schemas icon to the right of the search field in order to search by content.

This means the you can now find all schemas with a trigger on a specific source entity type or all schemas with a reference to a specific schema or partial schema that you are maybe considering changing or deleting.

The search result is displayed nicely with highlighting of the specific lines where a match was found.

Avatar of authorEnterspeed
Product Update
a year ago

New Destinations Available

We continue to expand the list of destinations that you can setup directly in the Management app. Today, we have added two new destinations:

1️⃣ Elastic Search

2️⃣ Clerk.io

Read more about how to use these destinations in our documentation.

Avatar of authorEnterspeed
FeatureAnnouncement
a year ago

New Metrics Dashboard

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

Avatar of authorEnterspeed
ImprovementAnnouncement
a year ago

Logging for Destinations

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?

Avatar of authorEnterspeed
Product Update
a year ago

New Destinations Available

Only last week, we announced the availability of creating and managing the Algolia, Azure Service Bus, and Webhooks destinations via the Management app. Today, we are expanding the list of destinations to include:

1️⃣ Relewise

2️⃣ Typesense

3️⃣ Elastic App Search

Read more about how to use these destinations in our documentation.


Avatar of authorEnterspeed