Skip to content
This repository was archived by the owner on Apr 16, 2021. It is now read-only.
This repository was archived by the owner on Apr 16, 2021. It is now read-only.

Elastic Stack Beta 2 #1132

@dougburks

Description

@dougburks
  • Elasticsearch

    • Elasticsearch 5.6.4
  • Kibana

    • Kibana 5.6.4
    • avoid scroll bars on metric visualizations by replacing standard metric visualizations with time series visual builder metric visualizations
    • on Stats dashboard, Logstash Error Type (Donut Chart) visualization is showing all tags not just errors
  • Logstash

  • so-crossclustercheck

    • avoid issues with hyphenated hostnames (like elastic-virtual-machine)
    • cron job should not run until after cross cluster settings are initially applied
    • cron job should run as a limited user
    • add logrotate entry for /var/log/elasticsearch/crossclustercheck.log
    • enable/disable via /etc/nsm/securityonion.conf
  • so-elastic-start

    • break into separate scripts (so-elastic-start calls so-elastic-start-elasticsearch...)
  • /etc/init/securityonion.conf

    • check for /etc/init.d/xplico before trying to execute it
  • CapMe

    • check for IPv6 addresses
    • detect BRO_PE / BRO_X509 and pivot to BRO_FILES via FID and then to BRO_CONN via CID
    • increase $st and $et window and check for multiple results
  • sosetup-elastic

    • if configuring master-only, syslog-ng.conf never gets updated, thus logs never make it to Elastic (resolved in securityonion-elastic - 20171020-1ubuntu1securityonion13)
    • always disable Xplico
    • when re-running setup, make sure that /etc/nsm/crossclustertab gets removed
    • disable FreqServer and DomainStats when running Production Mode
  • so-status

    • elasticsearch and logstash output should be moved inside if statement in case they are disabled
    • move elastic logic to so-elastic-status and have so-status just call service nsm status and then so-elastic-status
  • securityonion-elastic package

    • postinst should run so-elastic-configure if Elastic is enabled and should include error checking

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions