Disable:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Enable:
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Disable:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Enable:
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
object | doc | description | url |
---|---|---|---|
APM routes | doc | Reset secret tokens for your APM resources. | POST /api/v1/deployments/{deployment_id}/apm/{ref_id}/_reset-token |
Accounts | doc | Retrieve and update the current Elasticsearch Service account. | GET /api/v1/account PATCH /api/v1/account PUT /api/v1/account |
App Search (Read only) | doc | Enable read only mode on an App Search resource. | GET /api/v1/deployments/{deployment_id}/appsearch/{ref_id}/read_only_mode PUT /api/v1/deployments/{deployment_id}/appsearch/{ref_id}/read_only_mode |
Authentication | doc | Mana |
With ...
> SELECT id, color, name FROM shirts LIMIT 5
id color name
1 blue Jane
2 yellow Susan
3 green Craig
4 yellow Susan
5 blue Susan
ILM phases+actions proceed sequentially. This implies if ILM gets stuck on a preceeding step it will never finish its sequence. A tabular format of the linked doc
actions\phase | hot | warm | cold | frozen | delete |
---|---|---|---|---|---|
set-priority | TRUE | TRUE | TRUE | f | f |
unfollow | TRUE | TRUE | TRUE | TRUE | f |
rollover | TRUE | f | f | f | f |
read-only | TRUE | TRUE | TRUE | f | f |
# docker-compose -f elastic_docker_singleNode_withSecurity.yaml -p "secure_elastic" up | |
version: '3' | |
services: | |
elasticsearch: | |
container_name: elasticsearch | |
image: docker.elastic.co/elasticsearch/elasticsearch:7.17.7 | |
environment: | |
- bootstrap.memory_lock=true | |
- discovery.seed_hosts=elasticsearch | |
- discovery.type=single-node |
# Runtime: https://www.elastic.co/guide/en/elasticsearch/reference/8.5/runtime-mapping-fields.html | |
DELETE test_index | |
PUT test_index | |
{ "mappings": { "properties": { "myKey": { "type": "text" }}}} | |
General rule access
doc If you want to use the alerting features in a Kibana app, you must have the appropriate feature privileges. For example, to create rules in Stack Management > Rules and Connectors, you must have
all
privileges for the Management > Stack Rules feature. To attach actions to the rule, you must also haveread
privileges for the Actions and Connectors feature. For more information on configuring roles that provide access to features, go to Feature privileges.
Specific rule type (via feature)
doc You must have
all
privileges for the appropriate Kibana features, depending on theconsumer
andrule_type_id
of the rules you’re creating. For example, the Management > **Stac
import datetime | |
import math | |
import matplotlib.pyplot as plt # https://matplotlib.org | |
import mplcursors # https://mplcursors.readthedocs.io | |
import numpy as np # https://numpy.org/ | |
import os | |
import sys | |
### usage notes | |
# Method to pull file statitics may depend on OS. |
Checking the Node Stats *.cpu
outputs compared to container/system CPU info.
http://localhost:9200/_nodes/stats?filter_path=nodes.*.os.cpu,nodes.*.os.cgroup.cpu,nodes.*.process.cpu.percent
This data backs JSON for CAT Nodes which uses os.cpu
per code.
Using Docker to run a local, basic Elasticsearch with Kibana setup: