Add CLI activity Log to Domostats

This should already be included but is not.

Domo should add robust CLI logging into Domostats

We have repeated issue where Domo occasionally removes the upsert key on our dataset without warning or cause.

Domo can also add a section to the Web GUI that allows users to control Upsert Keys for CLI datasets

4
4 votes

Comments

  • CR-eSobylak
    CR-eSobylak Contributor

    Does anybody else have an issue where the Upsert Key is removed when you update the schema for a table? Domo removes the key without warning. Even in cases where the upsert key column(s) are preserved and you won't know about it until it is too late.

    Do other folks struggle with this as well?

  • DanBrinton
    DanBrinton Domo Product Manager

    Hi, @CR-eSobylak - What is the CLI logging you're looking for? For logged actions taken using the CLI tool, logs are written to the Activity Log and are logged as the Domo user who authenticated in the CLI tool (or, if authenticated using an auth token, logged as the Domo user that owns the auth token).

    Does that meet your need? Or are you looking for a different kind of logging?

    Also, regarding an Upsert Key being removed: Please raise that with Domo Support if you haven't already.

    Thanks!

  • CR-eSobylak
    CR-eSobylak Contributor

    Is there anything in the Activity Log that marks CLI actions as such? Or do they all get comingled with regular User actions? If they are co-mingled then this does not meet the need to being able to audit CLI actions separetly.

    I have opened a Domo support ticket. They are still looking into the Key being removed.