Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Now try the following experiments:

  1. Assuming the actual Validity Interval is in fact 14 days, set maxValidityInterval to something less and watch the process fail: an error message will be logged and the metadata will be removed from the pipeline.

  2. Again assuming Assuming the actual Validity Interval is 14 days, set maxValidityInterval to something more and watch the process fail: a warning message will be logged.

  3. Assuming the actual Validity Interval is 14 days, set the subintervals to overlapping values (say, -E P3D -F P12D) and watch the process fail: a warning message will be logged.

  4. Set the freshnessInterval to some ridiculously small value (like PT60Ssay, -F PT60S) and watch the process fail: a warning message will be logged.

  5. Set the expirationWarningInterval to some ridiculously large value (relative to the actual Validity Intervalsay, -E P13D -F PT60S) and watch the process fail: a warning message will be logged.

Once When you've confirmed that the early warning system is behaving as expected, continue with the following configuration steps.

...