<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Enriching logs with AWS entity information in Log Analytics</title>
    <link>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265722#M1138</link>
    <description>&lt;P&gt;Hi Mani,&lt;BR /&gt;&lt;BR /&gt;It is possible you can get the "entity id" from the AWS service and manually tag the logs using classic log processing rules or openpipeline.&amp;nbsp;&lt;BR /&gt;I have done something similar in the past for cloudwatch logs and it works well.&lt;BR /&gt;Best is to get details about the AWS service entity from the API and then reuse it to map the topology accordingly.&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/api-entities-v2-get-entity" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/api-entities-v2-get-entity&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Dec 2024 02:58:30 GMT</pubDate>
    <dc:creator>RohitBisht</dc:creator>
    <dc:date>2024-12-19T02:58:30Z</dc:date>
    <item>
      <title>Enriching logs with AWS entity information</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265712#M1137</link>
      <description>&lt;P&gt;we have 2 integrations in place&lt;/P&gt;
&lt;P&gt;1. AWS Cloudwatch integration, where we are pulling in cloudwatch metrics for various AWS Services&lt;/P&gt;
&lt;P&gt;2. Log integration. We are pulling in AWS Database Migration service logs from cloudwatch into Dynatrace&lt;/P&gt;
&lt;P&gt;When logs are coming in, they are not getting mapped to entities (AWS DMS Entities)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When looking through documentation for Dynatrace, entity linking is not available for DMS Services -&amp;nbsp;&lt;A href="https://docs.dynatrace.com/docs/shortlink/lma-stream-logs-with-firehose#view-aws-logs" target="_blank" rel="noopener"&gt;https://docs.dynatrace.com/docs/shortlink/lma-stream-logs-with-firehose#view-aws-logs&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are thinking if we can use OpenPipeline to achieve this ? Is it possible - any thoughts ?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 07:39:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265712#M1137</guid>
      <dc:creator>manisundaram</dc:creator>
      <dc:date>2024-12-19T07:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: Enriching logs with AWS entity information</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265722#M1138</link>
      <description>&lt;P&gt;Hi Mani,&lt;BR /&gt;&lt;BR /&gt;It is possible you can get the "entity id" from the AWS service and manually tag the logs using classic log processing rules or openpipeline.&amp;nbsp;&lt;BR /&gt;I have done something similar in the past for cloudwatch logs and it works well.&lt;BR /&gt;Best is to get details about the AWS service entity from the API and then reuse it to map the topology accordingly.&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/api-entities-v2-get-entity" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/api-entities-v2-get-entity&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 02:58:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265722#M1138</guid>
      <dc:creator>RohitBisht</dc:creator>
      <dc:date>2024-12-19T02:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: Enriching logs with AWS entity information</title>
      <link>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265734#M1139</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/34365"&gt;@manisundaram&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition to valuable inputs by&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/45903"&gt;@RohitBisht&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding the raised concern PFA resources for actual execution as per monitoring requirements:&lt;/P&gt;&lt;P&gt;AWS:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metrics" target="_blank"&gt;https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metrics&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/aws-metrics-ingest/cloudwatch-metric-streams" target="_blank"&gt;https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/aws-metrics-ingest/cloudwatch-metric-streams&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://video.dynatrace.com/watch/XBanorC1aSmHWhH5G6jCva" target="_blank"&gt;https://video.dynatrace.com/watch/XBanorC1aSmHWhH5G6jCva&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://www.youtube.com/watch?v=zX6CFj5EB94" target="_blank"&gt;https://www.youtube.com/watch?v=zX6CFj5EB94&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Entities&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/entity-v2" target="_blank"&gt;https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/entity-v2&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2024-12-19_10h19_13.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/25337iC0CE8705E9E9308F/image-size/large?v=v2&amp;amp;px=999" role="button" title="2024-12-19_10h19_13.png" alt="2024-12-19_10h19_13.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Logs&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-log-ingestion/lma-log-ingestion-via-api/lma-cloud-provider-log-forwarding#aws-log-forwarding" target="_blank"&gt;https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-log-ingestion/lma-log-ingestion-via-api/lma-cloud-provider-log-forwarding#aws-log-forwarding&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-use-cases" target="_blank"&gt;https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-use-cases&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Log processing with Open Pipeline:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-openpipeline" target="_blank"&gt;https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-openpipeline&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Regarding the accurate mapping:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;You can refer to the available topology relationships upon the successful integration.&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/discover-dynatrace/references/semantic-dictionary/model/dt-entities" target="_blank"&gt;https://docs.dynatrace.com/docs/discover-dynatrace/references/semantic-dictionary/model/dt-entities&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hoping it helps.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 06:27:06 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Log-Analytics/Enriching-logs-with-AWS-entity-information/m-p/265734#M1139</guid>
      <dc:creator>Peter_Youssef</dc:creator>
      <dc:date>2024-12-19T06:27:06Z</dc:date>
    </item>
  </channel>
</rss>

