Hi,
Could you please help me in configuring FR IDM metrics in Prometheus helm
chart in GITHUB to collect data from IDM using the IDM endpoint for metrics.
Thanks & regards,
Sai Kiran.
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To
Hi all,
I am working on setting up Prometheus in a Federated state for Istio,
exactly as depicted
here
https://istio.io/latest/docs/ops/best-practices/observability/#optimizing-metrics-collection-with-recording-rules.
However when I configure Prometheus to scrape the /federate endpoint and
{__name__!~"(prefix_1|prefix_2).+"}
On Tuesday, 15 November 2022 at 06:59:34 UTC oof...@gmail.com wrote:
> Hello,
>
> I'm trying to find the best way to use federation to match a metric
> blacklist. Currently we are using a single query string as one long array
> element to accomplish this,
Hi all,
I'm attempting to do a basic metric relabeling where I replace
the __name__ by removing a prefix (specifically workload:). This is taken
directly from the upstream istio documentation found here
Hello,
I'm trying to find the best way to use federation to match a metric
blacklist. Currently we are using a single query string as one long array
element to accomplish this, i.e.:
params:
'match[]':
- >-
{__name__=~".+",
__name__!~"prefix_1.+",
Hello,
We use file_sd_configs extensively. We have multiple target files (json)
and it is refered in prometheus yaml. The targets in json are maintained by
our customized discovery agents.
We now have usecase to support dns_sd_configs. Does dns_sd_config also
allow cases where the dns domain
i need support install data sources error "Error reading Prometheus:
bad_response: readObjectStart: expect { or n, but found <, error found in
#1 byte of ...| <|..., bigger context ...| Node
Exporter|..."
--
You received this message because you are subscribed to the Google Groups
We have a requirement that each service in our organization is able to set
its own pagerduty service and slack channel. We have 1300 of these
combinations. We want to match on the "team" label on alerts. So far i've
come up with repeating the following route and receiver for all 1300 teams
-
Would anyone happen to have a sample Alertmanager.yml that includes the
arbitrary key values here:
[ details: { : , ... } | default = {
firing: '{{ template "pagerduty.default.instances" .Alerts.Firing
}}'
resolved: '{{ template "pagerduty.default.instances" .Alerts.Resolved
}}'
Hi,
can you please help me to configure FR IDM metrics in Prometheus helm chart
on GITHUB to collect data from IDM to Prometheus using IDM endpoint.
Thanks & regards,
Sai Kiran.
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To
You didn't say what URL you put in for the data source. But based on the
error, I'm guessing that you've pointed the URL at an instance of
node_exporter, not an instance of prometheus.
That is, I think you put: http://127.0.0.1:9100 # the port which
node_exporter listens on
If so, you
> Reason: We have large number of targets and want to maintain smaller
files.
What's the reason you are using dns_sd_configs in the first place? It
sounds like you should be using file_sd_configs. You should only use
dns_sd_configs if you need to do an unusual DNS lookup like SRV or MX
12 matches
Mail list logo
