Hot answers tagged

11

As far as I know, Prometheus doesn't mind high-cardinality data. What Prometheus doesn't like is high-cardinality labels. Let's start with Prometheus official documentation, it gives a good high-level explanation why: CAUTION: Remember that every unique combination of key-value label pairs represents a new time series, which can dramatically increase ...


6

kill -9 is used by the kernel to terminate stateful programs that are no longer responding (including to shutdown requests). To gracefully shut down a stateful app you would use kill -15 which instructs the application to call it's shutdown functions and do the requisite cleanup. If you app is truly stateless, there should be no difference in the results of ...


4

I can answer the 2nd point: Docker is most suited in a micro service based architecture when the application runs inside the containers but the storage or any other live sessions are maintained in shared RAM or the database. Basically you just should not store anything inside the docker container. There are many reasons to it: Consider upgrade: Someone ...


4

I think the solution comes down to a broad spectrum of approaches that ensures data protection: Data Classification: The most efficient technical strategy is to categorise the data at the point of creation rigorously. At its core, the developers are responsible for ensuring that all logged information is assigned a category. Categorization can, for example,...


3

The durability design objective is not especially relevant above some number of 9's, because it is simultaneously both extremely unlikely and non-zero. The 99.999999999% durability is easily calculated by reading between the lines as the product of the failure probabilities of 6 copies each with an AFR between 1% and 2%. Older versions of the documentation ...


3

A stateless app can always handle kill -9? Yes. But even a stateless app handles connections from the outside (or it would do nothing, really!). That is the issue here. If your app, say, some HTTP server that only serves static files, and is thus stateless, were to be routinely killed with -9, then ever so often, you would kill it with an active connection. ...


2

Let's simplify the dictionary in the first task and loop subelements in second. The tasks below - set_fact: nginx_users_selected: "{{ nginx_users_selected| default({})| combine({item.key: item.value}) }}" loop: "{{ nginx_users| dict2items| ...


1

we'd prefer not to bake them into the actual Docker image itself (plus we want the ability to change the assets without having to recompile the application images). This is indeed good properties to have. You are on the right track. The problem, however, comes with our read-only data assets (similar to a game's asset files). This can be solved with ...


1

looks like your new to stack exchange. You need to form a clearer question to get a good answer.... As far as your error goes.... count is a reserved name. It's only accessible when the block you're writing has a count set! You have You just need to specify the count of aws_internet_gateway data resources you're trying to get. Your code implies there is ...


1

Welcome to DevOps SE! Is it possible to make data management and operation of data sets to be an asset on its own? It seems like data has become more important so a more data-centric approach could help. Program managers have the insider info on what the demo data needs to look like This proves also organizational silo and lack of communication in the ...


Only top voted, non community-wiki answers of a minimum length are eligible