Changing SLOs causing issues with scheduled views about slogen HOT 5 CLOSED

yeah the 50 char limit has been frustrating, the search team has agreed to increase it to 256 but currently.

I was wondering if when we add the "hash" to the view name, that we also limit the name to no more than 50 characters

yes, this will be the ideal approach here for now. once the limit has been increased to 256 we can make the naming more human readable along with the hash suffix.

from slogen.

A workaround is to rename the SLO to "xxx-v2" to get it to repopulate the data

from slogen.

yeah this has been a known limitation of views.
i like the query hash idea, it will cause a one time recreation of existing scheduled views when released but I think its well worth it. let me discuss this with other and get back.

from slogen.

Awesome! One more thing to add to this:
The name of the SLO i.e. "api-ltc" will cause issues if it's too long because its directly used to name the scheduled view. This meant that when the view name i.e. "tf_slogen_view_api_ltc" becomes longer than 50 characters, it errors out.

I was wondering if when we add the "hash" to the view name, that we also limit the name to no more than 50 characters, regardless of what the SLO name is. This would mean that I could have something like "api-with-very-long-name-slo-ltc" and it would still work.

from slogen.

added --useViewHash flag to add a hash of the query as suffix.
By default the flag is false for preserving old behaviour without using the flag.

released in https://github.com/SumoLogic-Labs/slogen/releases/tag/v0.7.11

the view name char limit has also been increased to 255.

from slogen.