6 results found
-
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 .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…
2 votes -
DXP Management Portal
Restart Site - Have "Restart one instance at a time" be checked by default since not checking this can cause serious issues upon restart.
Also adding the checkbox state to the confirmation message so users are aware.
1 vote -
Request for Wildcard Hostname Support on DXP
Wildcard hostnames are not supported on DXP, and all configured hostnames must be explicitly mapped in the CMS admin.
We will have thousands of customers for whom we will be setting up individual sites. Is it possible to configure a wildcard entry on DXP—such as *.procase.riogrande.com—to support this model? Managing tens of thousands of individual URLs in Optimizely DXP would be difficult for both Opti and us, and it would significantly increase our customer onboarding time.
1 vote -
Alerting for suspicious bot traffic spikes
Customers never get alerted to suspicious traffic spikes unless they impact site speed or uptime.
Ability to establish alerting for suspicious attacks, even if they are addressed by cloudflare before they impact site performance.9 votes -
3 votes
- Don't see your idea?