<?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 AWS output/aggregator with unexpected missing indicators in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/aws-output-aggregator-with-unexpected-missing-indicators/m-p/156393#M98963</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a dev and prod instance of MM. &amp;nbsp;Noticed both dev and prod behaving the same way, where many indicators were not showing up in output feed for AWS miners. &amp;nbsp;Config on both is the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;nodes:
  aws_route53_miner:
    inputs: []
    output: true
    prototype: aws.ROUTE53
  aws_ipv4_output:
    inputs:
      - aws_ipv4_aggregator
    output: false
    prototype: stdlib.feedHCWithValue
  aws_s3_miner:
    inputs: []
    output: true
    prototype: minemeldlocal.aws_S3
  aws_ec2_miner:
    inputs: []
    output: true
    prototype: aws.EC2
  aws_amazon_miner:
    inputs: []
    output: true
    prototype: aws.AMAZON
  aws_ipv4_aggregator:
    inputs:
      - aws_cloudfront_miner
      - aws_ec2_miner
      - aws_route53_miner
      - aws_route53_healthchecks_miner
      - aws_amazon_miner
      - aws_s3_miner
    output: true
    prototype: stdlib.aggregatorIPv4Generic
  aws_cloudfront_miner:
    inputs: []
    output: true
    prototype: aws.CLOUDFRONT
  aws_route53_healthchecks_miner:
    inputs: []
    output: true
    prototype: aws.ROUTE53_HEALTHCHECKS
&lt;/PRE&gt;
&lt;P&gt;Dev/Prod both showed the same # of indicators on Nodes tab:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aws_amazon_miner 511&lt;/P&gt;
&lt;P&gt;aws_cloudfront_miner 35&lt;/P&gt;
&lt;P&gt;aws_ec2_miner 222&lt;/P&gt;
&lt;P&gt;aws_route53_healthchecks_miner 16&lt;/P&gt;
&lt;P&gt;aws_route53_miner 2&lt;/P&gt;
&lt;P&gt;aws_s3_miner 62&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aws_ipv4_aggregator 323&lt;/P&gt;
&lt;P&gt;aws_ipv4_output 346&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I made a change in dev to take the aws_amazon_miner with 511 indicators straight to an output.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;nodes:
  aws_test_full_output:
    inputs:
      - aws_amazon_miner
    output: false
    prototype: stdlib.feedHCWithValue
&lt;/PRE&gt;
&lt;P&gt;The result is that the issue is not seen on this output, but the original aggregator and output nodes also&amp;nbsp;had the issue go away for the time being:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aws_ipv4_aggregator 848&lt;/P&gt;
&lt;P&gt;aws_ipv4_output 577&lt;/P&gt;
&lt;P&gt;aws_test_full_output 511&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Was planning to go production with this AWS output next week. &amp;nbsp;Need to vet out this issue asap.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Attaching engine logs from both instances as well as copys of output feeds in multiple versions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;prod &amp;nbsp;0.9.36&lt;/P&gt;
&lt;P&gt;dev 0.9.38&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 May 2017 15:17:14 GMT</pubDate>
    <dc:creator>andrew.stanton</dc:creator>
    <dc:date>2017-05-15T15:17:14Z</dc:date>
    <item>
      <title>AWS output/aggregator with unexpected missing indicators</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aws-output-aggregator-with-unexpected-missing-indicators/m-p/156393#M98963</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a dev and prod instance of MM. &amp;nbsp;Noticed both dev and prod behaving the same way, where many indicators were not showing up in output feed for AWS miners. &amp;nbsp;Config on both is the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;nodes:
  aws_route53_miner:
    inputs: []
    output: true
    prototype: aws.ROUTE53
  aws_ipv4_output:
    inputs:
      - aws_ipv4_aggregator
    output: false
    prototype: stdlib.feedHCWithValue
  aws_s3_miner:
    inputs: []
    output: true
    prototype: minemeldlocal.aws_S3
  aws_ec2_miner:
    inputs: []
    output: true
    prototype: aws.EC2
  aws_amazon_miner:
    inputs: []
    output: true
    prototype: aws.AMAZON
  aws_ipv4_aggregator:
    inputs:
      - aws_cloudfront_miner
      - aws_ec2_miner
      - aws_route53_miner
      - aws_route53_healthchecks_miner
      - aws_amazon_miner
      - aws_s3_miner
    output: true
    prototype: stdlib.aggregatorIPv4Generic
  aws_cloudfront_miner:
    inputs: []
    output: true
    prototype: aws.CLOUDFRONT
  aws_route53_healthchecks_miner:
    inputs: []
    output: true
    prototype: aws.ROUTE53_HEALTHCHECKS
&lt;/PRE&gt;
&lt;P&gt;Dev/Prod both showed the same # of indicators on Nodes tab:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aws_amazon_miner 511&lt;/P&gt;
&lt;P&gt;aws_cloudfront_miner 35&lt;/P&gt;
&lt;P&gt;aws_ec2_miner 222&lt;/P&gt;
&lt;P&gt;aws_route53_healthchecks_miner 16&lt;/P&gt;
&lt;P&gt;aws_route53_miner 2&lt;/P&gt;
&lt;P&gt;aws_s3_miner 62&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aws_ipv4_aggregator 323&lt;/P&gt;
&lt;P&gt;aws_ipv4_output 346&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I made a change in dev to take the aws_amazon_miner with 511 indicators straight to an output.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;nodes:
  aws_test_full_output:
    inputs:
      - aws_amazon_miner
    output: false
    prototype: stdlib.feedHCWithValue
&lt;/PRE&gt;
&lt;P&gt;The result is that the issue is not seen on this output, but the original aggregator and output nodes also&amp;nbsp;had the issue go away for the time being:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aws_ipv4_aggregator 848&lt;/P&gt;
&lt;P&gt;aws_ipv4_output 577&lt;/P&gt;
&lt;P&gt;aws_test_full_output 511&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Was planning to go production with this AWS output next week. &amp;nbsp;Need to vet out this issue asap.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Attaching engine logs from both instances as well as copys of output feeds in multiple versions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;prod &amp;nbsp;0.9.36&lt;/P&gt;
&lt;P&gt;dev 0.9.38&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 May 2017 15:17:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aws-output-aggregator-with-unexpected-missing-indicators/m-p/156393#M98963</guid>
      <dc:creator>andrew.stanton</dc:creator>
      <dc:date>2017-05-15T15:17:14Z</dc:date>
    </item>
    <item>
      <title>Re: AWS output/aggregator with unexpected missing indicators</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/aws-output-aggregator-with-unexpected-missing-indicators/m-p/156618#M98964</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/33044"&gt;@andrew.stanton&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;thanks, this is a bug and will be fixed in the next release. Details here:&amp;nbsp;&lt;A href="https://github.com/PaloAltoNetworks/minemeld-core/issues/213" target="_blank"&gt;https://github.com/PaloAltoNetworks/minemeld-core/issues/213&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A workaround is forcing a flush and an update on the existing miner you just added to the aggregator:&lt;/P&gt;
&lt;PRE&gt;$ /opt/minemeld/engine/current/bin/mm-console signal flush aws_amazon_miner
$ /opt/minemeld/engine/current/bin/mm-console hup aws_amazon_miner&lt;/PRE&gt;</description>
      <pubDate>Mon, 15 May 2017 09:03:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/aws-output-aggregator-with-unexpected-missing-indicators/m-p/156618#M98964</guid>
      <dc:creator>lmori</dc:creator>
      <dc:date>2017-05-15T09:03:10Z</dc:date>
    </item>
  </channel>
</rss>

