I see I have to set the liveReload plugin eanbled to false, but not sure where to set it. Is there a plugin config section somewhere in docpad.coffee
In the root folder of your docpad project edit the docpad.coffee file (or docpad.js)
docpadConfig:
...
# enabled example for live configuration
plugins:
livereload:
enabled: true
# enabled example for different environments
environments:
development: # change the name here if you have other environments
plugins:
livereload:
enabled: true
staging: # change the name here if you have other environments
plugins:
livereload:
enabled: true
...
more information about the configuration file is here - http://docpad.org/docs/config
Related
I've created a docker-compose file with some configurations that deploy Elasticsearch, Kibana, Elastic Agent all version 8.7.0.
where in the Kibana configuration files I define the police I needed under xpack.fleet.agentPolicies, with single command all my environment goes up and all component connect successfully.
The only issue is there is one manual step, which is I had to go to Kibana -> Observability -> APM -> Add Elastic APM and then fill the Server configuration.
I want to automate this and manage this from the API/CMD/configuration file, I don't want to do it from the UI.
What is the way to do this? in which component? what is the path the configuration should be at?
I tried to look for APIs or command to do that, but with no luck. I'm expecting help with automating the remaning step.
#Update 1
I've tried to add it as below, but I still can't see the integration added.
package_policies:
- name: fleet_server-apm
id: default-fleet-server
package:
name: fleet_server
inputs:
- type: apm
enabled: true
vars:
- name: host
value: "0.0.0.0:8200"
- name: url
value: "http://0.0.0.0:8200"
- name: enable_rum
value: true
frozen: true
Tldr;
Yes, I believe there is a way to do it.
But I am pretty sure this is poorly documented.
You can find some idea in the repository of apm-server
Solution
In the kibana.yml file you can add some information related to fleet.
This section below is taken from the repository above and helped me set up apm automatically.
But if you have some specific settings you would like to see enable I am usure where you provide them.
xpack.fleet.packages:
- name: fleet_server
version: latest
xpack.fleet.agentPolicies:
- name: Fleet Server (APM)
id: fleet-server-apm
is_default_fleet_server: true
is_managed: false
namespace: default
package_policies:
- name: fleet_server-apm
id: default-fleet-server
package:
name: fleet_server
It is true that the kibana Fleet API is very poorly documented at this moment. I think your problem is that you are trying to add the variables to the fleet-server package insted of the apm package. Your yaml should look like this:
package_policies:
- name: fleet_server-apm
id: default-fleet-server
package:
name: fleet_server
- name: apm-1
package:
name: apm
inputs:
- type: apm
keep_enabled: true
vars:
- name: host
value: 0.0.0.0:8200
frozen: true
- name: url
value: "http://0.0.0.0:8200"
frozen: true
- name: enable_rum
value: true
frozen: true
Source
I have a serverless file with:
custom:
specificProp: true
I have another file with a property that should be shared by multiple serverless files:
custom:
commonProp: true
Is there any Serverless plugin or yaml feature that would allow me to merge the file with the common prop into the first file to produce:
custom:
specificProp: true
commonProp: true
I have an input settings like this (Proof Of Concept) and i will add more prospectors further on.
Can i avoid repetition of the multiline properties?
filebeat.prospectors:
- type: log
enabled: true
paths:
- /data/server/logs/inode-stage/inode-stage.log
multiline.pattern: '^\['
multiline.negate: true
multiline.match: after
fields:
env: 'stage'
app: 'inode'
- type: log
enabled: true
paths:
- /data/server/logs/inode-dev/inode-dev.log
multiline.pattern: '^\['
multiline.negate: true
multiline.match: after
fields:
env: 'dev'
app: 'inode'
I don't think that is possible right now. Not sure how many variations you will have in your inputs, but based on your current example I would extract the env with dissect. If you need something more powerful, you could even go for the script processor.
I am using elasic.co/filebeat:6.3.1 and ELK elastic.co:6.3.0 in ubuntu as docker, while running filebeat facing this issue,
https://i.stack.imgur.com/9rZjt.png
And my filebeat.yml is
filebeat.inputs:
# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.
- type: log
# Change to true to enable this input configuration.
enabled: false
# Paths that should be crawled and fetched. Glob based paths.
paths:
- /usr/local/java/ABC_LOGS/*/*.log
#- c:\programdata\elasticsearch\logs\*
#============================= Filebeat modules ===============================
filebeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
# Set to true to enable config reloading
reload.enabled: false
#==================== Elasticsearch template setting ==========================
setup.template.settings:
index.number_of_shards: 3
#index.codec: best_compression
#_source.enabled: false
#============================== Dashboards =====================================
setup.dashboards.enabled: true
#============================== Kibana =====================================
setup.kibana:
host: "10.0.0.0:5601"
#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
hosts: ["10.0.0.0:9200"]
Please help me,Thanks in advance
I am building a Sinatra API and I have some custom configurations which needs to be used by the API.
For eg :
master:
- role: 'production'
node_ip: '192.168.1.1'
notify: 'abc#gmail.com'
- role: 'production'
node_ip: '192.168.1.2'
notify: 'def#gmail.com'
development:
role: 'production'
node_ip: '192.168.1.2'
notify: 'def#gmail.com'
So I need use these configuation in my app. Right now I have put it in yml files and loading it and using it in my app. Is there any better way to do achieve the same without using yaml.