Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

Export/import services and pipelines #40

Open
kikito opened this issue Mar 9, 2015 · 5 comments
Open

Export/import services and pipelines #40

kikito opened this issue Mar 9, 2015 · 5 comments

Comments

@kikito
Copy link
Contributor

kikito commented Mar 9, 2015

Related with #39

It would be useful to have one endpoint to export/import a service's configuration (endpoint, pipeline) so that it can be then imported in a different monitor.

@interhive
Copy link

Any progress on this? I'm running into the same memory/disk IO issue I had before.

@kikito
Copy link
Contributor Author

kikito commented May 25, 2015

Hi @interhive,

Currently our development efforts are in the backend, so frontend features such as this one have drifted a bit.

I would like to try to help you anyway. You have an on-premise monitor, right? The last thing I have is that, it was a Debian-based installation (after moving away from Docker, with which you were having trouble).

Can you tell me more about the issues you are having? Maybe there is a simpler solution than exporting everything to a new server.

@interhive
Copy link

I moved away from docker to the Debian install. I tried the redis command you gave but, under Wheezy, the redis version didn't support the EVAL command. So, I went ahead and upgraded to Debian Jessie yesterday. After upgrading and wiping out the redis database with the command you gave, I rebuilt the APITools configuration and all seems well now. I wish I knew what caused the sudden performance issue. It really crops up out of nowhere. Tons of memory and CPU usage out of nginx and redis.

@IsmaABA
Copy link

IsmaABA commented Oct 20, 2016

Hi! I use apitools in production, but my problem is how export my configuration and pipelines for have a backup. And how to import in another machine. Thanks!

@mikz
Copy link
Contributor

mikz commented Oct 21, 2016

@IsmaABA the easiest way is to use redis backup and import it on different node.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants