ELASTALERT-CREATE-INDEX(1)
π NAME π
elastalert-create-index β bestie, this is the little tool that sets up your Elasticsearch index for ElastAlert, and I'm gonna walk you through every single flag, no gatekeeping π
πΈ DESCRIPTION πΈ
okay so here's the vibe. You run this thing and it makes your index. That's it. That's the whole job. But there are so many knobs to turn, and we're gonna turn all of them together π«Ά
The way you call it looks like this:
usage: elastalert-create-index [-h] [--host HOST] [--port PORT]
[--username USERNAME] [--password PASSWORD]
[--url-prefix URL_PREFIX] [--no-auth] [--ssl] [--no-ssl]
[--verify-certs] [--no-verify-certs] [--index INDEX] [--alias
ALIAS] [--old-index OLD_INDEX] [--send_get_body_as
SEND_GET_BODY_AS] [--boto-profile PROFILE] [--profile PROFILE]
[--aws-region AWS_REGION] [--timeout TIMEOUT] [--config CONFIG]
[--recreate RECREATE]
β¨ options: β¨
-h,--helpβ shows this help message and then dips. iconic behavior honestly π--host HOSTβ the Elasticsearch host. where your cluster lives, fr fr π--port PORTβ the Elasticsearch port. the lil door number π--username USERNAMEβ Elasticsearch username. who you're claiming to be π--password PASSWORDβ Elasticsearch password. the secret. do NOT put this in the group chat π--url-prefix URL_PREFIXβ Elasticsearch URL prefix. that lil something-something tacked onto the front of the URL π--no-authβ suppresses the prompt for basic auth. no asking, just going β¨--sslβ use TLS. secure the connection, we love a locked-down queen π--no-sslβ do not use TLS. no encryption, raw dogging the wire (respectfully) π--verify-certsβ verify TLS certificates. check those IDs at the door π--no-verify-certsβ do not verify TLS certificates. skipping the ID check, lowkey risky but okay π«£--index INDEXβ the index name to create. name your baby πΌ--alias ALIASβ the alias name to create. a cute nickname that points at the real one π¦--old-index OLD_INDEXβ the old index name to copy. moving the whole closet over, one hanger at a time π--send_get_body_as SEND_GET_BODY_ASβ the method for querying Elasticsearch βPOST,GETorsourceπ--boto-profile PROFILEβ DEPRECATED, bestie, use--profileinstead. it's the Boto profile to use for signing requests. still works, but it's giving old news π°--profile PROFILEβ the AWS profile to use for signing requests. optionally you can use theAWS_DEFAULT_PROFILEenvironment variable instead π--aws-region AWS_REGIONβ the AWS Region to use for signing requests. optionally you can use theAWS_DEFAULT_REGIONenvironment variable instead π--timeout TIMEOUTβ Elasticsearch request timeout. how long we're willing to wait before we're like... okay bestie, we're done here β°--config CONFIGβ the global config file (default:config.yaml). your settings home base π‘--recreate RECREATEβ force re-creation of the index. β οΈ This will cause data loss. Like, actual, permanent, gone-forever data loss. Not a drill, not a vibe, not a cute little oops. Be SO sure before you do this one π
heads up bestie: --recreate is the scary one. Everything else is just configuration, but that flag will eat your data and not apologize π
and that's the whole page, you're basically a certified elastalert-create-index girlie now, go off π
this was elastalert-create-index version 0.2.4-3, from December 2022 β mwah, sending you love and successful index creation ππ
π¦ where this page comes from
- debian bookworm: elastalert 0.2.4-3 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms