You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- missing folders to structure the content artefacts fixed
13
+
14
+
* various updates and improvements
15
+
* missing folders to structure the content artefacts fixed
13
16
14
17
## Description - What is the Monitoring Content About?
18
+
15
19
It offers a configuration that persists data from various monitoring relevant tables and views.
16
-
- This persistence runs are delta enabled (by timestamp)
17
-
- Task chains are defined to schedule the update
18
-
- The data rentention time is configurable: you can define for how many days you like to keep persisted data. This insures that the data volume is kept in fixed boundaries.
20
+
21
+
* This persistence runs are delta enabled (by timestamp)
22
+
* Task chains are defined to schedule the update
23
+
* The data rentention time is configurable: you can define for how many days you like to keep persisted data. This insures that the data volume is kept in fixed boundaries.
19
24
20
25
The data to persist can be sourced from two different systems. Assuming you have a dev. and prov. environment, you can create the content in one of these tenants, and collect the data from both. One place to define views and e.g. stories to run evaluations for data from both tenant.
21
26
@@ -24,56 +29,67 @@ The data to persist can be sourced from two different systems. Assuming you have
24
29
In addition, several dimension tables are populated to enable a consisten reporting approach and to model something like a star-schema in the fact view. Examples are DATE, TIME, SPACE, STORY and WIDGET information and more.
25
30
26
31
For reporting
27
-
- Two access modes (persisted only or including real time data) are supported
28
-
- Data Access Controls to protect your data are delivered as well. You just need to assign them to the respective view
29
-
- Protection patterns like "Admin Access", "access to my data only" or to a "group of spaces" have been implemented.
32
+
33
+
* Two access modes (persisted only or including real time data) are supported
34
+
* Data Access Controls to protect your data are delivered as well. You just need to assign them to the respective view
35
+
* Protection patterns like "Admin Access", "access to my data only" or to a "group of spaces" have been implemented.
30
36
31
37
## Details
38
+
32
39
Please check the attached presentation for more detailed information on the Monitoring Content.
33
40
34
41
## Connectivity
42
+
35
43
SAP HANA Cloud in one or more SAP Datasphere instances.
36
44
37
45
## Download/Install Instructions
46
+
38
47
Please check the general documentation [here](https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/42093f14b43c485fbe3adbbe81eff6c8/ef516563b3fe4c69b6f718f17ed94cdf.html).
39
48
Please follow the setup and configuration instructions below to setup the SAP Datasphere Monitoring Content.
40
49
41
50
## Initial Setup of Monitoring Content
42
51
43
52
### Space and User Setup
44
-
- If it does not exist, create the space **SAP_ADMIN (Space Name: Administration (SAP)** and enable as "Monitoring Space".
45
-
- Ensure your SAP Datasphere user has sufficient privileges to access and configure content.
53
+
54
+
* If it does not exist, create the space **SAP\_ADMIN (Space Name: Administration (SAP)** and enable as "Monitoring Space".
55
+
* Ensure your SAP Datasphere user has sufficient privileges to access and configure content.
46
56
47
57
### Space Configuration (mandatory)
48
-
- HANA Connection for fetching data from a separat tenant:
49
-
- Create an analysis user and note down the HANA server and user/passwort
50
-
- if you are using a remote system: create analysis user in the remote datasphere system
51
-
- if not: create an Analysis User in your current datasphere system (workaround, required once for deployement of tables, can be adjusted later)
52
-
- Ensure that the DigiCert Global Root CA and DigiCert Global Root G2 are uploaded in SAP Datasphere - see also [here](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-security-guide/secure-communication-between-sap-hana-and-sap-hana-clients) and [here](https://www.digicert.com/kb/digicert-root-certificates.htm)
53
-
- Update the Remote Connection REMOTE_MONITORING_DATA with the Analysis User credentials
54
-
- Use the information of the Analysis User
55
-
- Save, deploy and verify that the connection is valid
58
+
59
+
* HANA Connection for fetching data from a separat tenant:
60
+
61
+
* Create an analysis user and note down the HANA server and user/passwort
62
+
63
+
* if you are using a remote system: create analysis user in the remote datasphere system
64
+
* if not: create an Analysis User in your current datasphere system (workaround, required once for deployement of tables, can be adjusted later)
65
+
66
+
* Ensure that the DigiCert Global Root CA and DigiCert Global Root G2 are uploaded in SAP Datasphere - see also [here](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-security-guide/secure-communication-between-sap-hana-and-sap-hana-clients) and [here](https://www.digicert.com/kb/digicert-root-certificates.htm)
67
+
* Update the Remote Connection REMOTE\_MONITORING\_DATA with the Analysis User credentials
68
+
* Use the information of the Analysis User
69
+
* Save, deploy and verify that the connection is valid
56
70
57
71
### Update existing remote/local tables (only mandatory if already in the repository)
58
72
59
73
Views with recently added columns require a metadata refresh:
60
-
- TASK_LOGS_V_EXT: Refresh the definition to ensure that we are on the latest status
61
-
- TASK_SCHEDULES_V_EXT: refresh the definition to ensure that we are on the latest status
62
-
- M_MULTIDIMENSIONAL_STATEMENTS
74
+
- TASK\_LOGS\_V\_EXT: Refresh the definition to ensure that we are on the latest status
75
+
- TASK\_SCHEDULES\_V\_EXT: refresh the definition to ensure that we are on the latest status
76
+
- M\_MULTIDIMENSIONAL\_STATEMENTS
63
77
64
78
Hint: The update can be triggered from the datasphere design time UI. Navigate to the view/table and press the "refresh" button. A dialog might come up and ask you which changes to consume. Select all and save and re-deploy the table.
65
79
66
80
Remote tables which have been replicated already - but with a different technical name. It is not possible to have one remote table imported two times with different names. Hence we have to resolve this conflict.
67
81
68
-
Example for the conflict: The table M_MULTIDIMENSIONAL_STATEMENT_STATISTICS have been replicated using the technical name M_MULTIDIMENSIONAL_STATEMENT_S. The content expects now M_MULTIDIMENSIONAL_STATEMENT_STATISTICS.
82
+
Example for the conflict: The table M\_MULTIDIMENSIONAL\_STATEMENT\_STATISTICS have been replicated using the technical name M\_MULTIDIMENSIONAL\_STATEMENT\_S. The content expects now M\_MULTIDIMENSIONAL\_STATEMENT\_STATISTICS.
69
83
70
84
Resolving options:
71
-
- Create a view M_MULTIDIMENSIONAL_STATEMENT_STATISTICS which wraps the remote table M_MULTIDIMENSIONAL_STATEMENT_S. During the import of source tables, skip the import of the remote tables.
72
-
- Rename the source table and adjust your existing scripts and views.
85
+
86
+
* Create a view M\_MULTIDIMENSIONAL\_STATEMENT\_STATISTICS which wraps the remote table M\_MULTIDIMENSIONAL\_STATEMENT\_S. During the import of source tables, skip the import of the remote tables.
87
+
* Rename the source table and adjust your existing scripts and views.
73
88
74
89
### Import Source Table Definitions
90
+
75
91
Once you have finished the space configuration, we are ready to import the content.
76
-
First import the source tables using the .package file **SAP_CC_DSP_Monitoring_Source_Tables.package**. It's recommended to choose the import option "do not overwrite existing content".
92
+
First import the source tables using the .package file **SAP\_CC\_DSP\_Monitoring\_Source\_Tables.package**. It's recommended to choose the import option "do not overwrite existing content".
77
93
78
94
Hint: On the import dialog, navigate to the second tab "Import Options" and select the option "Deploy after import".
79
95
@@ -82,81 +98,91 @@ All tables need to be available and deployed before starting the import of the v
82
98
### Import Configuration of Data Inbound
83
99
84
100
Let us continue with the full configuration of the inbound part of the monitoring data:
85
-
Import the .package file **SAP_CC_DSP_Monitoring_Reporting_Tables.package** and don't forget the check the flag for automatic deployment.
101
+
Import the .package file **SAP\_CC\_DSP\_Monitoring\_Reporting\_Tables.package** and don't forget the check the flag for automatic deployment.
102
+
86
103
87
104
88
105
**A brief introduction to the folder structure:**
89
-
- Each folders with leading number represent a source table. The name of the source table is part of the folder name.
90
-
- Folder **Dimensions** contains all dimensions defined for reporting purposes
91
-
- Folder **DataReplication** contains all dataflows required to update the replicated date
92
-
- Folder **Configuration** contains all configuration tables.
106
+
107
+
* Each folders with leading number represent a source table. The name of the source table is part of the folder name.
108
+
* Folder **Dimensions** contains all dimensions defined for reporting purposes
109
+
* Folder **DataReplication** contains all dataflows required to update the replicated date
110
+
* Folder **Configuration** contains all configuration tables.
93
111
94
112
We have finished the inital import of the reporting entities. The next chapter describes the initial configuration of the content, how to enable authorization on the data and how to schedule the replication.
95
113
96
114
## Configuration of Monitoring Content
97
115
98
116
### Mandatory: Days to keep data and Source Selection
99
-
- Upload or manually enter the following rows into table CONFIGURATION. Select via true/false which source should be loaded.
100
117
101
-
| Name | Value | Enabled |
102
-
| ---- | ----- | ------- |
103
-
|KEEP_HISTORY_DAYS|30|true|
104
-
|LOAD_FROM_LOCAL_HOST||true/false|
105
-
|LOAD_FROM_REMOTE_HOST||true/false|
118
+
* Upload or manually enter the following rows into table CONFIGURATION. Select via true/false which source should be loaded.
119
+
120
+
|Name|Value|Enabled|
121
+
|-|-|-|
122
+
|KEEP\_HISTORY\_DAYS|30|true|
123
+
|LOAD\_FROM\_LOCAL\_HOST||true/false|
124
+
|LOAD\_FROM\_REMOTE\_HOST||true/false|
106
125
107
-
If you have only local data, set LOAD_FROM_REMOTE_HOST = false and LOAD_FROM_LOCAL_HOST = true.
126
+
If you have only local data, set LOAD\_FROM\_REMOTE\_HOST = false and LOAD\_FROM\_LOCAL\_HOST = true.
108
127
109
-
The proposed value to keeping history is set to 30 days. To understand the data volume created by the replication, see chapter 
128
+
The proposed value to keeping history is set to 30 days. To understand the data volume created by the replication, see chapter !\[](#Retention Time of Data)
110
129
111
130
### Mandatory: Schedule Data Replication
112
131
113
132
In the folder "Monitoring Inbound" => "DataReplicatoin" you will find a set of task chains. Schedule them to run e.g. every hour.
114
133
115
134
Thoughts about the frequency:
116
-
- It needs to be faster than the retention time of the source. E.g. if the M_EXPENSIVE_STATEMENT will contain data for the past 5 hours, the scheduling should be below e.g. 3 hours (for safety)
117
-
- When using Real-time access, the data volume fetched remotely is higher and hence the performance is reduced
135
+
136
+
* It needs to be faster than the retention time of the source. E.g. if the M\_EXPENSIVE\_STATEMENT will contain data for the past 5 hours, the scheduling should be below e.g. 3 hours (for safety)
137
+
* When using Real-time access, the data volume fetched remotely is higher and hence the performance is reduced
118
138
119
139
### Optional: Addition manual configurations
120
140
121
-
User friendly text for DATABASE_ID and HOST
122
-
- After the initial load, the dimension HOST_DIM is filled.
123
-
- Open the dimension in the table editor and manually change the default text for the database_id. It will not be overwritten during a subsequent load.
141
+
User friendly text for DATABASE\_ID and HOST
142
+
143
+
* After the initial load, the dimension HOST\_DIM is filled.
144
+
* Open the dimension in the table editor and manually change the default text for the database\_id. It will not be overwritten during a subsequent load.
124
145
125
146
Grouping of Spaces
126
-
- A space group is automatically derived from the space_id. Rule is to use substring before first underscore ('_') as group id.
127
-
- Example: SAP_INBOUND, SAP_HARMONIZE and SAP_REPORTING will all have the GROUP SAP.
128
-
129
-
Authorizations: HANA Application User
130
-
- The data accessc control TCT_DAC_APP_USER_DAC can be used to control access to data, where an application user is available. This is typically the case for HANA statistic views.
131
-
- Default Authorization: Every User can see his on data => no configuration required
132
-
- Admin Authorization: Add application user to table TCT_DAC_ADMIN_USERS_LOC => full access to data
133
-
134
-
Authorizations: Spaces
135
-
- The data access control TCT_DAC_SPACE_DATABASE_DAC can the used to controll access to data, where a space is available.
136
-
- Per default, all access is blocked
137
-
- Admin Authorization: Add application user to table TCT_DAC_ADMIN_USERS_LOC => full access to data. Note that this is the same tables as used for the HANA application user.
138
-
- User specific authorization: Add application user, space group and database id to table TCT_DAC_SPACE_GROUP_LOC.
139
-
140
-
### Retention Time of Data
141
-
142
-
The default proposed is 30 days. The major limit here is the data volume (on disc) you like to spend to monitoring data. Below you find typical groth rates in terms of records count and memory per persisted table (naming *_LOC):
143
-
144
-
|Table Name|Disk Usage per x records|Records per Day|Disk Usage per Day|
* A space group is automatically derived from the space\_id. Rule is to use substring before first underscore ('\_') as group id.
149
+
* Example: SAP\_INBOUND, SAP\_HARMONIZE and SAP\_REPORTING will all have the GROUP SAP.
150
+
151
+
Authorizations: HANA Application User
152
+
153
+
* The data accessc control TCT\_DAC\_APP\_USER\_DAC can be used to control access to data, where an application user is available. This is typically the case for HANA statistic views.
154
+
* Default Authorization: Every User can see his on data => no configuration required
155
+
* Admin Authorization: Add application user to table TCT\_DAC\_ADMIN\_USERS\_LOC => full access to data
156
+
157
+
Authorizations: Spaces
158
+
159
+
* The data access control TCT\_DAC\_SPACE\_DATABASE\_DAC can the used to controll access to data, where a space is available.
160
+
* Per default, all access is blocked
161
+
* Admin Authorization: Add application user to table TCT\_DAC\_ADMIN\_USERS\_LOC => full access to data. Note that this is the same tables as used for the HANA application user.
162
+
* User specific authorization: Add application user, space group and database id to table TCT\_DAC\_SPACE\_GROUP\_LOC.
163
+
164
+
### Retention Time of Data
165
+
166
+
The default proposed is 30 days. The major limit here is the data volume (on disc) you like to spend to monitoring data. Below you find typical groth rates in terms of records count and memory per persisted table (naming \*\_LOC):
167
+
168
+
|Table Name|Disk Usage per x records|Records per Day|Disk Usage per Day|
0 commit comments