Delete and Print actions for SignalCopy console applicatoin

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.

[elv1s42]

Hi!

Just want to share a couple of more actions for SignalCopy:
Action (--action) can be 'copy', 'print' or 'delete'. The delete action works by default for all signals, but you can also specify --signal=.

I my case I had a couple of deleted (via Seq Web GUI) signal, which were copied into another server. So I had to remove them via Seq API.

[nblumhardt]

Thanks for the PR!

The purpose of signal-copy in this repo is to provide a codebase that can be extended and modified to fit different administrative scenarios, so I think adding more features to it might start to detract from that goal.

Your suggestions do raise the interesting possibility of building/shipping a more flexible Seq admin client... I can see things like:

# Creates a .seq-admin file with server details
seq-admin login -s https://my-seq -u admin -p somepass
seq-admin signal export -n "Production Errors" -o production-errors.json
seq-admin signal delete -n "Production Errors"
seq-admin signal import -i production-errors.json
...

This might be a bit of a pipe-dream, given current time and resource constraints, but there's the possibility we could create a new, mostly-empty repository and just chip away at it slowly. What do you think?

[elv1s42]

Hi @nblumhardt,
I think this is a good idea and ready to contribute (at least for the commands, that may be useful to me).
At the moment I am using custom SignalCopy console app builded with net45 traget framework.
It would be great to have something officially approved by Datalust organization.

[nblumhardt]

Moving to datalust/seqcli#2 :-)

[nblumhardt]

Just a quick note, this has been published in the latest seqcli preview.