Xperience.cloud: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Setup= | =Setup= | ||
==2FA, Multi- oder Zwei-Faktor-Authentifizierung== | ==2FA, Multi- oder Zwei-Faktor-Authentifizierung== | ||
| Line 13: | Line 11: | ||
==3Q Streaming Provider== | ==3Q Streaming Provider== | ||
{{:3Q (Streaming Provider)}} | {{:3Q (Streaming Provider)}} | ||
=Hosting= | |||
==Performance Log== | |||
{{:xperience.cloud - Hosting Performance Log}} | |||
Revision as of 10:11, 8 February 2021
Setup
2FA, Multi- oder Zwei-Faktor-Authentifizierung
Login
https://www.twilio.com/console
Ask Sebastian Druschel or David Smith for your user account.
Setup for the xperience.cloud
Setup a Alpha Sender ID (Showing a Name instead of a Number as SMS Sender)
Please mind that Alpha Sender ID's does not work global. For Details read here: https://support.twilio.com/hc/en-us/articles/223133767-International-support-for-Alphanumeric-Sender-ID.
- Goto Messaging Services: https://www.twilio.com/console/sms/services
- "Create a Messaging Service", if non exists for your Client. Mind to use our Agentursoftware Common Client Name.
- "Add Senders to Service" and choose "Alpha Sender" as "Sender Type".
- Add your senders name to the "Sender Pool", please mind that there is a max of 11 characters.
- Add one or more Long Code Fallback Senders to your "Sender Pool"
- Choose "Messaging Services"/"Properties" to get the "Messaging Service SID".
- Configure "(Global) Event Settings"/"Twilio (SMS/ Voice) Seetings"/"Alpha Sender ID (Messaging/ Messaging Services/ SID)" in your xperience.cloud Subsite.
- Test!
Cookie Consent Bar
Setup Usercentrics for the xperience.cloud
Due to mission Multisite Support, Usercentrics is configured to show a generic Cookie Consent Bar pointing to two relative url's.
- The "Cookies Policy" is pointing to /cookie-policy/
- The "Privacy Policy" is pointing to /privacy/
Due to this relative url's, the link will point to https://{your_sites_url}/cookie-policy/ and https://{your_sites_url}/privacy/. If you have to forward this urls to a different location, e.g. an url or pdf, please use the "Redirection" Plugin:
- Goto "Tools"/"Redirection"
- "Add New"
- "Source URL": /cookie-policy/ or /privacy/
- "Query Parameters": "Exact match all parameters in any order"
- "Target URL": Your Target URL. If you point to an url within your xperience.cloud Subsite, please use a relative url.
- "Group": "Redirections" or something else. Important! All Groups must use "Module" for redirects.
Modules
Streaming
3Q Streaming Provider
Generell kann die xperience.cloud mit jedem Streaming Provider streamen und jedes VOD Format integrieren.
Gute Erfahrung für das Live Video Streaming in Europa haben wir mit 3Q erzieht.
Setup
"Video Livestream" Projekt anlegen. Folgende Parameter sind wichtig:
Eingangssignal/Stream Typ
| RTMP PUSH von Ihrem Encoder | Der normale RTMP Stream aus bsp. OBC oder Wirecast. |
| RTMP PUSH von Ihrem Encoder mit Low-Latency | "Low-Latency" bezieht sich auf den Wiedergabe Puffer, das Video hat also weniger Latenz beim User. Zwischen Aufnahme und Wiedergabe liegt also weniger Zeit. Dies kann insbesondere bei Live Interaktionen (Chat, Live Components, ...) wichtig sein. |
| SRT | Sofern möglich unterstützt 3Q auch SRT. |
Billing Template (Streaming)
| EUR | ||
|---|---|---|
| Live Video Streaming Setup | EUR 200,00 | Event |
| Transcoding/ Minute (6 Auto-Transcoder) | EUR 0,04 | Minute |
| Bandwidth/ GB | EUR 0,10 | GB |
| Handlingfee Live Streaming | 10% |
Billing Template (VOD)
| EUR | Einheit | |
|---|---|---|
| Bandwidth/ GB | EUR 0,10 | GB |
| Storage | EUR ?? | GB |
| Encoding | EUR ?? | Minute |
Hosting
Performance Log
| AWS/ EFS (MiB/Sek) | AWS/ RDS | AWS/ ElastiCache/ Redis | AWS/ EC2 | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Event-Datum | Event-Name | ca. Teilnhemer | Bereitgestellt | Max. Auslastung | Bereitgestellt | Max. Auslastung (CPU) | Bereitgestellt | Max. Auslastung (CPU) | Bereitgestellt | Max. Auslastung (CPU) | xpcl.service. | xpcl.matomo. |
| StandBy Config | 50 MiB/s | db.m6g.large | cache.t2.small | 2 * c5.2xlarge | ||||||||
| 20.01.2020 | https://www.brandsummit2021.com | 2.500 | 100 MiB/s | 6% | db.m5.xlarge | 1% | cache.t2.small | 16% | 4 * c5.2xlarge | 8% | 3,7% | 60% (Fixed with "Number of requests that are processed in one batch: 150") |
| 09.02.2021 | https://mitgeredet.schalke04.de | 3*1.000 | ||||||||||