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

(Stack Monitoring) Ingest Pipeline install HTTP 404 errors #199532

Open
stefnestor opened this issue Nov 8, 2024 · 1 comment
Open

(Stack Monitoring) Ingest Pipeline install HTTP 404 errors #199532

stefnestor opened this issue Nov 8, 2024 · 1 comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team

Comments

@stefnestor
Copy link
Contributor

👋 howdy, team! Following-up to kibana#41936 and kibana#149386, attempting a default Elastic Cloud setup with Logs&Metrics enabled is erring under "Ingest Pipelines".

  1. Create Deployment (GCP v8.15.3 "storage optimized") with ES (2GB by 2 zones) and KB (1GB by 1 zone)
  2. Enable Logs&Metrics. (Confirmed occurs with and without "self-monitoring".)
  3. Create a Data View under Stack Management (so doesn't redirect you later, just for demo purposes).
  4. Navigate Stack Monitoring > select "remind me later" for "Create Rules" pop-in > Elasticsearch Overview > Ingest Pipelines.
  5. See errors HTTP 404 Saved object [dashboard/elasticsearch-metrics-ingest-pipelines] not found
    Image
  6. Attempting kibana#149386 workaround POST /api/fleet/epm/packages/elasticsearch/latest from DevTools HTTP 500 errors (without KB logs saying more than literally the same)
    Image
  7. Instead do longer workaround : Kibana > Integrations, search "Elasticsearch" (/app/integrations/detail/elasticsearch-1.15.3/overview) > "Add Elasticsearch" > "Add integration only (skip agent installation)" > "Save and continue" > "Add Elastic Agent later". Page loads after as expected.
    Image
@stefnestor stefnestor added bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring labels Nov 8, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 8, 2024
@bhavyarm bhavyarm added the Team:Monitoring Stack Monitoring team label Nov 8, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 8, 2024
@consulthys
Copy link
Contributor

This should be solved by #190980

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

3 participants