I find the root cause is that our http client didn't use connection pool,
On Saturday, March 7, 2020 at 12:03:49 PM UTC+8, Kaiming Wan wrote:
>
> Env info:
> prometheus version: 2.16.0
> linux: centos7
> prometheus config:
> system config: 8 core 16g ram
>
> ```
> --web.max-connections=1024 --web
I have introduced the security module in springboot2.0 and want to
authenticate the request of / actuator / *.
Now visit the IP: port / actuator / prometheus through the browser, and
enter the username and password for normal access;
only the username and password in basic_auth are added to prom
Hello, how can i get the grfana dashboard like you to monitor prometheus's
inner metric itself. Can the dashboard config be shared?
On Saturday, May 18, 2019 at 1:32:14 AM UTC+8, limi...@gmail.com wrote:
>
> Hello Prometheus experts,
>
> We are starting to use Prometheus since last October and it
Env info:
prometheus version: 2.16.0
linux: centos7
prometheus config:
system config: 8 core 16g ram
```
--web.max-connections=1024 --web.read-timeout=5m
--storage.tsdb.retention.time=30d --query.max-concurrency=200
--query.timeout=2m --storage.tsdb.path=/home/admin/app/prometheus
--config.
thanks for your help I newbie on prometheus app and i don't known many
things
On Fri, 6 Mar 2020, 16:21 Brian Candler, wrote:
> On Friday, 6 March 2020 18:56:08 UTC, Ricardo Estalder wrote:
>>
>> - source_labels: [module, __address__]
>> target_label: __param_target
>> repl
On Friday, 6 March 2020 18:56:08 UTC, Ricardo Estalder wrote:
>
> - source_labels: [module, __address__]
> target_label: __param_target
> replacement: $1
> action: replace
>
Not sure what's going on: there's no need to join labels together, and then
later on you repl
Thank now it works !
relabel_configs:
- source_labels: [module]
target_label: __param_module
- source_labels: [module, __address__]
target_label: __param_target
replacement: $1
action: replace
- source_labels: [__address__]
separator: ;
In your relabeling, you also need to copy label "module" to
"__param_module" (otherwise it won't get sent to the exporter)
--
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, sen
> As you said, someone else is hitting the /metrics endpoint, the health
probes!
Is it worth asking for endpoints for healthy/ready so we don't trigger the
exporter doing all the work and subsequently incur expenses just to check
(from outside the container/instance) if the exporter is worth t
I don't see anything that allows me to change its behavior. I've increased
--storage-tsdb.retention.time and --query.lookback-delta, and it didn't
change anything.
On Friday, March 6, 2020 at 10:16:50 AM UTC-5, sayf eddine Hammemi wrote:
>
> hmmm this maybe linked to the WAL size ?
>
> On Fri, M
hmmm this maybe linked to the WAL size ?
On Fri, Mar 6, 2020 at 3:31 PM hai huang wrote:
> I am getting the error message "Error on ingesting samples that are too
> old or are too far into the future" when trying to put my own custom
> timestamp into the scrape data. According to this issue (
>
https://fancyhabermagazin.blogspot.com/2020/03/turkcell-yonetiminden-ayrilik.html
--
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..
I am getting the error message "Error on ingesting samples that are too old
or are too far into the future" when trying to put my own custom timestamp
into the scrape data. According to this issue
(https://github.com/prometheus/prometheus/issues/4911), this problem
problem has been resolved. Ho
Hi,
I would like to share a python package that allows you to query prometheus
metrics into python dataframe.
https://github.com/goettl79/parides
In the source code you need to replace one line in prepare_time_slices in
converter.py from
date_range = panda.date_range(start=start_time, end=e
On 04.03.20 18:26, Brian Candler wrote:
Outside of the prometheus ecosystem, there are applications which are
designed for matching log patterns and alerting on specific conditions
- typically known as "HIDS" (host-based intrusion detection systems) -
e.g. ossec/wazuh. There are also tools whi
Ok, found it... As you said, someone else is hitting the /metrics endpoint,
the health probes!
(ノ_<。)
https://github.com/prometheus/prometheus/issues/2831
Gonna use that feature now...
Thanks for the help!
On Friday, March 6, 2020 at 9:44:01 AM UTC+1, Brian Brazil wrote:
>
> On Fri, 6 Mar 2
On Fri, 6 Mar 2020 at 08:30, Albert Serrallé Ríos
wrote:
> To make things easier, I've just removed everything except for one metric:
>
> region: us-east-1metrics:
> - aws_namespace: AWS/CloudFront
> aws_metric_name: Requests
> aws_statistics: [Sum]
> aws_dimensions: [DistributionId, Region
To make things easier, I've just removed everything except for one metric:
region: us-east-1metrics:
- aws_namespace: AWS/CloudFront
aws_metric_name: Requests
aws_statistics: [Sum]
aws_dimensions: [DistributionId, Region]
aws_dimensions_select:
Region: [Global]
Then prometheus:
globa
It's usual to keep the raw data as returned by the exporter.
If the two manufacturers are using the *same* OID from the same standard
MIB, but using different units, then one of them is doing it wrong.
If the two manufacturers are returning different OIDs in different
vendor-specific MIBs, then
19 matches
Mail list logo
