Logstash Email Config


(Nikhil Singh) #21

getting response for the first url


(Lewis Barclay) #22

Post full config


(Nikhil Singh) #23

################### Heartbeat Configuration Example #########################

This file is an example configuration file highlighting only some common options.

The heartbeat.reference.yml file in the same directory contains all the supported options

with detailed comments. You can use it for reference.

You can find the full configuration reference here:

https://www.elastic.co/guide/en/beats/heartbeat/index.html

############################# Heartbeat ######################################

Configure monitors

heartbeat.monitors:

setup.template.settings:
index.number_of_shards: 1
index.codec: best_compression
setup.template.overwrite: true
#_source.enabled: false

#================================ General =====================================

The name of the shipper that publishes the network data. It can be used to group

all the transactions sent by a single shipper in the web interface.

#name:

The tags of the shipper are included in their own field with each

transaction published.

#tags: ["service-X", "web-tier"]

Optional fields that you can specify to add additional information to the

output.

#fields:

env: staging

#============================== Dashboards =====================================

These settings control loading the sample dashboards to the Kibana index. Loading

the dashboards is disabled by default and can be enabled either by setting the

options here, or by using the -setup CLI flag or the setup command.

#setup.dashboards.enabled: false

The URL from where to download the dashboards archive. By default this URL

has a value which is computed based on the Beat name and version. For released

versions, this URL points to the dashboard archive on the artifacts.elastic.co

website.

#setup.dashboards.url:

#============================== Kibana =====================================

Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.

This requires a Kibana endpoint configuration.

setup.kibana:

Kibana Host

Scheme and port can be left out and will be set to the default (http and 5601)

In case you specify and additional path, the scheme is required: http://localhost:5601/path

IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

host: "10.20.12.59:5601"

Kibana Space ID

ID of the Kibana Space into which the dashboards should be loaded. By default,

the Default Space will be used.

#space.id:

#============================= Elastic Cloud ==================================

