New Features for

Version 1.8.3 of was released on January 8th, 2024. It includes the following new features:

• Implementation of Unified Connector Framework 2.0 (UCF 2.0).
  
  
  • Implementation of UCF 2.0 improves the scalability and performance of the AWS S3 connector for AWS data sources.
  
  
• Azure Active Directory service was replaced with Microsoft Entra ID
  
  
  • The name of Azure Active Directory service was replaced with Microsoft Entra ID on October 1, 2023. This change caused the discrepancies with the DM onboarding instructions and might have been confusing for the users. Following the documentation, the service icon has changed. All the references to AAD, Azure AD, Azure Active Directory have been replaced with correct ones according to the rules (Microsoft Entra ID or Microsoft Entra depending on context). All the Azure input onboarding maps have been replaced using the correct service name. Additionally all the comments in the code and test cases names which referenced Azure Active Directory service have been corrected using the new service name.




• Changes to the AWS Inputs Health dashboard.
  
  
  • Fixed the display of CloudTrail index information and VPC Flow Logs
  • Added the ability to filter by time range, and by index.
  • Applied all old and new filters to all page content (all charts and table). Old filters were applied only for table. Changes are expected to add speed and flexibility.
  • With the addition of the time range filter, table columns were updated.
    The following columns were removed:
    • Last Seen Event (Last 7 Days)
    • Number of Events (Last 7 Days)
    • Last 7 Days Sparkline
    • Number of Events Ingested Today
    • Events Ingested Today Sparkline

    
    The following columns were added:
    

    • Last Seen Event
    • Number of Events
    • Sparkline
• Fixed issue: Successful prerequisites check for data accounts hides error message for control account.
  
  
  • This issue is related to the AWS multi account input. On the Edit input page, the prerequisites check for the control account and data accounts were working in parallel, and independent of each other. That caused a situation when the call with an error response came up first, and then when the successful one had been completed, it replaced the error notification with green successful notification. Other than that indicator, there were no error details in the UI when the error was related to the control account.
    To fix this issue:
    The notification comes up when both prerequisites checks are completed. If either the control account or data accounts causes the error, only one error notification appears. A UI update has been made, where, in the event of an error with the control account, an exclamation mark icon was added with tooltip containing error details.

The Amazon S3 data input for Data Manager is being gradually rolled out to Splunk Cloud Platform and may not be available immediately. If you have an urgent need for this capability and do not see it yet in your Splunk Cloud Platform environment, then please contact your Splunk Cloud Platform sales representative.

For users of any Azure Data Manager inputs, beginning on December 3, 2022, function apps running on versions 2.x and 3.x of the Azure Functions runtime can no longer be supported. Before that time, test, verify, and migrate your function apps to version 4.x of the Functions runtime. After the deadline, function apps can be created and deployed, and existing apps continue to run. However, your apps won't be eligible for new features, security patches, performance optimizations, and support until you upgrade them to version 4.x. End of support for these runtime versions is due to the ending of support for .NET Core 3.1, which is required by these older runtime versions. This requirement affects all Azure Functions runtime languages. For more information, see the ''Migrating from 3.x to 4.x'' topic in the Microsoft documentation.

Upgrade requirements

Splunk Data Manager is cloud native application and automatically updates to the latest version, ensuring users always have the most current features and security enhancements with minimal maintenance effort.

Migrate to Azure function runtime version 4.x

On December 3, 2022, Microsoft ended support for Azure function runtime versions 2.x and 3.x. Azure environments that contain function apps running on versions 2.x and 3.x of the Azure Functions runtime are no longer supported. Function apps can be created and deployed, and existing apps continue to run, but your apps won't be eligible for new features, security patches, performance optimizations, and support until you upgrade them to version 4.x.

End of support for these runtime versions is due to the ending of support for .NET Core 3.1, which is required by these older runtime versions. This requirement affects all Azure Functions runtime languages.

When migrating to version 4.x of the Azure functions runtime, users will experience a downtime of a couple of seconds as the migration requires that the existing Azure function be restarted. Therefore, the best practice is to perform this migration when you do not anticipate a lot of traffic.

Perform the following steps to migrate the function app from version 3.x to version 4.x.

1. Log into your Azure Portal and select the function specific deployment where you want to make the migration update.
2. Select the name of the resource that is the Function App type.
3. In the selected function app, navigate to Settings > Configuration on the sidebar menu.
4. In the Configuration page of the selected function app, navigate to the Function runtime settings tab.
5. On the Function runtime settings tab, navigate to the Runtime version field, and change the field value from ~3 to ~4. A prompt for a restart of the function app will appear.
6. Review and agree to the prompt to restart your function app. There will be a downtime of several seconds while the function app restarts.
7. To verify that the Azure function runtime version has been upgraded, navigate to your function app Overview page, and review the version listed in the Runtime version field.

For more information, see the following topics:

The Azure function app runtime prerequisites section of the Azure prerequisites for Data Manager topic in the Data Manager User Manual.

The Migrating from 3.x to 4.x topic in the Microsoft documentation.
The Azure Functions runtime versions overview topic in the Azure product documentation.

Compatibility

1.8.2 is compatible with Splunk Cloud versions version 8.2.2014 and higher.