-
Notifications
You must be signed in to change notification settings - Fork 435
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
[Nginx] Add SLO's with Nginx Package #10269
Conversation
@@ -1,7 +1,7 @@ | |||
format_version: "3.0.2" | |||
format_version: "3.3.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsoriano - I have updated the version to 3.3.0 to test the behaviour and I am getting this error.
Error: building package failed: invalid content found in built zip package: could not load specification for version [3.3.0]: spec version "3.3.0" not found
Can you suggest on how to test this change with the pre-release version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No released version of package spec contains this spec version, you will need to add a replace in the meantime, something like this:
go mod edit -replace github.com/elastic/package-spec/v3=github.com/elastic/package-spec/v3@main
go mod tidy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the format_version
that we could use for testing the package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the
format_version
that we could use for testing the package?
format_version: 3.3.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsoriano - Tried the above step and with the format_version:3.3.0
we are still getting the same error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, yes, this should be enough for CI.
If you want to use elastic-package locally with this dependency you can run it as go run github.com/elastic/elastic-package
from the integrations repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jsoriano!
- We are getting few validation errors in different package, I am skipping those for now as those are not related.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, after updating go.mod all tests are executed, but you can ignore the ones not related to your package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No released version of package spec contains this spec version
@jsoriano When is the next release of the package spec?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsoriano When is the next release of the package spec?
We release more or less on demand, and we have just released 3.2.1. Maybe we can release 3.2.2 soon with a couple of bugfixes. This release would also include 3.3.0 prerelease, what will allow to use SLOs in prerelease packages.
🚀 Benchmarks reportTo see the full report comment with |
go.mod
Outdated
@@ -208,3 +208,5 @@ require ( | |||
sigs.k8s.io/structured-merge-diff/v4 v4.4.1 // indirect | |||
sigs.k8s.io/yaml v1.3.0 // indirect | |||
) | |||
|
|||
replace github.com/elastic/package-spec/v3 => github.com/elastic/package-spec/v3 v3.2.1-0.20240626070810-2758f3ed9689 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@muthu-mps I just want to verify if this version is correct v3.2.1-0.20240626070810-2758f3ed9689
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsoriano If I understand correctly, this addition is temporary? I mean once the next package-spec is released, do we still need this change? Maybe we should exclude this change from git and just rely on running go run github.com/elastic/elastic-package build
locally to be able to test it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@muthu-mps I just want to verify if this version is correct
v3.2.1-0.20240626070810-2758f3ed9689
Yes, With this version I am able to build the integrations successfully by adding SLO's. That means it is using the package-spec
change to add slo's.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jsoriano If I understand correctly, this addition is temporary? I mean once the next package-spec is released, do we still need this change? Maybe we should exclude this change from git and just rely on running
go run github.com/elastic/elastic-package build
locally to be able to test it?
Yes, this is temporary to allow to run in CI till 3.3.0 is available. This PR cannot be merged till then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This replace can be removed now, we have just released a version of elastic-package
that includes the technical preview of 3.3.0.
Changes LGTM! I leave a comment here, regarding updating the README file of the Ngnix integration to include the SLO asset addition. |
Co-authored-by: Panagiota Mitsopoulou <giota85@gmail.com>
I found similar commit, where |
## SLOs | ||
|
||
SLOs are usually defined in terms of metrics such as availability, response time, and throughput, and they are used to ensure that the service meets the needs of its users. | ||
You can use the Nginx integration to measure the availability of the Nginx service. The SLOs gets created automatically during the installation of the integration. The user can view the created SLOs in the Kibana dashboard panel. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@muthu-mps Nice! I took your changes and I was able to see the README changes in the UI!
I have one correction regarding this text in the Kibana dashboard panel
. You should change that, since user can see the automatically generated SLOs under the Observability SLOs page.
I was checking the Kibana SLO documentation page and they reference the SLOs page page like this Observability -> SLOs
.
So feel free to change to: The user can view the created SLOs in the Observability -> SLOs page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I have updated the README file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per offline discussion, need to update the following things!
- Need to use index logs-* instead of logs-nginx-*
- Need to add data_stream.dataset query since the field that has been used is ecs and if the user having multiple packages, SLO/alerts will also be generated from that field!
Yes Harnish, The issue here is that the default dataview is only supported here. I have already captured it here. |
💚 Build Succeeded
History
|
Quality Gate failedFailed conditions |
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
Fixes https://github.com/elastic/observability-dev/issues/3677
Adds new SLO to be shipped with the integration package.
package spec
version in the integration to 3.3.0 (pre-release version) as suggested by @jsorianoPackage spec changes goes here.