Skip to content

Conversation

klacabane
Copy link
Contributor

@klacabane klacabane commented Nov 23, 2022

Summary

Closes elastic/kibana#144995

Creates a Beat package that supports monitoring of standalone beats and apm-server from Agent.

Testing

@klacabane klacabane added the Team:Infra Monitoring UI - DEPRECATED Label for the Infrastructure Monitoring UI team. - DEPRECATED - Use Team:obs-ux-infra_services label Nov 23, 2022
@klacabane klacabane self-assigned this Nov 23, 2022
@elasticmachine
Copy link

elasticmachine commented Nov 23, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-12-16T16:30:03.135+0000

  • Duration: 16 min 56 sec

Test stats 🧪

Test Results
Failed 0
Passed 8
Skipped 0
Total 8

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented Nov 28, 2022

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (0/0) 💚
Files 100.0% (0/0) 💚
Classes 100.0% (0/0) 💚
Methods 100.0% (6/6) 💚
Lines 100.0% (0/0) 💚 7.4
Conditionals 100.0% (0/0) 💚

@klacabane klacabane marked this pull request as ready for review December 1, 2022 15:09
@miltonhultgren miltonhultgren self-requested a review December 2, 2022 10:27
Copy link
Contributor

@crespocarlos crespocarlos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I've quickly looked at it, but I haven't run any tests yet. First, I've got a question on the package name: beats or beat?

@klacabane
Copy link
Contributor Author

Looks like the system tests fail because the stack started by the CI is older than the minimum kibana version of the package (>= 8.7.0). I thought the constraint was ignored when testing, I'll take a look

Copy link
Contributor

@miltonhultgren miltonhultgren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏼 Tested and works well for both variants

Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
@jsoriano
Copy link
Member

Some failures now are related to the upgrade of the format version, look here for troubleshooting them: https://github.com/elastic/elastic-package/blob/main/docs/howto/update_major_package_spec.md#troubleshooting-upgrades-from-package-spec-v1-to-v2

@klacabane
Copy link
Contributor Author

klacabane commented Dec 15, 2022

System tests are complaining about the dataset format when we overwrite it in the manifest.yml, we may not check that field when doing the comparison. edit: it should probably be picked up here

[0] field "data_stream.dataset" should have value "beat.stats", it has "beats.stack_monitoring.stats"
[1] field "event.dataset" should have value "beat.stats", it has "beats.stack_monitoring.stats"

@jsoriano
Copy link
Member

System tests are complaining about the dataset format when we overwrite it in the manifest.yml, we may not check that field when doing the comparison. edit: it should probably be picked up here

[0] field "data_stream.dataset" should have value "beat.stats", it has "beats.stack_monitoring.stats"
[1] field "event.dataset" should have value "beat.stats", it has "beats.stack_monitoring.stats"

Yeah, it looks like something is missing there. I will take a look.

Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
@jsoriano
Copy link
Member

@klacabane elastic-package 0.70.1 should fix the issue with dataset checks, we have just updated to this version the integrations repository, please try to update this branch.

@klacabane
Copy link
Contributor Author

/test

@klacabane klacabane merged commit 6e35a3a into elastic:main Dec 19, 2022
@elasticmachine
Copy link

Package beat - 0.0.1 containing this change is available at https://epr.elastic.co/search?package=beat

klacabane added a commit to elastic/kibana that referenced this pull request Dec 19, 2022
## Summary
Closes #146686

Update apm and beats queries to read from the Beat package data streams
created in elastic/integrations#4708. Also
updates health API to fetch from the data streams.

API tests follow up in #147755

### Testing
That's a fairly heavy workflow. I'm investigating ways to make that
easier

- build `beat` package with `elastic-package build`. The package is not
published yet so you'll need to pull
elastic/integrations#4708 locally
- start a stack `elastic-package stack up -v -d --version
8.7.0-SNAPSHOT`. Make sure you do this within `integrations` repo so it
picks up the previously built package
- start a beat service with `elastic-package service up -v --variant
metricbeat_8.7.0`
- install both elasticsearch and beat packages from the kibana started
by the stack command (`https://localhost:5601`). Nothing shows up in SM
if we don't have elasticsearch data.
- both packages are prerelease versions and we need to explicitly tell
Integrations plugin to show them up[1]
- elasticsearch hosts is `https://elasticsearch:9200` and beat _should
be_ `http://elastic-package-service_beat_1:5066` but it may differ
depending on your docker version
- start a Kibana with this branch connected to the elasticsearch
instance from the `stack up` command. [see
howto](https://github.com/elastic/observability-dev/blob/main/docs/infra-obs-ui/stack-monitoring_integration-packages.md#connecting-a-local-kibana)
- navigate to Stack Monitoring and verify the metricbeat is properly
monitored
- start an apm server with `elastic-package service up -v --variant
apm_8.7.0`
- navigate to Stack Monitoring and verify apm-server is properly
monitored


[1]
<img width="853" alt="Screenshot 2022-12-01 at 00 20 20"
src="https://user-images.githubusercontent.com/5239883/204929352-c7656679-f88c-4013-b1f8-cf7c67d4c830.png">

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
@andrewkroh andrewkroh added the New Integration Issue or pull request for creating a new integration package. label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Integration:beat Beat New Integration Issue or pull request for creating a new integration package. Team:Infra Monitoring UI - DEPRECATED Label for the Infrastructure Monitoring UI team. - DEPRECATED - Use Team:obs-ux-infra_services
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Stack Monitoring] create beats package
6 participants