All Apps and Add-ons

After upgrading the Splunk Add-on for Amazon Web Services from 4.0.0 to 4.1.1, why did inputs stop collecting data and accounts are missing?

yannK
Splunk Employee
Splunk Employee

While using the Splunk Add-on for Amazon Web Services and the Splunk App for AWS, I got in a situation where all my inputs stopped after upgrading the add-on from 4.0.0 to 4.1.1

The symptoms were:

  • no data collection
  • many accounts missing or not found on the internal AWS logs.
  • warning icon on the accounts page on the add-on on the region column "Not set, please edit this account"

List item

Also, when editing an account from the APP (not the add-on ), the accounts were removed when we saved them.

The workaround was to:

  • edit the accounts one by one from the add-on
  • add the region
  • save, and check the warning

Recommendation: use the Add-on inputs manager rather than the app one.

1 Solution

yannK
Splunk Employee
Splunk Employee

The workaround was to

  • edit the accounts one by one from the add-on
  • add the region
  • save, and check the warning

View solution in original post

yannK
Splunk Employee
Splunk Employee

The workaround was to

  • edit the accounts one by one from the add-on
  • add the region
  • save, and check the warning
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...