These settings simplify using heartbeat with the Elastic Cloud (https://cloud.elastic.co/).

The cloud.id setting overwrites the output.elasticsearch.hosts and

setup.kibana.host options.

You can find the cloud.id in the Elastic Cloud web UI.

#cloud.id:

The cloud.auth setting overwrites the output.elasticsearch.username and

output.elasticsearch.password settings. The format is <user>:<pass>.

#cloud.auth:

#================================ Outputs =====================================

Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:

Array of hosts to connect to.

hosts: ["10.20.12.59:9200"]

Optional protocol and basic auth credentials.

#protocol: "https"
#username: "elastic"
#password: "changeme"

#----------------------------- Logstash output --------------------------------
#output.logstash:

The Logstash hosts

#hosts: ["localhost:5044"]

Optional SSL. By default is off.

List of root certificates for HTTPS server verifications

#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

#================================ Procesors =====================================

Configure processors to enhance or manipulate events generated by the beat.

processors:

  • add_host_metadata: ~
  • add_cloud_metadata: ~

#================================ Logging =====================================

Sets log level. The default log level is info.

Available log levels are: error, warning, info, debug

#logging.level: debug

At debug level, you can selectively enable logging only for some components.

To enable all selectors use ["*"]. Examples of other selectors are "beat",

"publish", "service".

#logging.selectors: ["*"]

#============================== Xpack Monitoring ===============================

heartbeat can export internal metrics to a central Elasticsearch monitoring

cluster. This requires xpack monitoring to be enabled in Elasticsearch. The

reporting is disabled by default.

Set to true to enable the monitoring reporter.

#xpack.monitoring.enabled: false

Uncomment to send the metrics to Elasticsearch. Most settings from the

Elasticsearch output are accepted here as well. Any setting that is not set is

automatically inherited from the Elasticsearch output configuration, so if you

have the Elasticsearch output configured, you can simply uncomment the

following line.

#xpack.monitoring.elasticsearch:


(Lewis Barclay) #24

heartbeat logs?


(Nikhil Singh) #25

2018-12-03T14:47:00.644+0530 INFO instance/beat.go:592 Home path: [C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64] Config path: [C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64] Data path: [C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64\data] Logs path: [C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64\logs]
2018-12-03T14:47:00.663+0530 INFO instance/beat.go:599 Beat UUID: c9bd2180-f6ea-4cc3-942b-6941945ca07e
2018-12-03T14:47:00.663+0530 INFO [beat] instance/beat.go:825 Beat info {"system_info": {"beat": {"path": {"config": "C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64", "data": "C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64\data", "home": "C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64", "logs": "C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64\logs"}, "type": "heartbeat", "uuid": "c9bd2180-f6ea-4cc3-942b-6941945ca07e"}}}
2018-12-03T14:47:00.663+0530 INFO [beat] instance/beat.go:834 Build info {"system_info": {"build": {"commit": "b1c6ac83cc037bd75395334eed23b64bd63c87ef", "libbeat": "6.5.1", "time": "2018-11-16T01:31:45.000Z", "version": "6.5.1"}}}
2018-12-03T14:47:00.663+0530 INFO [beat] instance/beat.go:837 Go runtime info {"system_info": {"go": {"os":"windows","arch":"amd64","max_procs":2,"version":"go1.10.3"}}}
2018-12-03T14:47:00.674+0530 INFO [beat] instance/beat.go:841 Host info {"system_info": {"host": {"architecture":"x86_64","boot_time":"2018-11-22T10:05:50.19+05:30","name":"MUM-CALDEV03","ip":["10.20.3.126/25","::1/128","127.0.0.1/8"],"kernel_version":"6.3.9600.19179 (winblue_ltsb_escrow.181015-1847)","mac":["00:50:56:a6:53:e6","00:00:00:00:00:00:00:e0"],"os":{"family":"windows","platform":"windows","name":"Windows Server 2012 R2 Datacenter","version":"6.3","major":3,"minor":0,"patch":0,"build":"9600.19182"},"timezone":"IST","timezone_offset_sec":19800,"id":"b3e0acdf-91ea-4575-8299-9273c1bd9bc4"}}}
2018-12-03T14:47:00.677+0530 INFO [beat] instance/beat.go:870 Process info {"system_info": {"process": {"cwd": "C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64", "exe": "C:\Users\Calypso\Downloads\heartbeat\heartbeat-6.5.1-windows-x86_64\heartbeat.exe", "name": "heartbeat.exe", "pid": 7760, "ppid": 6536, "start_time": "2018-12-03T14:47:00.511+0530"}}}
2018-12-03T14:47:00.677+0530 INFO instance/beat.go:278 Setup Beat: heartbeat; Version: 6.5.1
2018-12-03T14:47:03.700+0530 INFO add_cloud_metadata/add_cloud_metadata.go:319 add_cloud_metadata: hosting provider type not detected.
2018-12-03T14:47:03.700+0530 INFO elasticsearch/client.go:163 Elasticsearch url: http://10.20.12.59:9200
2018-12-03T14:47:03.700+0530 INFO [publisher] pipeline/module.go:110 Beat name: MUM-CALDEV03
2018-12-03T14:47:03.702+0530 INFO elasticsearch/client.go:163 Elasticsearch url: http://10.20.12.59:9200
2018-12-03T14:47:03.708+0530 INFO elasticsearch/client.go:712 Connected to Elasticsearch version 6.4.2
2018-12-03T14:47:03.708+0530 INFO kibana/client.go:118 Kibana url: http://10.20.12.59:5601
2018-12-03T14:47:05.727+0530 INFO instance/beat.go:717 Kibana dashboards successfully loaded.


(Lewis Barclay) #26

It is working fine


(Nikhil Singh) #27

But I'm not seeing any response for the 2nd url specified in the yml in kibana


(Lewis Barclay) #28

I would suggest you check your URL is correct


(Nikhil Singh) #29

I have a question that if I edit my yml file do we need to restart or run the installation commands again to reflect the changes?


(Lewis Barclay) #30

No you just restart the service


(Nikhil Singh) #31

could you provide me with the command to do so?


(Lewis Barclay) #32

In windows just open services.msc, find heartbeat service and press restart?


(Nikhil Singh) #33

Thanks Lewis it worked.
So now if we have two different urls and we need to create different visualization of it in Kibana how do we do it.
Also there is just http.url field which is different


(system) #34

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.