Discussed in https://github.com/cuebook/CueObserve/discussions/75

Describe the solution you'd like I'd love to give CueObserve a try but our warehouse is currently in MS SQL Server.

Describe the solution you'd like Add ClickHouse as a supported data source.

I will wait when https://github.com/cuebook/CueObserve/issues/52 will resolve and try to implements PR

Is your feature request related to a problem? Please describe. I'd love to give CueObserve a try but our warehouse is currently in MS SQL Server.

Describe the solution you'd like Add SQL Server as a supported data source.

Additional context I'd be interested in making the necessary pull request, but I'd like some high level advice on what might be needed.

Is it as simple as adding the necessary sqlserver.py in https://github.com/cuebook/CueObserve/tree/main/api/dbConnections ?

Describe the bug Cueobserve scheduled tasks are getting being struck in celery queue and not completing(No error is thrown)

To Reproduce Steps to reproduce the behavior:

1. create 6 different anomalies definitions
2. create 5 min cron interval & wait for 5min to start the scheduled tasks

th0se tasks are not completing even after 1 day.

for debugging, I have tried executing 5 scheduled tasks and 1 Scheduled task separately(different cron intervals), its is working fine, but when the scheduled tasks are 6 with same cron interval those got struck and didn't finish

Expected behavior It should complete the 6 accepted tasks and pull the next tasks

Thanks

Is your feature request related to a problem? Please describe. The docker-compose files provided sets everything with network mode "host". For various reason this setting does not work in my environment.

Describe the solution you'd like

• Capacity to use port mapping within the docker-compose files.
• Capacity to use a Docker Swarm

got the result:

/usr/local/lib/python2.7/dist-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release. from cryptography.hazmat.backends import default_backend Traceback (most recent call last): File "/usr/local/bin/docker-compose", line 7, in from compose.cli.main import main File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 24, in from ..config import ConfigurationError File "/usr/local/lib/python2.7/dist-packages/compose/config/init.py", line 6, in from .config import ConfigurationError File "/usr/local/lib/python2.7/dist-packages/compose/config/config.py", line 51, in from .validation import match_named_volumes File "/usr/local/lib/python2.7/dist-packages/compose/config/validation.py", line 12, in from jsonschema import Draft4Validator File "/usr/local/lib/python2.7/dist-packages/jsonschema/init.py", line 21, in from jsonschema._types import TypeChecker File "/usr/local/lib/python2.7/dist-packages/jsonschema/_types.py", line 3, in from pyrsistent import pmap File "/usr/local/lib/python2.7/dist-packages/pyrsistent/init.py", line 3, in from pyrsistent._pmap import pmap, m, PMap File "/usr/local/lib/python2.7/dist-packages/pyrsistent/_pmap.py", line 98 ) from e ^ SyntaxError: invalid syntax

Discussed in https://github.com/cuebook/CueObserve/discussions/129

• [x] Image bytes included in response json

Sometimes Anomaly detection job fails or the RCA job fails due to fewer data in a few buckets in that case we don't even show the results for the other buckets.

    if not allTasksSucceeded:
        runStatusObj.status = ANOMALY_DETECTION_ERROR

We have added such checks to the code. But I think this is not a good thing to do as the user is not aware of the reason for the failure. Better is to skip this bucket and show the result of the rest of the buckets.

Is your feature request related to a problem? Please describe. There are different kinds of datasets. Anomalies on some are a P0 alert and on some, they are not that urgent. On the same dataset also a certain threshold needs immediate attention while others do not that much.

Describe the solution you'd like While configuring settings for the slack channel we should be able to configure the different priorities and their slack channel id. Then while creating anomaly definition we should mention the priority of the anomaly definition. Just like we do for schedules.

Describe the bug Failed to create a docker image using docker-compose -f docker-compose-dev.yml up -d . Build fails with error Service 'cueo-backend' failed to build : Build failed

To Reproduce Steps to reproduce the behavior:

1. Git clone this repo
2. Run docker-compose -f docker-compose-dev.yml up -d

Expected behavior CueO components image to be built successfully and CueObserve to start running on localhost:3000

Additional context Will add the entire log in the file or snippet below.

Discussed in https://github.com/cuebook/CueObserve/discussions/187

Discussed in https://github.com/cuebook/CueObserve/discussions/172

select DATE_FORMAT(date, '%Y-%m-%d %H') as Date,
pagelt from pageloadtime2