insights-client.conf(5)

okay so bestie, welcome to insights-client.conf(5) — the literal glow-up guide for the Red Hat Insights client config ✨ this is the page you read when you wanna know what every knob in that file does, and ngl it's kind of iconic. let's get into it 💅

🌸 NAME 🌸

insights-client.conf — Red Hat Insights client configuration. that's it, that's the vibe 🎀

✨ DESCRIPTION ✨

so the insights-client.conf file is where all the configuration info lives for insights-client, which is — you guessed it — the client for the Red Hat Insights service 🫶

the file is in INI style format, meaning option=value, and the default or example values are all shown below 💖 it opens with this section header:

[insights-client]

and here's every single option, no skips, no cap 👑

• loglevel=DEBUG — changes the log level 🪵 valid options are DEBUG, INFO, WARNING, ERROR, CRITICAL. pick your fighter.
• auto_config=True — automatically attempts to configure connectivity to Red Hat Insights 🔌 and like, if an RHSM or Satellite subscription is detected, CERT auth gets automatically selected. it just knows ✨
• base_url=cert-api.access.redhat.com:443/r/insights — the base URL for API interactions 🌐 that's the address it's talking to, fr fr.
• proxy=http://user:pass@192.168.100.50:8080 — the URL for the proxy 🛡️ (yes, with user and pass right there in the example, mind your business).
• auto_update=True — automatically updates the dynamic configuration 🔄 it stays fresh, it stays current.
• obfuscation_list= — here you specify which data types should be obfuscated in the data collection 🙈 lowkey important if you're shy about certain data.
• display_name= — the display name for this system 🏷️ make it cute, make it yours.
• ansible_host= — the Ansible hostname for this system 🧚 basically its little name tag for Ansible.
• cmd_timeout=120 — the timeout for commands run during collection, measured in seconds ⏱️ so 120 seconds of patience, then it's over.
• http_timeout=120 — the timeout for HTTP calls, in seconds 🌐 same energy, same 120.
• core_collect=True — when True, use Insights Core to perform the data collection 🔥 heads up though: this option is provided for compatibility only and will be deprecated in a future release. so like, it's giving "still here but on notice" 💀
• redaction_file=/etc/insights-client/file-redaction.yaml — this file can be used to omit files or commands from the collection 🚫📄 for the deets on how to use it, see /usr/share/doc/insights-client/file-redaction.yaml.example or https://access.redhat.com/articles/4511681.
• content_redaction_file=/etc/insights-client/file-content-redaction.yaml — this file can be used to omit lines or keywords from files and commands in the collection ✂️🔍 and same deal, see /usr/share/doc/insights-client/file-content-redaction.yaml.example or https://access.redhat.com/articles/4511681 for how to actually use it.
• tags_file=/etc/insights-client/tags.yaml — the location of the tags file for this system 🏷️💖 it's where the tags live.

🦋 SEE ALSO 🦋

• insights-client(8) — go read that one next bestie, it's the whole other half of the story 👀

ngl this page is short but it ate. every option is a little main character in its own right 👑

mwah, that's the whole page 💜 this was insights-client.conf(5) from the Red Hat Insights Configuration crew — go forth and configure responsibly, bestie 🌈💅🫶