Viewing the data usage
The data usage costs by customers is incurred by the amount of MBs 'consumed'.
The amount of MBs is monitored and displayed on the Licence usage level.
Procedure
1. Go to License usage level.
This level has three steps:
◦ Hits/MBs today
This step displays the amount of MBs incurred on the current day. At the end of each day, this list will be emptied and a new count is started.
◦ Daily summary
This step displays the a list of daily counts.
◦ Total license usage
This step displays a yearly summary of all daily counts and shows the maximum vs. the total consumed amount of MBs. Here, you can also set a Threshold, which is a percentage that you can set and which can be used for notifications (alerts).
Understanding the consumption of hits
To understand how the incurrence of hits works, it is good to know which actions count against consuming hits and which do not.
◦ What counts against consuming hits?
- When you make a connection with a third-party product such as Tableau, Excel, PowerBI and download data as part of that request.
- Refreshing a query, this will keep on drawing data from the data lake.
- Using the data lake to populate your own data warehouse.
◦ What does not consume hits?
- Synchronizing the data lake from the environment.
Access log vs. TSI: difference in data consumption
There is a difference in the consumed amount of data that is logged in the Access log (Environment Management gadget > Logs tab > localhost access log) and the License usage data in the TSI.
The difference is explained by the fact that the data we retrieve from the Mongo DB is counted and shown in the TSI. Planon has to pay for the transport between our Cloud environment and the Atlas cloud. The data is then transported to the client requestor, through OData, via the Tomcat Web server.
Depending on the amount of requested data, Tomcat will compress that data before sending it to the client requestor. The amount of data that is sent from Tomcat is the amount that can be found in the Access log.