103 results found
-
Dashboard for Enterprise Headless CMS
Enterprise CMS Headless architecture: Customer Dashboard for usage and platform health.
• Greater visibility and proactive reporting on their environment usage and performance. Specifically a dashboard (or reporting capability) that shows: • Usage/consumption metrics • Traffic patterns • Response times • Proactive monitoring data to help identify issues (e.g., 404 errors) before they become support tickets • The ability for customer teams to independently access this data, rather than having to request it from OptimizelyHaving this available standard vs. a custom build. This will help Enterprise customers shift from reactive issue handling → proactive management of their Optimizely environment
8 votes -
Application Insights - be able to sample or filter logged data
As a customer and implementation partner using DXP I would like either:
- a built-in tool somewhere, in the DXP portal, optimizely or Azure, to be able to filter out unwanted third party dependencies from being logged to the DXP Application Insights,
or
- the permissions to add our own sampling in Application Insights.
Optimizely DXP injects Application Insights (via required headers) and we cannot opt out of that. We don't have any way to sample the data logged to that Application Insights instance.
We get alerts about "DXC - Production Application Insight Daily cap reached" on logged data that is mainly…
1 vote -
Immutable Backups
Immutable Backups are increasingly becoming cybersecurity and resilience best practice.
Currently CMS PaaS data is not covered by immutable backups. To further protect us against ransomware attacks and accidental or malicious data tampering having this as a standard or at least optional feature would be highly desirable, providing a reliable last line of defense for fast and trustworthy recovery after a cyber incident or operational failure.
Any update on timeline for its availability would be very much appreciated.20 votes -
Add .NET Counter publication to App Insights on Startup
There are a whole suite of .NET counters available to use to publish to App Insights. This is a low-lift modification that enables us to gain many insights, directly inside of App Insights Metrics, we can utilize to diagnose issues on customers.
This enables us to do performance investigations that otherwise require manual intervention (such as downloading .ETL files and opening them in PerfView or capturing dump files and analyzing them).
We can skip these manual steps and jump write to "close to root causes" by publishing this information. There is little cost and no significant performance degradation associated with…
1 vote -
Dynamic Scaling in DXP - improve performance and reduce costs
The default hardware SKU for Optimizely is P1V3. P1V3 only has 2 cores and P2V3 has 4 cores. Because the number of cores available to the system dictates the number of default threads the system attempt to regulate, it would be best to deviate away from our current default hardware SKU, P1V3 to P2V3, instead. However, doing so would increase costs which we do not want to do necessarily. This is a proposal to decrease costs while simultaneously increasing hardware resources during peak hours.
The idea is to increase a customer's lower environment hardware to P2V3 during "working hours" (to…
1 vote -
Add Custom .NET Core Event Counters to CMS
In order for development teams to identify development issues within their implementation they need to be able to see under the hood of their implementation and inspect the qualitative metrics of their implementation.
Additionally, within our production environment, we should have a variety of metrics available to us to diagnose the quality of an implementation. These metrics would help guide our investigation as the
Currently, this is missing and we have major issues with partner and customer implementations because of it and our MTTR within our production environments is protracted because of the lack of this information.
We also need…
1 vote -
25 Production Service Buses Broken
We need to define what "working" means for a service bus so that reliability engineering can maintain reliability based on these metrics.
When a service bus no longer functions, reliability engineering should be equipped with the capacity to upgrade service buses in order to meet a component-specific SLA.
We need product management to define what "working" means for a service bus so reliability engineering can respond appropriately when a service bus is "broken" rather than having to go back to PM as though we need a exception for every broken service bus.
We also need monitoring in place to ensure…
1 vote -
Ensure Release Notes on nuget.optimizely.com
When navigating from a specific version of a DLL on nuget.optimizely.com. For example:
https://nuget.optimizely.com/packages/episerver.cms.ui.core/13.0.2
via the right-nav's Release Notes link that offers a filtered view of the packages, you see nothing in the filtered list.
Preferably, we should be eliminating this extra hop to have to click to the underlying page.
The release notes should be surfaced directly on the nuget.optimizely.com website so no further navigation is necessary.
Release notes for package should include an aggregation of all of the underlying changes' release notes.
This information should also be available within Visual Studio.
Without such information, developers can't know why…
1 vote -
IQI Report - App Insights as the Source of Truth
There are multiple similar functions happening that are similar within Optimizely. They all need to be utilizing the same data a the singular source of truth. They are:
Incident Management, primary data is App Insights.
Deep diagnostics done by Problem Management, primary data is App Insights
App Insights Dashboard
IQI Health Check reporting, primary information (aside from pingdom's availability info which for legal reasons) is Cloud Flare for health information.
The inconsistency of source data causes issues because we cannot make a consistent presentation of the information when the source being utilized is entirely different.
It also adds possibility of…
1 vote -
Fix NuGet Search UI on world.optimizely.com
Many deficits exist within the NuGet portion of world.optimizely.com.
An effort should be made to rectify the UX experience within the site to:
- Make it more user friendly.
2.) Make it so that our NuGet search functionality works appropriately within production.
For example, you should be able to filter the UI not just by the package name, but the DLL. See - https://docs.developers.optimizely.com/content-management-system/docs/nuget-package-families-in-cms
1 vote -
Down-Sampling Service Bus App Insights
Much of the log analytics costs come from voluminous amounts of service bus activity that is largely useless for analytics purposes. We could generally use a fraction of the analytics and we would be just fine.
For diagnostic purposes, we generally need to inspect the contents of the service bus itself to identify problems.
1 vote -
Consider shifting from Adaptive Sampling to Fixed Sampling
There's a known bug in Adaptive Sampling that prevents us from getting accurate analytics from App Insights. It largely calls the values of App Insights largely into question because we cannot tell when the metrics within App Insights are accurate or not.
Moving from Adaptive Sampling to Fixed Rate Sampling resolves this issue, but it also can cause an increase in log analytics and the possibility of exceeding the log quota.
If we can come up with a weekly way to determine the appropriate sampling rate for a given type of log data for a customer and tweak the analytics…
1 vote -
Identify and Communicate Crashing Instance Causes by Exception/Log Inspection
Due to my elevated level of access nobody on the team gets these errors emails from Microsoft except Erik.
We need an easy way to address these with customers through the ticketing system.
These are causing instances crashes for the sites. Here's an example of what's happening on moco.
Here are the email threads I'm receiving from Microsoft that shows they're having outages.
1 vote -
Visible in menu should be available in Graph
In CMS 13 the VisibleInMenu PageData property is not indexed.
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Expose categories in Graph
Categories are part of CMS 13 but they're not supported by Graph yet. We use them for filtering content.
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
When there are errors on the servicebus we don't log it. It would help if we logged errors for troubleshooting purposes.
When there are issues with the servicebus it is not possible to see what went wrong many times. You can go to the servicebus and look at the graph and see that there are "server errors" and "user errors" and "throttled messages"but there is no way to see the details of the server errors or the user errors.
Some times we can see a log entry in the CMS logs but not always and I guess it depends on the type of error.
If we had more information it would help when troubleshooting customers having problems with the servicebus.14 votes -
add button ID property
Analytics requires us to differentiate between different CTA buttons on a page that may go to the same destination (e.g. event "register today"). Please ad a button-ID property in the standard link interface (page, external link, media, remaining URL, etc.) We cannot use UTM-like properties as that breaks tracking within a current session. This is very standard in other CMSs.
1 vote -
send alerts when sync jobs fail
We want alerts to be sent via email and or our incident io pager system when sync jobs fail. Now, we have to look in every job's history to see if any sync jobs fail.
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Real-Time Audiences from ODP to CMS: respecting cookie consent for personalization
Real-time audiences can be synced from ODP to CMS via a NuGet package (https://docs.developers.optimizely.com/optimizely-data-platform/docs/odp-cms). This enables audiences created in ODP to become selectable in the CMS's Audiences setting.
The CMS's Audiences setting doesn't take account of cookie consent configurations at all, however. This creates a problem for configuring personalization in the CMS with synced ODP audiences.
ODP audiences may opt out of personalization in their cookie consent preferences. But if personalization is configured in the CMS, the personalized view will still display for those who have opted out.
(This is not an issue with Web Experimentation, as Web…
1 vote -
Allow disabling warmup for integration and preproduction
Integration and preproduction environments are sometimes protected by IP-whitelists and in those cases the warmup step always fails with status code 401. The warmup system waits for about 15 minutes until these requests time out. This increases delivery times to these environments specially when CI/CD is set up.
Ex:
2026-03-10 12:40:24 Information Starting to warm up the targets slots...
2026-03-10 12:40:25 Information Preparing target slot for Go Live (<masked>/slot) (warming up the slot)
2026-03-10 12:52:21 Warning Timed out waiting for all instances for webapp <masked> and slot "slot" to become ready!
2026-03-10 12:52:21 Information Validating deployment ID uniqueness between slots…7 votes
- Don't see your idea?