Platform

Platform

A place for Apptio product users to learn, connect, share and grow together.

 View Only
Back to Library

DataLink 4.6.15 (Build 8904): Release Notes 

Wed June 06, 2018 02:36 AM

Release date: June 6, 2018

 

TIP  See also previous DataLink release notes. To see details for all recent Apptio product releases, refer to "Latest Release Notes & What's New" on the Product Central home page.

 

This release adds TLS 1.2 enforcement for FedRAMP, and broadens API support in the Apptio Download connector. This release also addresses issues with agent restarts, excessive retries, timezone support, DigiCert certificates, an XML parser vulnerability, and a DataDrop archive issue introduced in 4.6.13.

 

New Features

  • DL-5497 - Add support for requiring TLS 1.2 for FedRAMP
  • DL-4918 - Download connector: support URL containing componentId
  • DL-4953 - Download connector: support all export formats (see matrix for formats supported)
R12R11
File ExtensionDataPathReportPathDataPath
.xlsxYesYes--
.xlsYesYesYes
.txtYesYesYes
.jsonYesYes--
.xml--Yes--
.zipYesYesYes
.tsvYesYesYes

 

Compatibility

  • Upgrade DataLink manager and DataLink engine to this version in order to receive all the features and improvements. There is no need to upgrade the DataLink agent.
  • You can also upgrade the DataLink engine only.

 

Bug Fixes

  • DL-5428 - Ensure status is correct after restarting agent while connectors are running and/or in waiting-to-run state
  • DL-3995 - Avoid account lockout when testing connectors by eliminating retry when credentials are bad
  • DL-5803 - Increase security of XML parser to prevent XML External Entity vulnerability
  • DL-5759 - Use timezone in connector schedule to convert month/year to retrieve source data 
  • DL-5857 - Add DigiCert CA certificate to DataLink Manager keystore
  • DL-5850 - Network File Connector: Fix "failed to archive data file" when using DataDrop (VFS issue introduced in 4.6.13)

 

Product Availability

To schedule your upgrade to the latest version, submit a support ticket  or email Apptio Support. 

 

TIP To learn more, visit the Data for TBM Knowledge Base.




#Datalink

Statistics
0 Favorited
2 Views
0 Files
0 Shares
0 Downloads

Comments

Ken Haniu
Thu July 05, 2018 03:48 PM

John, I believe the only change has been the inclusion of timezone offset when determining current/previous period. With that in place, I believe the 2-connector approach described in this document provides a way to ensure that all data ends up in the right Apptio time periods, accommodates time zone offsets, and is resilient to any delays in availability of the AWS data. This approach makes the system to do a lot of extra work, but it's the best option at this point given the frequency we need to run and the way AWS incrementally adds to the bill. Let me know if there are any scenarios this does not cover correctly. 


#Datalink

Apptio Community Member
Tue July 03, 2018 12:08 AM

Ken,

 

Can I get an update on the months, as it is still confusing and seems to change the last couple of months, also as dbr and all other connectors use different logic I need to know both versions.

 

Thanks,

 

John Feore


#Datalink

Ken Haniu
Thu June 07, 2018 06:46 PM

Here's part of the answer:

  • Previous behavior: scheduled run time of connector respected time zone, but the determination of current/previous period for target Apptio time period was not taking time zone into account. On the edge days of a month, this might result in data being uploaded to the wrong month.
  • New behavior: timezone is taken into account when determining target time period for current/previous month in Apptio

 

John, I am getting involved in your support ticket regarding DBR in particular so we'll get your remaining questions answered through that route.


#Datalink

Apptio Community Member
Wed June 06, 2018 05:53 PM

Hi,

 

Can someone please explain the new logic contained in 

  • DL-5759 - Use timezone in connector schedule to convert month/year to retrieve source data 

 

and also confirm that this is consistent across all DL connectors (as previously dbr and all other connector types used different logic). This is is also issue when scheduling and requires multiple connectors to allow for the timezone differences.... eg Cloud data for AWS & Azure for the final day of the previous month is not available until approx 6am on 1st day of new month, which is plus 17-19 hours for Australia meaning we are still running previous month Cloud data on the second day of the new month. Note, I also have to refresh most data after day 5 of new month when Cloud providers update billing files with final adjustments / invoice numbers / aligns with bill / general cleanup as data changes from estimate to final, but this is different timing issue.

 

Can you please explain and also how would schedule without having multiple connectors / manual scheduling.

 

Thanks,

 

John Feore


#Datalink