Incorrect After a user logs in to your organization, a SessionLog event is created. See also when.Ĭorrect After you install the update, save your changes. See add-on in the Splexicon.Ĭorrect add-on Add-on the add-on the Splunk Add-on for Incorrect add-On Add-On addon AddOn after Use to denote a chronological sequence of events that doesn't rely on cause and effect. Use the term "add-on" when you are writing about a technical add-on (TA), supported add-on (SA), or domain add-on (DA) in Splunk docs. The term takes a definite article, and you can write it as "the add-on" after the first instance of the full name of the add-on. In references not about an unscheduled search, use "if needed". Don't use any other term for a search that a user launches manually. ad hoc Use only when referring to an unscheduled search, otherwise don't use Latin abbreviations or terms. Use "earlier" or "previous" to refer to page elements. Use "higher" to refer to versions of software. Directional or visual instructions are unhelpful to visually impaired users. above Don't use to refer to a location in a document. Otherwise, use "force quit", "cancel", "fail", "close", "stop", "end", or another term that accurately reflects the situation. abort Don't use unless referring to a specific command or system language. If only one system is supported, use "UNIX" or "Linux". * *nix Use to refer to both UNIX and Linux together. The following list outlines terms to use and avoid in Splunk documentation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |