Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Challenges for Integrations using Prometheus Input #4271

Closed
ishleenk17 opened this issue Sep 22, 2022 · 3 comments
Closed

Challenges for Integrations using Prometheus Input #4271

ishleenk17 opened this issue Sep 22, 2022 · 3 comments
Assignees
Labels
release-pending Stalled Team:Service-Integrations Label for the Service Integrations team

Comments

@ishleenk17
Copy link
Contributor

ishleenk17 commented Sep 22, 2022

While working on multiple service integrations, we came to a point of using prometheus as input for many integrations.
As a result we started collating some of the challenges we are facing with Prometheus input and probable solutions for the same,
This document list the challenges and solutions

cc: @ruflin
Pinging @elastic/obs-service-integrations

@ishleenk17 ishleenk17 added release-pending Team:Service-Integrations Label for the Service Integrations team labels Sep 22, 2022
@ishleenk17 ishleenk17 self-assigned this Sep 22, 2022
@andrewkroh
Copy link
Member

Can you please share the document publicly? The user community might be interested in this discussion.

@ishleenk17
Copy link
Contributor Author

ishleenk17 commented Nov 10, 2022

Listing down the conclusions from the document in the ticket as well:

Conclusions:

  • For curated integrations, we should have a compact set of metrics and individual mapping should be followed here.
  • Ways of handling metrics explosion:
  1. Flattened type, this will index the entire object as a single field:
    https://www.elastic.co/guide/en/elasticsearch/reference/current/flattened.html
  2. Using metrics_include/exclude: Here only the included metrics will be mapped.
    https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-prometheus-collector.html
  3. If required for some scenarios, dynamic_mapping: false setting :
    https://www.elastic.co/guide/en/elasticsearch/reference/current/dynamic.html#dynamic
  4. Mapping limit settings (Might have data rejections issues):
    https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-settings-limit.html.
    A probable solution to handling data rejections: Make total fields limit less of a nuisance to users elasticsearch#89911
  • Have as many options as possible exposed to the user. Eg: Bearer_token, ssl_authenticaion_authorities should be exposed
  • Discussion around the generic way of handling integrations using Prometheus as endpoint for exporting metrics: This will be handled once we have the Prometheus input which will be providing custom mapping and ingest pipeline

@botelastic
Copy link

botelastic bot commented Nov 11, 2023

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Nov 11, 2023
@botelastic botelastic bot closed this as completed May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-pending Stalled Team:Service-Integrations Label for the Service Integrations team
Projects
None yet
Development

No branches or pull requests

2 participants