241 results found
-
App Insights alerts
Self-serve creation of alerts in App Insights based on specific thresholds exceeding a limit will help be proactive in responding to potential performance issues or other problems
11 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 -
Visual Builder: When changing style settings or property values in the outline panel, the left preview panel always refreshes
CMS SaaS: I have just converted my project from using @remkoj/optimizely-cms-nextjs to @optimizely/cms-sdk, but the live preview sync for style settings and property value updates is not as smooth as with @remkoj/optimizely-cms-nextjs.
Previously, my project worked very smoothly in Visual Builder mode. It only updated the element I changed and did not refresh the entire iframe.
However, after switching to @optimizely/cms-sdk, whenever I update anything, it always refreshes the preview iframe, resulting in a very poor user experience.
Is this expected behavior, or am I missing something?CMS 13: We’re seeing the same full iframe refresh issue on Optimizely CMS…
1 vote -
Copied pages to be Draft rather than Published by default
Global Digital Marketing Director.
When I copy and paste a page in the tree its status is always published or maybe it is the same of the page it is being copied from. I want to make the status of that page unpublished by default and then publish is manually later on, without requiring additional development work.
There have been other threads about this in the past eg https://world.optimizely.com/forum/developer-forum/CMS/Thread-Container/2018/5/copy-and-pasted-pages-always-have-published-status/
3 votes -
Disable Allowed Content Types Description in CMS 12 Edit View
In CMS 12 Episerver Edit interface we noticed a new feature: above all ContentArea fields, a description appears listing allowed content types (Refer attachment).We’d like to have this removed. It seems to add more confusion than clarity for our editors. We already enforce allowed content types using the [AllowedTypes] attribute in code, so displaying the full list in the UI—especially including unrelated options like Episerver Forms elements—is unnecessary and distracting.
This description wasn’t present in CMS 11, and we would prefer to maintain that cleaner editor experience.9 votes -
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 -
Ability to smoke-test more than 1 site during smooth deploy (slot domains)
Ability to smoke-test more than 1 site during smooth deploy (slot domains)
As a CMS developer and QA specialist we want to be able to smoke-test multiple sites so that we can detect potential issues on all our sites during deployment with DXP Cloud Platform to our multi-site CMS platform.
When we deploy to PREP/PROD we get a temporary SLOT to run our smoke-tests against. For example:
https://projectidprep-slot.dxcloud.episerver.net/
https://projectidprod-slot.dxcloud.episerver.net/
These are the default URL provided by Optimizely and are configured on the first website. We would like to be able to smoke-test multiple sites on the SLOT instance.
We could…
5 votes -
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 -
Assess binding settings to resolve resets
We need to evaluate whether setting the suggested Microsoft setting is worthwhile to resolve resets. As part of that effort, we would have to evaluate the risks of doing so.
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 -
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 -
Identify and Aid Customers with Production Live-Locks
There's the concept of a "dead" lock and a "live" lock. A live-lock is essentially a race condition within a production environment. It causes stair stepping of CPU usually until the server crashes.
This often happens when a developer accidentally uses a non-thread safe object in a multi-threaded manner.
The object (for example a HashSet) being used needs to be identified and a thread safe type needs to be replaced so that the live-lock goes away and the CPU goes back to normal.
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 -
Improve “Select All” behaviour for lazy loaded export
We’ve received reports from our users regarding confusion when exporting form submissions.
Currently, when users click the header “select all” checkbox, the label shows:
“All 25 posts are selected.”Because only 25 submissions are initially loaded, the checkbox correctly selects only these items. However, users often interpret this label as indicating that all existing submissions (e.g., all 69) have been selected - even though the remaining items have not yet been loaded via lazy loading. This misunderstanding has led to incorrect or incomplete exports.
To reduce user confusion and better reflect what is selected, we would like to request an…
2 votes -
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!
-
Search functionality to help finding needed content type
When there is several page and block types in use it would be easier to have search field so you could find correct content type effectively.
11 votes -
Insert an image into rich text editor from DAM
When the DAM Asset Picker is installed to the CMS, content authors should have the ability to "insert image" into a rich text field from the DAM, in addition to inserting from the CMS media library or uploading a new image.
7 votes -
Upload very large single files using cms
People are needing to upload very large files, such as video files and are running into Cloudflare file size limits.
Being able to upload a very large file into the storage blobs using the Deployment API and then being able to refer to it in the CMS may be a way to work around the size limits in Cloudflare.
The problem trying to do this now is that uploading via the deployment API won't make it into the same container that the CMS is configured to read from. Also, usually when people add media, a reference in the DB is…
4 votes
- Don't see your idea?