225 results found
-
Size estimates on CMS pages/media before deployment/publish
For a developer, or CMS editor: Is it possible to get a size estimate of the page, media etc before deployment, so that our teams dont accidentally publish something which has a huge size (like 2 TB) and impacts performance
2 votes -
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 -
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 -
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 -
Align IQI Health Check with Dashboard Actionable Reports
Currently, the IQI report offers information such as a breakdown of HTTP status codes. Unfortunately, that does not offer the customer or partner information they can actively take action on because it requires further investigation on their part to make it actionable.
We want to bridge the gap between the data and being able to take action, on our side. The information we offer within the Dashboard is much closer to directly actionable, in many cases it is directly actionable.
For example, on the dashboard we offer a EpiCms database deadlock report. The customer or partner needs to identify which…
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 -
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 -
Visible in menu should be available in Graph
In CMS 13 the VisibleInMenu PageData property is not indexed.
1 vote -
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 vote -
Editor Content Health Dashboard : A personalized, self-service governance view for every content editor in the CMS
As a content editor, I want to see a personalized dashboard when I log in to the CMS that shows me only the content I own that needs attention, so that I can find and fix issues myself, without waiting for someone else to tell me about them.
This dashboard replaces the generic default view in the CMS for all content editors. It does not replace any existing admin tools or reports. The intent is to move content governance from a reactive, admin-led activity into a proactive, editor-led habit. The dashboard is the trigger for that behavioural shift. This is…
1 vote -
Improve the visibility of image thumbnails in the Media Panel.
Our content editors rely on thumbnails in the Media Panel to identify images. However, the current view makes this difficult, as the thumbnails are too small. While it is possible to open each image to view it in full size, this process is inconvenient and time-consuming. Providing larger thumbnails would make image identification much easier and more efficient.
Suggestion: Provide an option to enlarge thumbnails for better visibility.
1 vote -
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
- Don't see your idea?