Instana grouping in Analyze Calls for Smart Alert Event by blueprint template

Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

As the Log blueprint is being superseded by the new Smart Alert on Logs feature entirely, IBM has evaluated the request and has determined that it cannot be implemented at this time or does not align with our current strategy or roadmap.

In 12 months, you will receive a notification that you can resubmit this request for consideration.

Thank you for bringing your ideas to us. If you have any additional feedback, thoughts or ideas, or if there is anything else I can do, please do not hesitate to reply to this message to continue the conversation.

For the Logs blueprint we should be able to change to default grouping by log.message (as when alerting for just one log.level, grouping by level wouldn't be helpful)

As for HTTP code blueprint we'll need to still check how common alert configs are where a single status code is used, as in this case too, grouping for just a single code would be suboptimal.

Hello Mate, many thanks for the clarification. In our case blueprint would be Logs or Http Status Code. For blueprint Logs grouping by log.level or better log.message, for blueprint Http Status Code by http.status would be favourable.

So, we do have some different groupings already. We just checked Smart Alerts for Applications to have the following:
For Slowness blueprint: no grouping

• For per-AP alerting: grouping by service.name

• For per-Service alerting, or narrowed down to a single service by ID: by endpoint.name

• For per-Endpoint alerting: by call.name

• When scoped to a single endpoint: no grouping

• For Throughput blueprint:

• if expression-filter contains tags about service/endpoint: group by endpoint.name, otherwise service.name

• Else: use default grouping from UA: endpoint.name

So, if you have some specific examples where you'd like to see a different default grouping, please let me know and we can see if it's something we could add.

e.g. if the smart alert is built on blueprint log the "Analyze Calls" predefined grouping could be by log message or on blueprint http-code by http code (your example). Does this make sense!?

Could you please provide an example on which blueprint you'd like this?
I can think of HTTP errors to group by the error codes, but other blueprints may not have a straightforward grouping possibility.