Managed Flink: Add further notes on Logs integration (#1644)

Author: viren-nadkarni

content/en/user-guide/aws/kinesisanalyticsv2/index.md

@@ -183,6 +183,10 @@ $ awslocal kinesisanalyticsv2 add-application-cloud-watch-logging-option \
 }
 {{< /command >}}
 
+{{< callout >}}
+Enabling CloudWatch Logs integration has a significant performance hit.
+{{< /callout >}}
+
 Configured logging options can be retrieved using [DescribeApplication](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_DescribeApplication.html):
 
 {{< command >}}
@@ -206,6 +210,10 @@ $ awslocal logs get-log-events --log-group-name msaf-log-group --log-stream-name
 Logs events are reported to CloudWatch every 10 seconds.
 {{< /callout >}}
 
+LocalStack reports both Flink application and Flink framework logs to CloudWatch.
+However, certain extended information such as stack traces may be missing.
+You may obtain this information by execing into the Flink Docker container created by LocalStack and inspecting `/opt/flink/log`.
+
 ## Resource Tagging
 
 You can manage [resource tags](https://docs.aws.amazon.com/managed-flink/latest/java/how-tagging.html) using [TagResource](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_TagResource.html), [UntagResource](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_UntagResource.html) and [ListTagsForResource](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_ListTagsForResource.html).