[prometheus-users] Re: passwords in config file

[Natacha Souza]

Aaah, that is lovely. Thank you so much for pointing me in the right 
direction.

On Sunday, December 18, 2022 at 4:35:02 PM UTC-3 Brian Candler wrote:

> It's pretty simple. You point password_file at a file containing the 
> password; and you use Unix permissions to ensure that this file is readable 
> only by the prometheus process (i.e. the userid that prometheus runs as).
>
> If you are using Kubernetes, it has the ability to expose "secrets" at a 
> specific path in the filesystem, so you could point to one of those.
>
> Certainly, if someone breaks into the system as 'root' or the prometheus 
> user, they'll be able to read the secret. But that's pretty much a 
> requirement, since the prometheus process itself needs to know the secret.
>
> On Sunday, 18 December 2022 at 13:56:12 UTC natach...@gmail.com wrote:
>
>> Hi Brian,
>>
>> Yes, that's what I meant. But I also have some concerns about 
>> password_file, can you recommend some strategies I can study to use it 
>> securely? 
>> I've been trying to find it online for a few days before asking here, but 
>> without success.
>>
>> On Saturday, December 17, 2022 at 6:53:03 AM UTC-3 Brian Candler wrote:
>>
>>> If you're talking about basic_auth in scrape jobs 
>>> ,
>>>  
>>> then use password_file instead of password.
>>>
>>> Otherwise, please clarify, or give an example of the embedded 
>>> username+password config you're talking about.
>>>
>>> On Saturday, 17 December 2022 at 08:49:30 UTC natach...@gmail.com wrote:
>>>
 Hey guys,

 I'm looking for some best practices advice for securing my prometheus 
 stack, because I don't wanna have username+password for my targets in my 
 prometheus.yml file

 I've looked for environment variables because this is one way that I 
 know of, and that turned out to be a huge discussion and a dead end. 

 So what is you recommendation? What should I study/do ?

 Regards,
 Nat

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/05bb96c9-2eef-4855-bc31-9736d1e48f2an%40googlegroups.com.

Re: [prometheus-users] Prometheus-Thanos-Grafana Integration || error || open /etc/prometheus-shared/prometheus.yaml: no such file or directory

[Stuart Clark]

On 05/01/2023 18:12, Gaurav Nagarkoti wrote:

hi everyone,

w.r.t. Prometheus stateful set deployment I'm receiving the following 
error within logs


/*level=error msg="Error loading config 
(--config.file=/etc/prometheus-shared/prometheus.yaml)" 
file=/etc/prometheus-shared/prometheus.yaml err="open 
/etc/prometheus-shared/prometheus.yaml: no such file or directory"*/

/*
*/

  * would like to know the probable cause for the same
  o places to check
  * troubleshooting steps for  resolving the same
  * any workaround

As the error message says the file prometheus.yaml in the directory 
/etc/prometheus-shared doesn't exist, which is the configuration file 
for Prometheus.


You need to either ensure the file does exist at that location or adjust 
the command line to give the correct location if different.


--
Stuart Clark

--
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/17b0538a-5c8d-6964-3032-fb0a8589d64b%40Jahingo.com.

[prometheus-users] Prometheus-Thanos-Grafana Integration || error || open /etc/prometheus-shared/prometheus.yaml: no such file or directory

[Gaurav Nagarkoti]

hi everyone,

w.r.t. Prometheus stateful set deployment I'm receiving the following error 
within logs

*level=error msg="Error loading config 
(--config.file=/etc/prometheus-shared/prometheus.yaml)" 
file=/etc/prometheus-shared/prometheus.yaml err="open 
/etc/prometheus-shared/prometheus.yaml: no such file or directory"*


   - would like to know the probable cause for the same
   - places to check
   - troubleshooting steps for  resolving the same 
   - any workaround

Thank you,
Gaurav N.

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/c570e1ca-26a1-4045-b25c-aca3616d8f3fn%40googlegroups.com.

[prometheus-users] A way to exclude incident_key from Alertmanager Payload

[Apollo L]

Hi,

Is there a way to exclude incident_key from the Alertmanager payload 
completely? I have one integration where I want to send repeat alerts even 
when the payload is exactly same, but the integration deduplicates events 
by default if the incident_key is same. If there is a way to exclude 
incident_key for certain alerts, this will solve a problem for us without 
requesting any changes to the integration.

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/663cbfc1-2cc2-4f70-943a-3c3c516f36f0n%40googlegroups.com.