- Notifications
You must be signed in to change notification settings - Fork 515
[Istio] Add metric type to fields #6889
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
Conversation
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
🌐 Coverage report
|
ChrsMark left a comment
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.
Hey @constanca-m could you please add more details in the PR's description about what impact these changes will have? Will the package be broken? From what is mentioned in the description this is not clear to me. Maybe I miss context here but still I think that PRs should be self explanatory. Any links that would help here should be included in the PR's description.
| @@ -1,4 +1,9 @@ | |||
| # newer versions go on top | |||
| - version: "0.3.1" | |||
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.
I think this should be bumped up to 0.4.0 since it's not a bugfix but an enhancement.
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.
Will the package be broken?
The package will not be broken. Enabling TSDB with this change will break one of the visualizations of the predefined dashboard. But now, TSDB is not enabled, so merging this PR would not make any difference on that visualization.
I think this should be bumped up to 0.4.0 since it's not a bugfix but an enhancement.
I bumped it to 0.3.1 since 0.3.0 has another TSDB enhancement and this logic has been followed for every TSDB changes on the packages. But I could update it to 0.4.0 if you still think it's better?
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.
I think 0.4.0 is more accurate in general.
However do you have a specific plan that you folks follow in all TSDB changes? If that's the case is this decided/documented or it's just a convention?
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.
it is just a convention, it is not documented anywhere
Can we be more verbose on this? Why it's not working? Do we need a follow-up fix for this? Reading this makes me think that sth is broken but still do not know what is it and if related with this change.
Can you add a note here that it's not an issue for this PR since it does not enable TSDB?
What is the context of this? Can you add more context for what is this one related to please? |
I will bring it up tomorrow on TSDB meeting. I am also not sure why histogram types are being "ignored" for this purpose. The dynamic templating was an issue solved not long ago: elastic/kibana#155004 and we can see in this merged PR that every metric was changed apart from the histograms.
Yes, I will add it.
Those metrics are counter rates and I though at first that since they are counter rates, the metric type would be counter. Then I checked to confirm how they change over time and realized they were a gauge. That's all the context, it is just a proof to the reviewer in case they have the same doubt that I had. |
| object_type: keyword | ||
| description: | | ||
| Istiod metric labels | ||
| - name: istio.istiod.metrics.*.value |
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.
@constanca-m can you please share as well the screenshot of the data view for those fields? and the mapping?
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.
Yes, the mapping is on the description.
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
| Package istio - 0.3.1 containing this change is available at https://epr.elastic.co/search?package=istio |
What does this PR do?
Add metric type to metric fields for TSDB migration.
Histogram object does not have a metric type because it is not working - metric type gauge not appearing on the mapping:
Additionally, enabling TSDB with these metric types will cause a visualization to break since it is using an unsupported aggregation for type counter:

This is not a blocker to this PR, because TSDB is not yet enabled.
Extra: Proof that counter rate is a gauge:

Checklist
changelog.ymlfile.Related issues
Relates to #6567.